> I wonder if my similar problem is related to what you report here:  I am using
> dhcpcd and ifplug with my ADSL router, which acts as the dhcp server on my
> LAN.  For some reason ifplug does not always manage to get an IP address from
> the router and I end up with an APIPA address.  /etc/init.d/net.eth0
> stop/start gets it going again.  This problem only occurs if I disconnect and
> then reconnect the ethernet cable.  No such problem exists when I boot the
> machine with the cable already connected to the NIC.  I haven't changed
> timeouts or anything else from the dhcpcd defaults.  I have always attributed
> this problem to a somewhat slow dhcp server on the router.

It is similar, with a difference that /etc/init.d/net.eth0 restart
doesn't help. I tried
enlarging timeout but with no help.

>
> As a note:  WinXP machines do not have any such problem.  Even though they may
> end up with a APIPA address, they will in minute or so drop it and acquire a
> 10.10.10.XXX domain address from the router.  dhcpcpd does not seem to have
> this flexibility.

I noticed that in most cases after I boot to windows, when I reboot
back to linux I can't connect.
When I reboot back to windows, net is up.

When it fails I noticed that it send DHCP requests, but doesn't get a response.

I tried dhclient, dhcpd and pump, and the results are allways the
same. It happens in the evenings, when internet traffic is high.
-- 
gentoo-user@lists.gentoo.org mailing list

Reply via email to