After upgrading baselayout (1.12.0_pre17-r3) and udev (090), the network scripts no longer work correctly. My computer has three onboard ethernet ports. I use eth0 for the connection to the LAN and eth2 for the cable modem. eth0 has a static configuration and eth2 uses dhcp. The problem occurs when bringing up net.eth2. The dhcp-client program tries to setup _all_ interfaces, not just eth2. This destroys the configuration on eth0. If I bring up eth2 first then eth0, both interfaces work but I lose the resolv.conf from dhcp. Apr 20 17:51:39 [kernel] e100: eth2: e100_watchdog: link up, 10Mbps, half-duplex Apr 20 17:51:45 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 5 Apr 20 17:51:45 [dhclient] DHCPREQUEST on eth2 to 255.255.255.255 port 67 Apr 20 17:51:45 [dhclient] DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 20 17:51:46 [dhclient] DHCPACK from 10.178.112.1 Apr 20 17:51:46 [dhclient] bound to 67.187.84.119 -- renewal in 120069 seconds. Apr 20 17:51:50 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6 Apr 20 17:51:54 [dhclient] DHCPREQUEST on eth0 to 255.255.255.255 port 67 Apr 20 17:51:56 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 Apr 20 17:52:10 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5 Apr 20 17:52:10 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 8 Apr 20 17:52:15 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12 Apr 20 17:52:18 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 Apr 20 17:52:27 [dhclient] DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20 Apr 20 17:52:31 [dhclient] DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14 Apr 20 17:52:46 [dhclient] No DHCPOFFERS received.
post your /etc/conf.d/net file also, are you using hot or cold plugging ?
Why would udev matter in this? If you go back to 089 version of udev, does this get fixed?
(In reply to comment #2) > Why would udev matter in this? > > If you go back to 089 version of udev, does this get fixed? > I only mentioned this because it changed at the same time. Also this is the first time I've used the new scripts that use udev for coldplug. udev was trying to bring up net.eth1 when the system booted, but I figured out how to fix that. my /etc/conf.d/net: config_eth0=( "192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255" ) config_eth2=( "dhcp" )
(In reply to comment #1) > post your /etc/conf.d/net file > > also, are you using hot or cold plugging ? > Neither for the ethernet devices. I changed /etc/conf.d/rc to not allow coldplugging of net.*
What version of dhcp have you got installed?
(In reply to comment #5) > What version of dhcp have you got installed? > 3.0.3-r4
Try 3.0.3-r7
(In reply to comment #7) > Try 3.0.3-r7 > This corrects the problem.
I'm having similar problem. I have 2 interfaces: eth_wan0 configured using ISP's dhcp and eth_lan0 with static IP. I'm running local dhcpd for subnet on eth_lan0 too. When net.eth_wan0 is started, dhclient is run and it reconfigures eth_lan0 using local dhcpd server provided IP. I got this problem after upgrading baselayout from 1.11.15 to 1.12.4-r2. I have installed dhcp-3.0.3-r9. Appending "${iface}" to dhclient commandline in /lib/rcscripts/net/dhclient.sh on line 109 fixed the problem. But it's probably only hack, not a bugfix.
(In reply to comment #9) > Appending "${iface}" to dhclient commandline in /lib/rcscripts/net/dhclient.sh > on line 109 fixed the problem. But it's probably only hack, not a bugfix. No, that's the correct fix. I cannot believe that no-one has spotted that! Including me! Will be in the next baselayout release.
(In reply to comment #10) > Will be in the next baselayout release. Fixed in baselayout-1.12.4-r3
Fixored
