Fix Ubuntu 16 Networking

Bashed · 12-24-2019, 11:34 AM

Just installed Ubuntu 16 server with /29 as primary and /24 as secondary at the Cisco switches.

I use a simple bind.sh script to bind the /24.

Code:

for i in $(seq 2 254);
    do
		ip addr add xxx.xxx.211.$i/24 dev eno1
	done

ip addr show

I'm getting this error though.

Code:

root@ns4:~# systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled)
  Drop-In: /run/systemd/generator/networking.service.d
           └─50-insserv.conf-$network.conf
   Active: failed (Result: exit-code) since Tue 2019-12-24 12:29:58 EST; 1min 3s ago
     Docs: man:interfaces(5)
  Process: 13859 ExecStart=/sbin/ifup -a --read-environment (code=exited, status=1/FAILURE)
  Process: 13853 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm settle (code=exi
 Main PID: 13859 (code=exited, status=1/FAILURE)

Dec 24 12:29:56 ns4 ifup[13859]: RTNETLINK answers: File exists
Dec 24 12:29:56 ns4 ifup[13859]: Failed to bring up eno1:97.
Dec 24 12:29:56 ns4 ifup[13859]: RTNETLINK answers: File exists
Dec 24 12:29:56 ns4 ifup[13859]: Failed to bring up eno1:98.
Dec 24 12:29:56 ns4 ifup[13859]: RTNETLINK answers: File exists
Dec 24 12:29:56 ns4 ifup[13859]: Failed to bring up eno1:99.
Dec 24 12:29:58 ns4 systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Dec 24 12:29:58 ns4 systemd[1]: Failed to start Raise network interfaces.
Dec 24 12:29:58 ns4 systemd[1]: networking.service: Unit entered failed state.
Dec 24 12:29:58 ns4 systemd[1]: networking.service: Failed with result 'exit-code'.

berndbausch · 12-26-2019, 06:23 AM

You seem to imply that the systemctl error and the addition of IP addresses are related. What makes you think they are?

Also, the fact that systemctl reports an error is not necessarily a problem. I see that systemctl repeatedly attempts to bring eno1 up. This fails because it is already up. Could this be a bug in the systemd unit definition? In any case, apart from this particular failure, is anything wrong with your networking?

vincix · 12-27-2019, 02:28 PM

Is 'ip addr show' part of the script? I hope not.

Are the ips assigned after you execute the loop?

I'd also like to reiterate what berndbausch said: is there actually anything wrong with your network? If you get no connection, have you configured your gateway?