Am I missing something in my understanding here?
The first time I run "/etc/init.d/networking restart" after a reboot I
get the same message I would if I ran "ifdown eth0" about eth0 releasing
its dhcp address, and I no longer have network connectivity, i.e. the
/etc/init.d/networking script does not seem to call ifup -a to restart
all network connections. (I have only one nic on this computer.) To
get network connectivity back I must manually run "ifup etho".
However, ever after that first time event running
"/etc/init.d/networking restart" I get the message "reconfiguring
network interfaces" but no ifdown or ifup messages showing the releasing
and acquiring of an ip address through dhcp. If I run "ifdown eth0" at
this point it tells me that eth0 is not configured, but I have network
connectivity and ifconfig -a confirms that eth0 is configured.
If I run "/etc/init.d/networking stop" I get the correct message that
eth0 is releasing its dhcp address. However, then running
"/etc/init.d/networking start" does not run ifup on eth0 as eth0 remains
unconfigured, although I receive the message that the network interfaces
have been successfully reconfigured. I must manually run ifup eth0 to
configure it again and regain network connectivity.
My question is, is this behavior by design, or have I stumbled across a
bug?
I'm running an up-to-date Sid install.
Reply to: