With a new, updated Edgy install, I took the default
/etc/network/interfaces and replaced it with the following:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.5.2
netmask 255.255.255.0
gateway 192.168.5.1
After doing so, I ran;
/etc/init.d/networking restart
However, 30 minutes later, my system was unreachable at that IP, having
received a DHCP lease. Found that the dhclient3 process was still
running after the restart.
As ubuntu's networking init script is little more than a front-end to
ifup/ifdown, it becomes prone to bug 38410.
** Description changed:
After booting, eth0 is up and dhclient3 is running. However, eth0 still
doesn't have an address, see bug #33968, so I have to do an ifdown and
ifup to make things work.
I have noticed that after running ifdown, the dhclient3 process is still
running. If I just run ifup afterwards, there will be two of them
running.
(ifupdown 0.6.7ubuntu7 and dhcp3-client 3.0.3-6ubuntu6)
$ ps ax|grep dhc
3387 ? S< 0:00 dhclient3 -pf /var/run/dhclient.eth0.pid -lf
/var/lib/dhcp3/dhclient.eth0.leases eth0
+
+ Update: Please note that this also affects the init.d/networking script.
--
dhclient3 keeps running after ifdown
https://launchpad.net/bugs/38140
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
