Port-i386 archive

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

Re: 6.0.1 upgrade dhcp problem

 >It also seems that the sk config using dhcpcd might sometimes work, but
 >usually fails - and we do not yet have a reliable way to know which to
 >expect on any particular boot.   Is that a reasonable assessment of the
 >current results?

Yes, I've only seen sk0 configured properly once (maybe twice)--dhcpcd normally times out waiting for carrier when attempting to configure it.

 >I note there that the MTU set is 1500.   That is what it would be if
 >no MTU was being configured.   This suggests that the DHCP server that
 >dhcpcd is actually willing to listen to, is not attempting to configure
 >some strange mtu

No, it's not. By the way, the two DHCP servers are a failover pair running ISC's DHCP server version 4.2.5, but that's irrelevant to DHCP clients to the best of my knowledge.

I commented out "require dhcp_server_identifier" in /etc/dhcpcd.conf but it made no obvious difference.

Using dhcpcd's  --nohook mtu  option didn't help:

# dhcpcd --nohook mtu fxp0
dhcpcd[47]: version 5.5.4 starting
dhcpcd[47]: Kernel is not configured to accept IPv6 RAs
dhcpcd[47]: fxp0: carrier acquired
dhcpcd[47]: fxp0: carrier lost
dhcpcd[47]: fxp0: waiting for carrier
dhcpcd[47]: fxp0: carrier acquired
dhcpcd[47]: fxp0: broadcasting for a lease
dhcpcd[47]: fxp0: offered from
dhcpcd[47]: fxp0: ignoring offer of from
dhcpcd[47]: fxp0: acknowledged from
dhcpcd[47]: fxp0: checking for
dhcpcd[47]: fxp0: leased for 604800 seconds
dhcpcd[47]: forked to background, child pid 51
# ifconfig fxp0
        address: 00:10:dc:7b:92:a9
        media: Ethernet autoselect (none)
        status: no carrier
        inet6 fe80::210:dcff:fe7b:92a9%fxp0 prefixlen 64 scopeid 0x3
# dhcpcd -U fxp0

So the -U option gave no output, even when I used it on the PC whose fxp0 NIC works (after configuring the NIC via sysinst's menu).


Home | Main Index | Thread Index | Old Index