1 |
On Friday 18 January 2008, Marko Kocić wrote: |
2 |
> > Actually, as long as the interface is up, you can sniff traffic even if |
3 |
> > it does not have an IP address. Emerge wireshark (somehow...), do (as |
4 |
> > root) an "ip link set eth0 up" (or "ifconfig eth0 up") and run |
5 |
> > wireshark. Start capturing packets, run dhcpcd from the command line (or |
6 |
> > whatever DHCP client you use), and see what goes on the wire. You should |
7 |
> > see DHCP discovery/offer/request messages, or maybe not all of them if |
8 |
> > things are not working correctly. For each DHCP packet, look at the DHCP |
9 |
> > payload details from wireshark (you can save the capture for later |
10 |
> > viewing too). |
11 |
> > |
12 |
> > Then, start windows, install wireshark for windows, and do the same. To |
13 |
> > force a DHCP negotiation in windows, open a command prompt and issue |
14 |
> > an "ipconfig /release" followed by an "ipconfig /renew" (IIRC). Look at |
15 |
> > the traffic captured after the /renew command, and look for obvious or |
16 |
> > blatant differences between windows and linux in DHCP packets of the |
17 |
> > same kind. |
18 |
> |
19 |
> Thanks for the info. I'll try that. |
20 |
> |
21 |
> Also, I just found by googling that there is dhcp client called |
22 |
> net-misc/pump which |
23 |
> have --win-client-ident option. I'll try that too. |
24 |
|
25 |
I wonder if my similar problem is related to what you report here: I am using |
26 |
dhcpcd and ifplug with my ADSL router, which acts as the dhcp server on my |
27 |
LAN. For some reason ifplug does not always manage to get an IP address from |
28 |
the router and I end up with an APIPA address. /etc/init.d/net.eth0 |
29 |
stop/start gets it going again. This problem only occurs if I disconnect and |
30 |
then reconnect the ethernet cable. No such problem exists when I boot the |
31 |
machine with the cable already connected to the NIC. I haven't changed |
32 |
timeouts or anything else from the dhcpcd defaults. I have always attributed |
33 |
this problem to a somewhat slow dhcp server on the router. |
34 |
|
35 |
As a note: WinXP machines do not have any such problem. Even though they may |
36 |
end up with a APIPA address, they will in minute or so drop it and acquire a |
37 |
10.10.10.XXX domain address from the router. dhcpcpd does not seem to have |
38 |
this flexibility. |
39 |
-- |
40 |
Regards, |
41 |
Mick |