| 1 |
On 6/27/2007 7:45 AM Drew Tomlinson said the following: |
| 2 |
|
| 3 |
> On 6/27/2007 1:12 AM Alan McKinnon said the following: |
| 4 |
> |
| 5 |
>> On Wednesday 27 June 2007, Randy Barlow wrote: |
| 6 |
>> |
| 7 |
>> |
| 8 |
>>> Drew Tomlinson wrote: |
| 9 |
>>> |
| 10 |
>>> |
| 11 |
>>>> I ran tcpdump on eth1 and no packets are leaving the interface. |
| 12 |
>>>> Thus I assume that's why I'm not getting an address. |
| 13 |
>>>> |
| 14 |
>>> |
| 15 |
>>> I don't know how to solve your problem, but I don't think DHCP is at |
| 16 |
>>> the TCP layer of your network, and so you shouldn't see packets for |
| 17 |
>>> DHCP there. DHCP is a special protocol if I recall... |
| 18 |
>>> |
| 19 |
>> |
| 20 |
>> |
| 21 |
>> That's correct, dhcp is an ethernet protocol, and tcp/ip are one |
| 22 |
>> layer above it. |
| 23 |
>> |
| 24 |
>> Drew should be able to see the packets with the 'proto ether' |
| 25 |
>> expression. |
| 26 |
>> man tcpdump for more info |
| 27 |
>> |
| 28 |
>> alan |
| 29 |
>> |
| 30 |
>> |
| 31 |
> |
| 32 |
> Thank you both for your ideas. I've tested and it seems that I should |
| 33 |
> be able to see the packets without any special expressions. I've run |
| 34 |
> tcpdump on my DHCP server and can see packets from other nodes on my |
| 35 |
> network: |
| 36 |
> |
| 37 |
> Client IP: bigdaddy |
| 38 |
> Client Ethernet Address: 00:50:8d:d7:8d:89 (oui Unknown) |
| 39 |
> [|bootp] |
| 40 |
> 15:39:48.229850 IP (tos 0x0, ttl 128, id 25950, offset 0, flags |
| 41 |
> [none], proto: UDP (17), length: 328) bigdaddy.bootpc > |
| 42 |
> 255.255.255.255.bootps: BOOTP/DHCP, Request from 00:50:8d:d7:8d:89 |
| 43 |
> (oui Unknown), length: 300, xid:0x7707a3b2, secs:768, flags: [none] |
| 44 |
> |
| 45 |
> When I run 'tcpdump -i eth1' on the laptop, I see no traffic |
| 46 |
> whatsoever. I read the man page for tcpdump regarding the 'proto |
| 47 |
> ether' expression Alan mentions. While it is true that this |
| 48 |
> expression will limit the traffic captured, not specifying any |
| 49 |
> expression will show all traffic. Plus DHCP works by sending UDP |
| 50 |
> packets and thus 'proto ether' does not seem to be appropriate. |
| 51 |
> |
| 52 |
> Thanks, |
| 53 |
> |
| 54 |
> Drew |
| 55 |
|
| 56 |
|
| 57 |
For the archives... Ditching wpa_supplicant in favor of iwconfig |
| 58 |
(wireless tools port) solved my problems. Only downside is that I am |
| 59 |
unable to use WPA-PSK authentication. Maybe a future version of |
| 60 |
wpa_supplicant will work? |
| 61 |
|
| 62 |
Drew |
| 63 |
|
| 64 |
-- |
| 65 |
Be a Great Magician! |
| 66 |
Visit The Alchemist's Warehouse |
| 67 |
|
| 68 |
http://www.alchemistswarehouse.com |
| 69 |
|
| 70 |
|
| 71 |
-- |
| 72 |
gentoo-user@g.o mailing list |
Archives