Network repair with ifreload -a after reboot

K

kalle3

New Member
Sep 5, 2025
4
0
1
Hi,

I discovered that I need to repair my network configuration after rebooting with 'ifreload -a'. I'm currently doing this with a service (/etc/systemd/system/ifreload.service). Than my network works fine. What's wrong with my network configuration? Or is the networking.service destroying my network after rebooting, just like it does with 'systemctl restart networking.service'?
I can't solve the problem with following error message. It looks like the wrong order, doesn't it?
journalctl -u networking
networking[2203]: error: bond1.6: cmd '/bin/ip route replace default via 192.168.1.126 proto kernel dev bond1.6 onlink' failed: returned 2 (Error: Nexthop device is not up.


/etc/network/interfaces :

auto lo
iface lo inet loopback

iface eno1 inet manual

#corosync ring
auto eno2
iface eno2 inet static
address 10.1.6.3/24

iface eno3 inet manual

iface eno4 inet manual

auto eno49
iface eno49 inet manual

auto eno50
iface eno50 inet manual

#Storage, VM, Migration
auto bond1
iface bond1 inet manual
bond-slaves eno49 eno50
bond-miimon 100
bond-mode 802.3ad
bond-xmit-hash-policy layer3+4
bond-lacp-rate fast

# Management VLAN 6 on bond1
auto bond1.6
iface bond1.6 inet static
address 192.168.1.53/25
gateway 192.168.1.126
vlan-raw-device bond1

# Ceph VLAN 7 on bond1
auto bond1.7
iface bond1.7 inet static
address 192.168.7.8/24
vlan-raw-device bond1

# Bridge for VMs
auto vmbr1
iface vmbr1 inet manual
bridge-ports bond1
bridge-stp off
bridge-fd 2
bridge-vlan-aware yes
bridge-vids 2-4094

source /etc/network/interfaces.d/*
 
Setting the gateway directly on the bond does not work the first time, if the bond is member of a VLAN-aware bridge. You need to create the stanza for the vmbr1 interface instead:

Code: 
auto vmbr1.6
iface vmbr1.6 inet static
  address 192.168.1.53/25
  gateway 192.168.1.126

This should work.
 
You must log in or register to reply here.
Top Bottom