Arch Linux

Vrob

Member

Registered: 2007-12-07

Posts: 42

Error: Nexthop has invalid gateway

Hi all,

I have recently noticed a problem with my Contabo VPS. Apparently a script trying to set my routes failes at boot time, however, aside from some ping issues my network connection seems stable. Contabos VPS support has logged onto the machine and checked the routes, at seems that they are fine. It was speculated that docker might be interfering with my network setup, but I am not doing anything arcane there except isolating containers by creating docker networks. They all operate with Archs default drivers.

$ sudo systemctl --failed
  UNIT                      LOAD   ACTIVE SUB    DESCRIPTION
● set-route-network.service loaded failed failed set-route-network.service

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.

1 loaded units listed.

Here's the error message:

$ sudo systemctl status set-route-network.service
● set-route-network.service
     Loaded: loaded (/etc/systemd/system/set-route-network.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Tue 2020-05-12 15:22:22 CEST; 2 weeks 2 days ago
   Main PID: 652 (code=exited, status=2)

May 12 15:22:12 mail.sendersuchlauf.net systemd[1]: Started set-route-network.service.
May 12 15:22:22 mail.sendersuchlauf.net set_route_network.sh[728]: Error: Nexthop has invalid gateway.
May 12 15:22:22 mail.sendersuchlauf.net systemd[1]: set-route-network.service: Main process exited, code=exited, status=2/INVALIDARG
May 12 15:22:22 mail.sendersuchlauf.net systemd[1]: set-route-network.service: Failed with result 'exit-code'.

There are no other networkmanager configured:

$ sudo systemctl list-unit-files --state=enabled
UNIT FILE                              STATE   VENDOR PRESET
apparmor.service                       enabled disabled
autovt@.service                        enabled disabled
dbus-org.freedesktop.network1.service  enabled disabled
dbus-org.freedesktop.resolve1.service  enabled disabled
dbus-org.freedesktop.timesync1.service enabled disabled
docker.service                         enabled disabled
fail2ban.service                       enabled disabled
getty@.service                         enabled enabled
set-route-network.service              enabled disabled
sshd.service                           enabled disabled
systemd-networkd-wait-online.service   enabled disabled
systemd-networkd.service               enabled enabled
systemd-resolved.service               enabled enabled
systemd-timesyncd.service              enabled enabled
systemd-networkd.socket                enabled disabled
remote-fs.target                       enabled enabled
drop_caches.timer                      enabled disabled
pkgfile-update.timer                   enabled disabled
reflector.timer                        enabled disabled

19 unit files listed.

The only issues I notice are that sometimes it takes very long for a connection to a remote host to be established. Once it's there, its fast and error free. This happens when I try to ping google.com:

$ ping google.de
PING google.de (172.217.22.35) 56(84) bytes of data.
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=1 ttl=55 time=17.1 ms
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=2 ttl=55 time=17.2 ms
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=3 ttl=55 time=17.1 ms
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=4 ttl=55 time=17.0 ms
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=5 ttl=55 time=17.1 ms
64 bytes from 172.217.22.35 (172.217.22.35): icmp_seq=6 ttl=55 time=17.0 ms
^C
--- google.de ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 17168ms

Note that it took >17s to complete 6 pings, but each individual one was super quick!

Here are my routes:

$ ip route
default via 144.91.64.1 dev eth0 proto static
144.91.64.0/18 via 144.91.64.1 dev eth0
172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown
172.18.0.0/16 dev br-39b89b206139 proto kernel scope link src 172.18.0.1
172.19.0.0/16 dev br-9607d743c359 proto kernel scope link src 172.19.0.1 linkdown
172.22.0.0/16 dev br-5bcd1615b90f proto kernel scope link src 172.22.0.1
172.23.0.0/16 dev br-56b96adfbf03 proto kernel scope link src 172.23.0.1
172.24.0.0/16 dev br-c1fb48933348 proto kernel scope link src 172.24.0.1
172.27.0.0/16 dev br-ac66e9f2c0ca proto kernel scope link src 172.27.0.1
192.168.0.0/20 dev br-4c77bd7ff5bb proto kernel scope link src 192.168.0.1
192.168.203.0/24 dev br-d68946ddfe4b proto kernel scope link src 192.168.203.1

And my network config:

[Match]
Name=eth0

[Network]

Address=2a02:c207:3004:7365:0000:0000:0000:0001/64

Gateway=fe80::1

DNS=2a02:c207::2:53

DNS=2a02:c207::1:53


Address=144.91.97.242/18

Gateway=144.91.64.1

DNS=213.136.95.11

DNS=213.136.95.10

(This is the initial setup made by my VPS provider, I didn't touch the file).

When trying to restart the .service, it failes with the same error message. Im confused and would love to get pushed into the right direction for fixing this

Thanks!

Last edited by Vrob (2020-05-28 17:37:12)