Hi,

I am observing a strange problem on net-next (not observed with net,
bisection in progress) where the initial DHCP configuration using
busybox's udhcpc is able to configure the local interface address and
DNS serer, but not the default gateway. Restarting udhcpc a second time
does not exhibit this problem.

This is a system using SYSTEMPORT and the DSA SF2 switch but I could
also observe it on systems using the BCMGENET and Asix USB 2.0 network
drivers (all in tree).

Are there any netlink/packet/rhashtable changes in net-next, but not in
net that could explain that? Note that this is a system with very low
entropy on boot? Making the DHCP client more verbose or stracing it did
not expose the issue as frequently, so this might be some sort of race
condition.

Any hints appreciated!
-- 
Florian
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to