r228700 can't dhclient em0

Dimitry Andric dim at FreeBSD.org
Mon Dec 19 13:24:53 UTC 2011


On 2011-12-19 10:17, Doug Barton wrote:
> I updated to r228700 from 228122 and dhclient exits immediately saying
> that em0 doesn't exist. However ifconfig seems to disagree:
>
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>  metric 0 mtu 1500
>
> options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
>          ether 00:24:e8:30:10:9b
>          nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>          media: Ethernet autoselect (100baseTX<full-duplex>)
>          status: active
> lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST>  metric 0 mtu 16384
>          options=3<RXCSUM,TXCSUM>
>          nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
>
>
> Interestingly, some of the options are different in that version, vs.
> the working version:
>
> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST>  metric 0 mtu 1500
> 	options=219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC>
> 	ether 00:24:e8:30:10:9b
> 	inet 172.17.198.245 netmask 0xffff0000 broadcast 172.17.255.255
> 	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
> 	media: Ethernet autoselect (100baseTX<full-duplex>)
> 	status: active

I saw this too, when my kernel and userland were out of sync (e.g. just
after installing a new kernel, and before installworld).  I suspect it
is caused by the changes in r228571, which cause old ifconfig and
dhclient to not recognize any interfaces.  I'm not 100% sure though...


More information about the freebsd-current mailing list