Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: dhcpcd [configuration] problems



On 24/03/2012 19:44, Chris Ross wrote:
I have a sparc64 host running netbsd-6.  When I boot, the bge0
interface is connected, and can and will receive an address (and an
IPv6 rtadv), but it seems not to be able to do so during
/etc/rc.d/network.  I have:

ifconfig_bge0="dhcp"

I would actively discourage that.
Use dhcpcd=YES instead of running separate instances of it.


in my /etc/rc.conf, and I've even tried putting a "!sleep 10" on
either side of it, which does cause a sleep, but doesn't alleviate the
problem.  I've reset dhcpcd_flags to "-w", and then added "-L" (to
avoid the ZeroConf address), and later "-t 60" to extend the timeout.

  However, now that I have extended the timeout, the problem seems to
be that it doesn't keep *trying*.  When dhcpcd starts up, it triggers
a carrier reset.  Then, since autoconfiguration seems to take longer
than 10-15 seonds, it's given up by then.  I see:

Configuring network interfaces: bge0dhcpcd[113]: version 5.5.4 starting
dhcpcd[113]: bge0: carrier acquired
dhcpcd[113]: bge0: carrier lost
dhcpcd[113]: bge0: waiting for carrier
dhcpcd[113]: bge0: carrier acquired
dhcpcd[113]: bge0: sending IPv6 Router Solicitation
dhcpcd[113]: bge0: broadcasting for a lease
dhcpcd[113]: bge0: sending IPv6 Router Solicitation
dhcpcd[113]: bge0: sending IPv6 Router Solicitation
dhcpcd[113]: bge0: sending IPv6 Router Solicitation
dhcpcd[113]: bge0: no IPv6 Routers available
dhcpcd[113]: timed out
..

  And with a "-t 60", there's 40 seconds or so between the "no IPv6
Routers available", and the "timed out". It doesn't rebroadcast for a lease, it doesn't send another router solicitation, and if it *would*,
I suspect it would work.

This is false. You just don't see it. Try enabling debugging "-d" and
you'll see that dhcpcd re-transmits it's requests at the correct RFC
defined intervals.


  I don't see in the man page anything to tell it "please wait longer
after the carrier is acquired", or "please keep trying harder if you
don't get answers".  Is there any way to do this?

-t 60 means timeout after 60 seconds from start. The fact that carrier
was lost, acquired, etc is irrelevant to the timeout.
If carrier is being lost and acquired like that then I'd say it's due to either faulty cabling or driver. For reference, I use a bge(4) driver in
my i386 laptop which works just fine.

You could look into using the -K option which stops dhcpcd from ever
checking the driver link status and just tries to configure.

Thanks

Roy


Home | Main Index | Thread Index | Old Index