Moin,
leider eskaliert das mit den Tunneln zwischen den Gateways (für unsere Gluon-Meshes) etwas (um die 70 je Gateway), das macht das alles unübersichtlch. Wobei die meisten ›einfach‹ funktionieren, ›verschwinden‹ aber auch einige (da aber soweit bislang beobachtet immer die selben) nach kurzer Zeit. Beispiel Bicvpn-a:
2024-05-07T21:17:21.797698+00:00 ngw-ber01 root: ifup start: Bicvpn-a
2024-05-07T21:17:26.898427+00:00 ngw-ber01 (udev-worker)[5490]: Bicvpn-a: Could not set Alias=, MACAddress=/MACAddressPolicy=, TransmitQueues=, ReceiveQueues=, TransmitQueueLength=, MTUBytes=, GenericSegmentOffloadMaxBytes= or GenericSegmentOffloadMaxSegments=, ignoring: Device or resource busy
2024-05-07T21:17:31.945029+00:00 ngw-ber01 root: ifup done: Bicvpn-a — 56: Bicvpn-a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000#012 link/ether 1e:5a:15:c6:4d:68 brd ff:ff:ff:ff:ff:ff#012 inet 192.168.115.130/30 brd 192.168.115.131 scope global Bicvpn-a#012 valid_lft forever preferred_lft forever#012 inet6 2001:bf7:1317:308:0:115:128:2/126 scope global #012 valid_lft forever preferred_lft forever#012 inet6 fe80::1c5a:15ff:fec6:4d68/64 scope link #012 valid_lft forever preferred_lft forever
2024-05-07T21:17:42.721611+00:00 ngw-ber01 named[5666]: listening on IPv4 interface Bicvpn-a, 192.168.115.130#53
2024-05-07T21:17:42.792389+00:00 ngw-ber01 named[5666]: listening on IPv6 interface Bicvpn-a, 2001:bf7:1317:308:0:115:128:2#53
2024-05-07T21:17:42.792825+00:00 ngw-ber01 named[5666]: listening on IPv6 interface Bicvpn-a, fe80::1c5a:15ff:fec6:4d68%56#53
2024-05-07T21:17:43.468328+00:00 ngw-ber01 ntpd[5869]: IO: Listen normally on 35 Bicvpn-a 192.168.115.130:123
2024-05-07T21:17:43.475846+00:00 ngw-ber01 ntpd[5869]: IO: Listen normally on 117 Bicvpn-a [2001:bf7:1317:308:0:115:128:2]:123
2024-05-07T21:17:43.475963+00:00 ngw-ber01 ntpd[5869]: IO: Listen normally on 118 Bicvpn-a [fe80::1c5a:15ff:fec6:4d68%56]:123
2024-05-07T21:17:47.578499+00:00 ngw-ber01 ntpd[5869]: IO: Deleting interface #35 Bicvpn-a, 192.168.115.130#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs
2024-05-07T21:17:47.578714+00:00 ngw-ber01 ntpd[5869]: IO: Deleting interface #117 Bicvpn-a, 2001:bf7:1317:308:0:115:128:2#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs
2024-05-07T21:17:47.578948+00:00 ngw-ber01 ntpd[5869]: IO: Deleting interface #118 Bicvpn-a, fe80::1c5a:15ff:fec6:4d68%56#123, interface stats: received=0, sent=0, dropped=0, active_time=4 secs
Offensichtlich kam das Interface hoch, aber nach 16 Sekunden verschwindet es von Geisterhand; ifupdown ›weiß‹ noch, daß das Interface einmal erfolgreich initialisiert wurde — aber wer oder was hat es ›hintenrum‹ gelöscht?
root@ngw-ber01 ~ # ip addr show Bicvpn-a
Device "Bicvpn-a" does not exist.
root@ngw-ber01 ~ # ifup --verbose Bicvpn-a
ifup: parsing file /etc/network/interfaces.d/00_lo.cfg
ifup: parsing file /etc/network/interfaces.d/10_batman.cfg
ifup: parsing file /etc/network/interfaces.d/20_domain_bridge.cfg
ifup: parsing file /etc/network/interfaces.d/30_gretap.cfg
ifup: parsing file /etc/network/interfaces.d/42_gre_interbackbone.cfg
ifup: parsing file /etc/network/interfaces.d/90_icvpn.cfg
ifup: parsing file /etc/network/interfaces.d/eth0_iprule.cfg
ifup: interface Bicvpn-a already configured
root@ngw-ber01 ~ # ifdown --force --verbose Bicvpn-a
ifdown: parsing file /etc/network/interfaces.d/00_lo.cfg
ifdown: parsing file /etc/network/interfaces.d/10_batman.cfg
ifdown: parsing file /etc/network/interfaces.d/20_domain_bridge.cfg
ifdown: parsing file /etc/network/interfaces.d/30_gretap.cfg
ifdown: parsing file /etc/network/interfaces.d/42_gre_interbackbone.cfg
ifdown: parsing file /etc/network/interfaces.d/90_icvpn.cfg
ifdown: parsing file /etc/network/interfaces.d/eth0_iprule.cfg
ifdown: configuring interface Bicvpn-a=Bicvpn-a (inet)
run-parts --verbose /etc/network/if-down.d
run-parts: executing /etc/network/if-down.d/bind9
run-parts: executing /etc/network/if-down.d/bridge
run-parts: executing /etc/network/if-down.d/resolvconf
run-parts: executing /etc/network/if-down.d/resolved
/sbin/ip -6 addr del 2001:bf7:1317:308:0:115:128:2/126 dev Bicvpn-a ||:
Cannot find device "Bicvpn-a"
ip rule del iif $IFACE table ffnet ||:
ip addr del 192.168.115.130/255.255.255.252 broadcast 192.168.115.131 dev Bicvpn-a label Bicvpn-a
Cannot find device "Bicvpn-a"
ip -4 addr flush dev Bicvpn-a
Device "Bicvpn-a" does not exist.
ip link set dev Bicvpn-a down
Cannot find device "Bicvpn-a"
run-parts --verbose /etc/network/if-post-down.d
run-parts: executing /etc/network/if-post-down.d/bridge
/sbin/ip l2tp del session tunnel_id 1183 session_id 1183 ||:
RTNETLINK answers: No such device
/sbin/ip l2tp del tunnel tunnel_id 1183 ||:
RTNETLINK answers: No such device
root@ngw-ber01 ~ # ifup Bicvpn-a
Kennt das Problem jemand oder kennt gar 'ne Lösung? systemd-networkd ist keine Hilfe, weil dann das sinnfreie systemd-networkd-wait-online.service für neue Probleme sorgt.
root@ngw-ber01 ~ # lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 12 (bookworm)
Release: 12
Codename: bookworm