Re: Static IP and Network Configuration in Debian Linux

Talking about this HowTo: http://www.howtoforge.com/debian-static-ip-address

Getting this problem:

Code:

(2:2028)# /etc/init.d/networking restart
Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
Reconfiguring network interfaces...RTNETLINK answers: File exists
Failed to bring up eth0.
RTNETLINK answers: File exists
Failed to bring up eth0:0.
done.

Running perfect Debian Wheezy Server with ISPCFG3 + nginx

 

Code:

(2:2109)# service networking restart
Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
Reconfiguring network interfaces...RTNETLINK answers: File exists
Failed to bring up eth0.
RTNETLINK answers: File exists
Failed to bring up eth0:0.
done.

my /etc/network/interfaces

Code:

(2:2112)# 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 85.214.221.98
        netmask 255.255.255.255
        network 85.214.221.98
        broadcast 85.214.221.98
        gateway 85.214.192.1

auto eth0:0
iface eth0:0 inet static
        address 85.214.249.109
        netmask 255.255.255.255
        network 85.214.249.109
        broadcast 85.214.249.109
        gateway 85.214.192.1

#DNS configurations
dns-nameservers 208.67.220.220
dns-nameservers 8.8.8.8
dns-nameservers 8.8.4.4

 

It seems that dhclient is active.
kill the process of dhclient & then try to restart the networking service.

 

I did a killall -9 dhclient followed by service networking restart

output:

Code:

(2:2153)# service networking restart
Running /etc/init.d/networking restart is deprecated because it may not re-enable some interfaces ... (warning).
Reconfiguring network interfaces...RTNETLINK answers: File exists
Failed to bring up eth0.
RTNETLINK answers: File exists
Failed to bring up eth0:0.
done.

Notice the changed line:
Failed to bring up eth0:0.

Any idea how to fix this and how to stop dhclient from starting?
(I went through this tutorial simply to get away from DHCP so I think I can remove it but unsure which package contains dhclient?)

 

Hi please do one thing flush the ip address for the eth0:0, kill all process for the dhclinet then check the network restart.

 

Tried that, after this command my server went down:

logged via console, tried pkill -9 dhclient + service networking restart

Got:

And now I'm down - damn, shouldn'T have tried this in the middle of the day :-/

 

The interface came up on its own without further interaction. poooh. gave me a fright.
Thanks for helping out. You might want to add a few of these instructions onto the howto!

Btw. does it make sense to remove the dhclient parts on my server?

 

dhclient is responsible for the dynamic IP address allocation, sometimes it gives conflict with the static Ip addressing. So it was suggested to kill the dhclient.

Further you were getting the error for the RTLINK exists, it was due to the dhclient trying to update the eth0:0 to dynamic IP, but the network configuration file suggesting to static IP so the error.