Must run "/etc/init.d/networking restart" after each boot

[dochawk]

This machine previously worked under kubuntu, but with the confusion from removing a disk, I ended up doing a fresh install.

Now I need to run

/etc/init.d/networking restart


upon every boot for the network (plain old boring wired network) to come up. This is repeatable; it is needed and works on every boot.

I get the response,

hawk@localhost:~$ sudo /etc/init.d/networking restart
* Reconfiguring network interfaces...
RTNETLINK answers: No such process
SIOCDELRT: No such process


each time.

I assume that it somehow missed a piece during installation, but what?

thanks

hawk

[flarson]

Re: Must run "/etc/init.d/networking restart" after each boot

Since it comes up with restarting networking I am thinking you have the interface defined in /etc/network/interfaces? Will "sudo ifup eth0" bring it up after a reboot? Does your /etc/NetworkManager/nm-system-settings.conf have managed=false? If not network manager will try to manage it as will ifupdown. Right after boot if you run ifconfig do you see no eth0 interface?

[dochawk]

Re: Must run "/etc/init.d/networking restart" after each boot

Since it comes up with restarting networking I am thinking you have the interface defined in /etc/network/interfaces?

root@localhost:/home/hawk# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.0.10
netmask 255.255.255.0
network 192.168.0.0
broadcast 192.168.0.255
gateway 192.168.0.1
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.0.1
dns-search aerie

Right after boot if you run ifconfig do you see no eth0 interface?

It's there, but not active:

root@localhost:/home/hawk# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0d:87:8e:34:1f
inet6 addr: fe80::20d:87ff:fe8e:341f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:7 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:570 (570.0 B) TX bytes:3759 (3.7 KB)
Interrupt:11 Base address:0x8000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:24 errors:0 dropped:0 overruns:0 frame:0
TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1104 (1.1 KB) TX bytes:1104 (1.1 KB)

Will "sudo ifup eth0" bring it up after a reboot?

No:


root@localhost:/home/hawk# ifup eth0
ifup: interface eth0 already configured

Does your /etc/NetworkManager/nm-system-settings.conf have managed=false? If not network manager will try to manage it as will ifupdown.

root@localhost:/home/hawk# cat /etc/NetworkManager/nm-system-settings.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false



and then I do


root@localhost:/home/hawk# /etc/init.d/networking restart
* Reconfiguring network interfaces...
RTNETLINK answers: No such process
SIOCDELRT: No such process
[ OK ]



and the network is up.


This is 100% repeatable.

hawk

[flarson]

Re: Must run "/etc/init.d/networking restart" after each boot

I think you should uninstall the network manager. It is probably configuring you interface even though it should not. I think that
sudo aptitude purge network-manager
is likely to allow your setup to work.

[dochawk]

SOLVED: Must run "/etc/init.d/networking restart" after each boot

Yes, that did it.

It also solved the problem on my laptop that can see the wireless networks but can't connect.

Thanks greatly

hawk