Mehrminütiger Ausfall im 60 Minuten-Takt

wusel · 20. Mai 2024 um 00:24

Ich hab’s auch gerade live erleben dürfen, nachdem ich im Smokeping der VM hinter der Mesh04-Gluon-VM das Muster gefunden und das Remotelogging gefixt hatte:

(Zeiten in UTC)

MTRs vom Knoten zum Gateway und vom Clieent (durch das GW) zu 1.1.1.1:

33378-test-20240502 (192.168.177.14)                   2024-05-20T01:30:05+0200
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                       Packets               Pings
 Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 192.168.177.1                     0.0%  1370    1.2   0.7   0.6  12.3   0.4
 2. p3e9bf2e7.dip0.t-ipconnect.de     0.0%  1370    7.5  10.1   7.4  74.6   7.5
 3. b-eh2-i.B.DE.NET.DTAG.DE          0.0%  1370   13.8  14.0  13.0  65.6   3.7
 4. bgp-ber01.4830.org               10.9%  1370   14.0  14.2  13.6  62.6   3.2
 5. ngw-ber01.4830.org                0.5%  1370   13.7  14.1  13.6  41.0   2.8

                              My traceroute  [v0.95]
 test-mesh02 (10.234.147.250) -> 1.1.1.1 (1.1.1.1)               2024-05-19T23:31:06+0000
 Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                        Packets               Pings
  Host                                Loss%   Snt   Last   Avg  Best  Wrst StDev
  1. 10.234.144.70                     2.0%  1436   22.2  23.3  22.0  48.5   3.3
  2. 194.113.54.65                    86.7%  1436   43.2  24.0  22.0  44.4   2.9
  3. wobcom.n15.community-ix.de        2.6%  1436   24.4  24.6  22.7  71.1   4.2
  4. et-0-0-2-0.cbrc1101.as9136.net    1.5%  1436   24.2  25.3  22.9 107.8   5.5
  5. cloudflare.bcix.de                3.1%  1436   31.9  29.6  22.9 117.1  11.3
  6. one.one.one.one                   2.9%  1436   23.7  24.7  22.7  72.9   4.2

Logs via remote logging:

May 20 00:57:10 33378-test-20240502 netifd: wan (2926): udhcpc: lease of 192.168.177.14 obtained, lease time 600
May 20 00:57:45 33378-test-20240502 netifd: client (2940): cat: write error: Broken pipe
May 20 00:59:59 33378-test-20240502 netifd: client (2940): cat: write error: Broken pipe
May 20 01:00:23 33378-test-20240502 netifd: client (2940): cat: write error: Broken pipe
May 20 01:01:01 33378-test-20240502 netifd: client (2940): cat: write error: Broken pipe
May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: connectivity check failed
May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: going to fallback mode
May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: going back to standard mode
May 20 01:02:10 33378-test-20240502 netifd: Interface 'bat0' is now down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'loopback' is now down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'loopback' is disabled
May 20 01:02:10 33378-test-20240502 netifd: Network device 'lo' link is down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'loopback' has link connectivity loss
May 20 01:02:10 33378-test-20240502 dnsmasq[1767]: no servers found in /tmp/resolv.conf.auto, will retry
May 20 01:02:10 33378-test-20240502 kernel: [1477775.080263] batman_adv: bat0: Interface deactivated: primary0
May 20 01:02:10 33378-test-20240502 kernel: [1477775.082326] batman_adv: bat0: Removing interface: primary0
May 20 01:02:10 33378-test-20240502 kernel: [1477775.084741] batman_adv: bat0: Interface deactivated: mesh-vpn
May 20 01:02:10 33378-test-20240502 kernel: [1477775.086576] batman_adv: bat0: Removing interface: mesh-vpn
May 20 01:02:10 33378-test-20240502 kernel: [1477775.089627] br-client: port 2(bat0) entered disabled state
May 20 01:02:10 33378-test-20240502 netifd: Network device 'bat0' link is down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'bat0' has link connectivity loss
May 20 01:02:10 33378-test-20240502 netifd: Interface 'client' is now down
May 20 01:02:10 33378-test-20240502 kernel: [1477775.137227] device bat0 left promiscuous mode
May 20 01:02:10 33378-test-20240502 kernel: [1477775.138743] br-client: port 2(bat0) entered disabled state
May 20 01:02:10 33378-test-20240502 kernel: [1477775.142172] br-client: port 1(eth0) entered disabled state
May 20 01:02:10 33378-test-20240502 netifd: Interface 'bat0' is disabled
May 20 01:02:10 33378-test-20240502 kernel: [1477775.205729] device eth0 left promiscuous mode
May 20 01:02:10 33378-test-20240502 kernel: [1477775.207360] br-client: port 1(eth0) entered disabled state
May 20 01:02:10 33378-test-20240502 kernel: [1477775.214720] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 20 01:02:10 33378-test-20240502 netifd: Interface 'client' is disabled
May 20 01:02:10 33378-test-20240502 netifd: Interface 'gluon_bat0' is now down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'mesh_vpn' is now down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'mesh_vpn' is disabled
May 20 01:02:10 33378-test-20240502 netifd: Network device 'eth0' link is down
May 20 01:02:10 33378-test-20240502 netifd: bridge 'br-client' link is down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'client' has link connectivity loss
May 20 01:02:10 33378-test-20240502 netifd: Network device 'mesh-vpn' link is down
May 20 01:02:10 33378-test-20240502 netifd: Interface 'mesh_vpn' has link connectivity loss
May 20 01:02:10 33378-test-20240502 netifd: wan (2926): udhcpc: sending renew to 192.168.177.9
May 20 01:02:10 33378-test-20240502 netifd: wan (2926): udhcpc: received SIGTERM
May 20 01:02:10 33378-test-20240502 netifd: Interface 'wan' is now down
May 20 01:02:12 33378-test-20240502 logread[1715]: Logread connected to 192.168.177.9:514
May 20 01:02:13 33378-test-20240502 odhcp6c[15979]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
May 20 01:02:13 33378-test-20240502 odhcp6c[15981]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
May 20 01:02:13 33378-test-20240502 odhcp6c[15981]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
May 20 01:02:15 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:16 33378-test-20240502 netifd: Interface 'wan6' is now up
May 20 01:02:16 33378-test-20240502 firewall: Reloading firewall due to ifup of wan6 (br-wan)
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: reading /var/gluon/wan-dnsmasq/resolv.conf
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: using nameserver fd00::9a9b:cbff:feb1:1397#53
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: using nameserver 2003:ef:9f17:8900:9a9b:cbff:feb1:1397#53
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: using nameserver 192.168.177.9#53
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: using nameserver 192.168.177.1#53
May 20 01:02:16 33378-test-20240502 dnsmasq[2613]: using nameserver 8.8.8.8#53
May 20 01:02:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:22 33378-test-20240502 kernel: [1477786.797900] batman_adv: bat0: IGMP Querier appeared
May 20 01:02:22 33378-test-20240502 kernel: [1477786.799860] batman_adv: bat0: MLD Querier appeared
May 20 01:02:27 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:33 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:39 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:45 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:51 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:02:57 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:03:03 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:03:09 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=5)!
May 20 01:03:10 33378-test-20240502 td-client: [g02m04.4830.org:10004] Tunnel has timed out, closing down interface.
May 20 01:03:10 33378-test-20240502 td-client: [g02m04.4830.org:10004] Failed to send() control packet (errno=19, type=3)!
May 20 01:03:10 33378-test-20240502 netifd: Network device 'mesh-vpn' link is down
May 20 01:03:10 33378-test-20240502 netifd: Interface 'mesh_vpn' has link connectivity loss
May 20 01:03:10 33378-test-20240502 kernel: [1477834.469730] batman_adv: bat0: Interface deactivated: mesh-vpn
May 20 01:03:10 33378-test-20240502 kernel: [1477834.485739] batman_adv: bat0: Removing interface: mesh-vpn
May 20 01:03:10 33378-test-20240502 td-client: [g02m04.4830.org:10004] Connection lost.
May 20 01:03:10 33378-test-20240502 td-client: for(;;) -- context_reinitialize() for all brokers.
May 20 01:03:10 33378-test-20240502 netifd: Interface 'mesh_vpn' is now down
May 20 01:03:10 33378-test-20240502 netifd: Interface 'mesh_vpn' is disabled
May 20 01:03:10 33378-test-20240502 td-client: Performing broker selection...
May 20 01:03:10 33378-test-20240502 td-client: Brokers deemed working: 6
May 20 01:03:10 33378-test-20240502 td-client: main loop -- Reset availability information and standby setting.
May 20 01:03:10 33378-test-20240502 td-client: [g01m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: [g02m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: [g03m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: [g04m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: [g05m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: [g06m04.4830.org:10004] is not flagged as broken, that's good.
May 20 01:03:10 33378-test-20240502 td-client: main loop -- Perform broker processing for 10 seconds or until all brokers are ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] Broker's FQDN has been resolved to 194.113.55.67.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_GET_USAGE, sending initial request.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] Broker's FQDN has been resolved to 194.113.54.80.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_GET_USAGE, sending initial request.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] Broker usage: 384
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] Broker usage: 448
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] Broker's FQDN has been resolved to 194.113.54.81.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_GET_USAGE, sending initial request.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] Broker's FQDN has been resolved to 194.113.55.71.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_GET_USAGE, sending initial request.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] Broker usage: 384
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] Broker usage: 384
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:11 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g04m04.4830.org:10004] is ready.
May 20 01:03:11 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:11 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
[…]
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_REINIT.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] reinitializing tunnel context.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] Failed to resolve hostname.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] Failed to resolve hostname.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_REINIT.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] reinitializing tunnel context.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is in STATE_STANDBY
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_REINIT.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] reinitializing tunnel context.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] Broker's FQDN hasn't been resolved to an IP yet.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is in STATE_RESOLVING
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] Failed to resolve hostname.
May 20 01:03:21 33378-test-20240502 td-client: [g01m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g03m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g04m04.4830.org:10004] is ready.
May 20 01:03:21 33378-test-20240502 td-client: [g05m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: [g06m04.4830.org:10004] is NOT ready.
May 20 01:03:21 33378-test-20240502 td-client: main loop -- select_broker()
May 20 01:03:21 33378-test-20240502 td-client: Selected g02m04.4830.org:10004 as the best broker.
May 20 01:03:21 33378-test-20240502 td-client: main loop -- activate selected broker
May 20 01:03:21 33378-test-20240502 td-client: main loop -- Perform processing on the main context ...
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_GET_COOKIE
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] sending request for a tasty cookie ...
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] is in STATE_GET_TUNNEL
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] sending tunnel setup request ...
May 20 01:03:21 33378-test-20240502 netifd: Interface 'mesh_vpn' is enabled
May 20 01:03:21 33378-test-20240502 netifd: Network device 'mesh-vpn' link is up
May 20 01:03:21 33378-test-20240502 netifd: Interface 'mesh_vpn' has link connectivity
May 20 01:03:21 33378-test-20240502 netifd: Interface 'mesh_vpn' is setting up now
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] Tunnel successfully established.
May 20 01:03:21 33378-test-20240502 td-client: [g02m04.4830.org:10004] Setting MTU to 1364
May 20 01:03:21 33378-test-20240502 netifd: Interface 'mesh_vpn' is now up
May 20 01:03:21 33378-test-20240502 kernel: [1477845.462835] batman_adv: bat0: Adding interface: mesh-vpn
May 20 01:03:21 33378-test-20240502 kernel: [1477845.465202] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1364) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem.
May 20 01:03:21 33378-test-20240502 kernel: [1477845.477372] batman_adv: bat0: Interface activated: mesh-vpn
May 20 01:03:21 33378-test-20240502 firewall: Reloading firewall due to ifup of mesh_vpn (mesh-vpn)
May 20 01:03:22 33378-test-20240502 gluon-radv-filterd[16072]: Switching to f2:be:ef:00:04:71 (TQ=0)
May 20 01:03:29 33378-test-20240502 netifd: Interface 'client' is now up
May 20 01:03:29 33378-test-20240502 dnsmasq[1767]: reading /tmp/resolv.conf.auto
May 20 01:03:29 33378-test-20240502 dnsmasq[1767]: using local addresses only for domain lan
May 20 01:03:29 33378-test-20240502 dnsmasq[1767]: using nameserver 2620:fe::9#53
May 20 01:03:29 33378-test-20240502 dnsmasq[1767]: using nameserver 2606:4700:4700::1112#53
May 20 01:03:29 33378-test-20240502 firewall: Reloading firewall due to ifup of client (br-client)
May 20 01:03:37 33378-test-20240502 td-client: main loop -- connection established, broker [g02m04.4830.org:10004] is fine.
May 20 01:04:13 33378-test-20240502 netifd: client (15981): cat: write error: Broken pipe
May 20 01:06:19 33378-test-20240502 netifd: client (15981): cat: write error: Broken pipe
May 20 01:07:11 33378-test-20240502 netifd: wan (15971): udhcpc: sending renew to 192.168.177.9
May 20 01:07:11 33378-test-20240502 netifd: wan (15971): udhcpc: lease of 192.168.177.14 obtained, lease time 600
May 20 01:07:11 33378-test-20240502 firewall: Reloading firewall due to ifupdate of wan (br-wan)
May 20 01:07:48 33378-test-20240502 netifd: client (15981): cat: write error: Broken pipe
May 20 01:08:29 33378-test-20240502 netifd: client (15981): cat: write error: Broken pipe

Problem 1:

May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: connectivity check failed
May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: going to fallback mode
May 20 01:02:10 33378-test-20240502 : autoupdater-wifi-fallback: going back to standard mode

Das dürfte nicht passieren, a) nicht der »connectivity check failed«, b) nicht »going to fallback mode« & »going back to standard mode« direkt nacheinander.

Problem 2:

May 20 01:03:10 33378-test-20240502 td-client: main loop -- Perform broker processing for 10 seconds or until all brokers are ready.

In den meisten Meshes haben wir 2 GWs mehr in der Firmware hinterlegt als tatsächlich vorbereitet/genutzt. Hier in Mesh 4 sind z. B. g05m04.4830.org und g06m04.4830.org nicht im DNS eingetragen. Heißt bei Problemen mit dem Tunnel gibt es ggf. immer <= 10 Strafsekunden

Zu Problem 1: das lua-Skript /usr/sbin/autoupdater-wifi-fallback testet erst, ob eines der Batman-Gateways via batman-ping (»nur ein Ping«) erreichbar ist. Falls nicht(!), wird versucht, den/die eingetragenen Updateserver per ICMP-Ping (»nur ein einziges Ping!«) zu erreichen — schlägt das auch(!) fehl, wird der Katastrophenfall ausgerufen.

Insofern kann …

… tatsächlich effektiv zur Problemlösung beitragen. Reallocating resources …

wusel · 21. Mai 2024 um 22:27

Problem sollte nun behoben sein, firmware.ipv6.4830.org ist AFAICS aus allen Meshes wieder erreichbar. Und eine neue rawhide-Firmware mit erweitertem Logging im autoupdater-wifi-fallback-Package – was spannenderweise schon am Sonntag, testweise auf meinem Knoten installiert, die Aussetzer verschwinden lies – wurde auch schon von zwei Knoten gezogen:

Screenshot 2024-05-21 at 23-59-05 4830.org e. V

Thomas · 22. Mai 2024 um 06:59

Ohne neue Firmware scheint es auch wieder gut zu sein.
root@33378-TH-Test300e:~# /usr/sbin/autoupdater-wifi-fallback

root@33378-TH-Test300e:~#
root@33378-a42bb0f43a87:~# /usr/sbin/autoupdater-wifi-fallback

root@33378-a42bb0f43a87:~#
Es gibt zwar keine Ausgabe, aber auch kein Versuch die Firmware abzurufen, da der Autoupdater es vorher scheinbar schon geschafft hat. (Der Testknoten ist nur per Wifi Mesh angebunden)

Wurstkanone · 23. Mai 2024 um 14:23

Hallo Zusammen,

also bislang sieht bei mir auch alles wieder gut aus.

In beiden Standorten ist in den letzten Zwei Tagen kein Ausfall mehr aufgetreten.

Ich behalte es im Auge, doch denke ich, dass es sich somit erledigt hat.
Danke @wusel und @Thomas

m.bitterlich · 26. Mai 2024 um 19:52

Moin.

gerade hat der o.g. Knoten 17194-Joy-IT-126f wieder die Connection verloren.
Zusätzlich ist mir letztens aufgefallen, dass nach jedem Connection-Verlust die Traffic-Statistik auf der Geräteseite auf „0“ gesetzt wird. So kann man die „fehlerhaften Knoten“ auch identifizieren, auch wenn sie scheinbar funktionieren.

Die tng-Firmware dagegen läuft klaglos.

Log von 17194-Joy-IT-126f mit Firmware 1.4.0~121

Sat May 25 19:11:26 2024 daemon.debug td-client: [g01m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.err td-client: [g01m05.4830.org:10005] Hostname resolution timed out.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g02m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.err td-client: [g02m05.4830.org:10005] Hostname resolution timed out.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g03m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.err td-client: [g03m05.4830.org:10005] Hostname resolution timed out.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g04m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.err td-client: [g04m05.4830.org:10005] Hostname resolution timed out.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g05m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.err td-client: [g05m05.4830.org:10005] Hostname resolution timed out.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g06m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:26 2024 daemon.debug td-client: [g01m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g02m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g03m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g04m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g05m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:26 2024 daemon.debug td-client: [g06m05.4830.org:10005] is NOT ready.
Sat May 25 19:11:27 2024 daemon.debug td-client: [g01m05.4830.org:10005] is in STATE_REINIT.
Sat May 25 19:11:27 2024 daemon.debug td-client: [g01m05.4830.org:10005] reinitializing tunnel context.
Sat May 25 19:11:27 2024 daemon.debug td-client: [g01m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:27 2024 daemon.debug td-client: [g01m05.4830.org:10005] Broker's FQDN hasn't been resolved to an IP yet.
Sat May 25 19:11:27 2024 daemon.debug td-client: [g02m05.4830.org:10005] is in STATE_REINIT.
Sat May 25 19:11:27 2024 daemon.debug td-client: [g02m05.4830.org:10005] reinitializing tunnel context.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g02m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:28 2024 daemon.debug td-client: [g02m05.4830.org:10005] Broker's FQDN hasn't been resolved to an IP yet.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g03m05.4830.org:10005] is in STATE_REINIT.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g03m05.4830.org:10005] reinitializing tunnel context.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g03m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:28 2024 daemon.debug td-client: [g03m05.4830.org:10005] Broker's FQDN hasn't been resolved to an IP yet.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g04m05.4830.org:10005] is in STATE_REINIT.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g04m05.4830.org:10005] reinitializing tunnel context.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g04m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:28 2024 daemon.debug td-client: [g04m05.4830.org:10005] Broker's FQDN hasn't been resolved to an IP yet.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g05m05.4830.org:10005] is in STATE_REINIT.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g05m05.4830.org:10005] reinitializing tunnel context.
Sat May 25 19:11:28 2024 daemon.debug td-client: [g05m05.4830.org:10005] is in STATE_RESOLVING
Sat May 25 19:11:28 2024 daemon.debug td-client: [g05m05.4830.org:10005] Broker's FQDN hasn't been resolved to an IP yet.
Sat May 25 19:12:23 2024 daemon.notice netifd: client (16572): cat: write error: Broken pipe
Sat May 25 19:13:01 2024 user.notice ssid-changer: autoupdater is running, aborting.
Sat May 25 19:13:06 2024 user.info : autoupdater-wifi-fallback: connectivity check failed
Sat May 25 19:13:06 2024 user.info : autoupdater-wifi-fallback: going to fallback mode
Sat May 25 19:13:06 2024 kern.info kernel: [70011.590073] IPv6: ADDRCONF(NETDEV_UP): tmp.mesh0: link is not ready
Sat May 25 19:13:12 2024 kern.info kernel: [70018.336391] IPv6: ADDRCONF(NETDEV_UP): tmp.mesh1: link is not ready
Sat May 25 19:13:14 2024 user.info : autoupdater-wifi-fallback: connecting to radio0 mueritz.freifunk.net 86:BD:A3:A9:19:B8
Sat May 25 19:13:14 2024 daemon.notice netifd: Interface 'mesh_radio0' is disabled
Sat May 25 19:13:14 2024 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
Sat May 25 19:13:14 2024 kern.info kernel: [70020.346127] device client0 left promiscuous mode
Sat May 25 19:13:14 2024 kern.info kernel: [70020.351092] br-client: port 4(client0) entered disabled state
Sat May 25 19:13:15 2024 kern.info kernel: [70020.427014] device owe0 left promiscuous mode
Sat May 25 19:13:15 2024 kern.info kernel: [70020.431679] br-client: port 6(owe0) entered disabled state
Sat May 25 19:13:15 2024 daemon.notice netifd: Interface 'mesh_radio1' is disabled
Sat May 25 19:13:15 2024 daemon.notice netifd: Interface 'mesh_radio1' has link connectivity loss
Sat May 25 19:13:15 2024 kern.info kernel: [70020.569240] device client1 left promiscuous mode
Sat May 25 19:13:15 2024 kern.info kernel: [70020.574328] br-client: port 5(client1) entered disabled state
Sat May 25 19:13:15 2024 kern.info kernel: [70020.688445] device owe1 left promiscuous mode
Sat May 25 19:13:15 2024 kern.info kernel: [70020.693141] br-client: port 7(owe1) entered disabled state
Sat May 25 19:13:15 2024 kern.info kernel: [70020.781884] batman_adv: bat0: Interface deactivated: mesh0
Sat May 25 19:13:15 2024 kern.info kernel: [70020.787720] batman_adv: bat0: Removing interface: mesh0

m.bitterlich · 26. Mai 2024 um 19:58

Der Firmware-Server ist von diesem Knoten zurzeit auch nicht erreichbar.

  OS: 19.07-SNAPSHOT, r11430+27-ecbbb3    FW: 1.4.0~121
  HW: Joy-IT JT-OR750i
root@17194-Joy-IT-126f:~# autoupdater
Retrieving manifest from http://firmware.ipv6.4830.org/rawhide/sysupgrade/rawhide.manifest ...
autoupdater: warning: error downloading manifest: Connection failed
autoupdater: error: no usable mirror found
root@17194-Joy-IT-126f:~#

m.bitterlich · 26. Mai 2024 um 20:05

Hier leider auch mit neuer Firmware nicht …

root@17194-Joy-IT-126f:~# /usr/sbin/autoupdater-wifi-fallback
autoupdater-wifi-fallback: connectivity check failed
autoupdater-wifi-fallback: going to fallback mode
autoupdater-wifi-fallback: connecting to radio0 mueritz.freifunk.net 86:BD:A3:A9:19:B8
autoupdater-wifi-fallback: executing the autoupdater...

… und weg isser

wusel · 26. Mai 2024 um 21:42

Eine Gluon v2023.2-basierte FW steht für Juni/Juli auf dem Plan …

Was das ist wüßte ich auch gerne …

Nächstes Mal bitte einen traceroute firmware.ipv6.4830.org machen — Smokeping sagt was anderes, siehe g01, g02, g03, g04. EDIT: Rückweg tut auch:

 root@web01 ~ # traceroute -6 -s 2a06:e881:1709:1111:0:57ff:fefd:bc94 2001:bf7:170:192:46d1:faff:fe5a:126f
 traceroute to 2001:bf7:170:192:46d1:faff:fe5a:126f (2001:bf7:170:192:46d1:faff:fe5a:126f), 30 hops max, 80 byte packets
  1  2a06:e881:1709:1111::2 (2a06:e881:1709:1111::2)  0.729 ms  0.652 ms  0.577 ms
  2  2a06:e881:1709:1111::1 (2a06:e881:1709:1111::1)  0.526 ms  0.476 ms  0.437 ms
  3  2a06:e881:1705:1391::2 (2a06:e881:1705:1391::2)  19.806 ms  19.776 ms  19.729 ms
  4  2a06:e881:1709:1::1 (2a06:e881:1709:1::1)  20.089 ms  19.866 ms  20.491 ms
  5  bgp-ber01.4830.org (2a06:e881:1706:1::1)  25.363 ms  25.285 ms  25.208 ms
  6  2a06:e881:1706:11:0:c2ff:fe71:3656 (2a06:e881:1706:11:0:c2ff:fe71:3656)  25.513 ms  29.780 ms  29.674 ms
  7  2001:bf7:170:192:46d1:faff:fe5a:126f (2001:bf7:170:192:46d1:faff:fe5a:126f)  54.008 ms  55.275 ms  55.247 ms

Was heißt »weg isser«? Für mich heißt das »aufgehängt und tut nix mehr«, wogegen https://map03.4830.org/map/#!v:m;n:44d1fa5a126f (»21 Stunden up, online, letzte Nachricht vor 2 Minuten (26.05.2024, 23:22:23)«) spricht …

m.bitterlich · 27. Mai 2024 um 11:49

Moin.

  OS: 19.07-SNAPSHOT, r11430+27-ecbbb3    FW: 1.4.0~121
  HW: Joy-IT JT-OR750i
root@17194-Joy-IT-126f:~# autoupdater
Retrieving manifest from http://firmware.ipv6.4830.org/rawhide/sysupgrade/rawhide.manifest ...
autoupdater: warning: error downloading manifest: Connection failed
autoupdater: error: no usable mirror found
root@17194-Joy-IT-126f:~# traceroute -6 firmware.ipv6.4830.org

traceroute: bad address 'firmware.ipv6.4830.org'
root@17194-Joy-IT-126f:~#
root@17194-Joy-IT-126f:~# host firmware.ipv6.4830.org
-ash: host: not found
root@17194-Joy-IT-126f:~# ping firmware.ipv6.4830.org
ping: bad address 'firmware.ipv6.4830.org'
root@17194-Joy-IT-126f:~#

Es sieht so aus, als ob der Knoten den DNS-Namen nicht auflösen kann.

Naja. OK… Ich war per SSH drauf und nach " /usr/sbin/autoupdater-wifi-fallback" war auch die Verbindung weg und es dauerte auch eine Weile, bis der Knoten wieder per SSH/HTTP/ping ansprechbar war.

m.bitterlich · 28. Mai 2024 um 19:31

Moin.
DNS ist etwas instabil.
Ich habe mehrere Knoten verteilt auf alle Gateway in Mesh5 getestet … im Moment kann ‚firmware.ipv6.4830.org‘ nicht mehr aufgelöst werden.

root@17194-Joy-IT-126f:~#
root@17194-Joy-IT-126f:~# ping firmware.ipv6.4830.org
PING firmware.ipv6.4830.org (2a06:e881:1709:1111:0:57ff:fefd:bc94): 56 data bytes
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=0 ttl=58 time=48.720 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=1 ttl=58 time=49.290 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=2 ttl=58 time=50.212 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=3 ttl=58 time=50.511 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=4 ttl=58 time=50.528 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=5 ttl=58 time=50.638 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=6 ttl=58 time=47.507 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=7 ttl=58 time=46.422 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=8 ttl=58 time=51.187 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=9 ttl=58 time=51.703 ms
64 bytes from 2a06:e881:1709:1111:0:57ff:fefd:bc94: seq=10 ttl=58 time=48.630 ms
^C
--- firmware.ipv6.4830.org ping statistics ---
11 packets transmitted, 11 packets received, 0% packet loss
round-trip min/avg/max = 46.422/49.577/51.703 ms
root@17194-Joy-IT-126f:~# ping firmware.ipv6.4830.org
ping: bad address 'firmware.ipv6.4830.org'
root@17194-Joy-IT-126f:~# ping firmware.ipv6.4830.org
ping: bad address 'firmware.ipv6.4830.org'
root@17194-Joy-IT-126f:~# ping firmware.ipv6.4830.org
ping: bad address 'firmware.ipv6.4830.org'
root@17194-Joy-IT-126f:~#

wusel · 28. Mai 2024 um 21:04

Danke für den Hinweis; ich guck’ mal, welche Resolver Knoten nutzen.

MichaelKliewe · 28. Mai 2024 um 21:52

Zonemaster meldet für 4830.org, dass 2 der Nameserver per IPv6 weder per UDP noch TCP erreichbar sind. Ist aber nur ein Nebenproblem, nicht das Hauptproblem?

https://zonemaster.net/en/result/098a55d0642385c1

MichaelKliewe · 28. Mai 2024 um 21:59

DNSViz spuckt auch noch einen Fehler aus zu firmware.ipv6.4830.org:

https://dnsviz.net/d/firmware.ipv6.4830.org/dnssec/

wusel · 29. Mai 2024 um 10:14

Hrmpft, vergessen, den auch in der Zone auszutragen, danke.

firmware.ipv6.4830.org | DNSViz moniert nun „nur“ noch

4830.org zone: The server(s) were not responsive to queries over UDP. (2a01:4f9:3b:5822:0:41ff:fe15:598a)

Das ist Hetzner Helsinki (dns-fks.uu.org), muß ich mal morgen in Ruhe gucken.

system · 8. Juni 2024 um 10:15

Dieses Thema wurde automatisch 10 Tage nach der letzten Antwort geschlossen. Es sind keine neuen Antworten mehr erlaubt.