Mein Knoten wird als offline angezeigt und Clients bekommen keine IP Adresse.
Per SSH kann ich mich anmelden, die SSID wird normal ausgesendet und ich habe den Router einmal durchgeschubst.
Mit dem Internet verbunden bin ich über IP V4+V6 im Telekom Netz.
Welche Informationen kann ich noch zum Troubleshooting liefern?
Er ist wieder da und verteilt IPs 
Hmm. Bei sowas wären u. a. batctl gwl interessant, auch logread | grep -i fastd.
Merke ich mir und schicke ich das nächste mal mit. Danke.
Nabend,
dann habe ich da was. Einer meiner Knoten ist seit heute morgen auch Offline und da ich keine Zeit hatte ihn neuzustarten hier die Ausgabe.
batctl gwl
Gateway (#/255) Nexthop [outgoingIF]: gw_class … [B.A.T.M.A.N. adv 2013.4.0, MainIF/MAC: primary0/1e:b2:a3:75:1a:2b (bat0)]
No gateways in range …
root@33397-Lu-Hollenbeck-1:~# logread | grep -i fastd
Mon Feb 26 19:41:36 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:41:36 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:41:51 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:41:51 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:41:51 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:41:53 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:42:09 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:42:09 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:42:09 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:42:14 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:42:30 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:42:30 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:42:30 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:42:33 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:42:33 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:42:33 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:42:35 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:42:35 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:42:35 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:42:52 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:42:52 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:42:52 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:42:54 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:42:54 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:42:54 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:42:55 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:42:55 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:42:55 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:43:12 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:43:12 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:43:12 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:43:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:43:14 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:43:14 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:43:18 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:43:18 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:43:18 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:43:34 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:43:34 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:43:34 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:43:35 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:43:35 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:43:35 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:43:37 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:43:37 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:43:37 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:43:56 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:43:57 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:43:57 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:43:57 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:44:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:44:14 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:44:14 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:44:15 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:44:15 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:44:15 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:44:19 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:44:19 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:44:19 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:44:34 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:44:38 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:44:38 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:44:38 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:44:53 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:44:53 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:44:53 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:44:55 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:44:55 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:44:55 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:44:56 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:44:56 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:44:56 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:45:11 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:45:11 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:45:11 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:45:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:45:14 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:45:14 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:45:18 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:45:18 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:45:18 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:45:33 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:45:33 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:45:33 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:45:36 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:45:51 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:45:51 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:45:51 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:45:54 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:45:54 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:45:54 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:45:56 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:45:56 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:45:56 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:46:12 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:46:12 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:46:12 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:46:14 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:46:14 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:46:14 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:46:18 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:46:18 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:46:18 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:46:33 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:46:33 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:46:33 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:46:35 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:46:35 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:46:35 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:46:38 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:46:39 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:46:39 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:46:53 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:46:53 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:46:53 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Mon Feb 26 19:46:56 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Mon Feb 26 19:46:56 2018 daemon.info fastd[1691]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Mon Feb 26 19:46:56 2018 daemon.info fastd[1691]: resolved hostgw-test01.4830.org’ successfully
Mon Feb 26 19:47:01 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Mon Feb 26 19:47:01 2018 daemon.info fastd[1691]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Mon Feb 26 19:47:01 2018 daemon.info fastd[1691]: resolved hostgw-event01.4830.org’ successfully
Mon Feb 26 19:47:11 2018 daemon.info fastd[1691]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Mon Feb 26 19:47:11 2018 daemon.info fastd[1691]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Mon Feb 26 19:47:11 2018 daemon.info fastd[1691]: resolved hostgw-event02.4830.org’ successfully
Hoffe das es weiter hilft.
Danke. Hmm, daß die zweite GW-Gruppe nicht zieht ist klar, davon ist keins aktuell oben. Dennoch sollte über die andere fastd-Peer-Gruppe eine Verbindug zu eine der GWs stehen, lt. batctl gwl ist dem aber nicht so. Sprich: die VPN-Verbindung ist weg, warumauchimmer. kopfkratz
root@33378-freifunk-a42bb0f43a87:~# batctl gwl
Gateway (#/255) Nexthop [outgoingIF]: gw_class … [B.A.T.M.A.N. adv 2013.4.0, MainIF/MAC: primary0/06:f2:c8:ea:c4:db (bat0)]
No gateways in range …
root@33378-freifunk-a42bb0f43a87:~# logread | grep -i fastd
Thu Mar 1 19:50:29 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:50:29 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:50:37 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:50:37 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:50:37 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:50:39 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:50:39 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:50:39 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:50:50 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:50:50 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:50:50 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:50:58 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:50:58 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:50:58 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:50:59 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:50:59 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:50:59 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:51:11 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:51:11 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:51:11 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:51:16 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:51:16 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:51:16 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:51:18 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:51:18 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:51:18 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:51:31 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:51:31 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:51:31 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:51:36 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:51:52 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:51:52 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:51:52 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:51:56 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:51:56 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:51:56 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:51:58 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:51:58 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:51:58 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:52:12 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:52:12 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:52:12 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:52:16 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:52:32 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:52:32 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:52:32 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:52:34 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:52:50 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:52:50 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:52:50 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:52:54 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:53:08 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:53:08 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:53:08 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:53:12 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:53:12 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:53:12 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:53:14 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:53:14 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:53:14 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:53:29 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:53:29 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:53:30 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:53:33 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:53:33 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:53:33 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:53:34 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:53:34 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:53:34 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:53:47 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:53:47 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:53:47 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:53:50 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:53:50 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:53:50 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:53:54 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:53:54 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:53:54 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:54:05 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:54:05 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:54:05 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:54:10 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:54:10 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:54:10 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:54:12 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:54:12 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:54:12 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:54:23 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:54:23 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:54:23 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:54:28 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:54:28 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:54:28 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:54:30 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:54:30 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:54:30 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:54:42 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:54:42 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:54:42 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:54:47 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:54:47 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:54:47 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:54:50 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:54:50 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:54:50 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:54:59 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:54:59 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:54:59 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:55:08 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:55:08 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:55:08 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:55:10 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:55:10 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:55:10 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:55:19 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:55:19 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:55:19 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:55:29 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:55:29 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:55:29 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
Thu Mar 1 19:55:32 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event02>[127.127.127.2:10000]…
Thu Mar 1 19:55:32 2018 daemon.info fastd[1876]: resolving hostgw-event02.4830.org' for peer <mesh_vpn_event_peer_event02>... Thu Mar 1 19:55:32 2018 daemon.info fastd[1876]: resolved hostgw-event02.4830.org’ successfully
Thu Mar 1 19:55:39 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_event01>[127.127.127.1:10000]…
Thu Mar 1 19:55:39 2018 daemon.info fastd[1876]: resolving hostgw-event01.4830.org' for peer <mesh_vpn_event_peer_event01>... Thu Mar 1 19:55:39 2018 daemon.info fastd[1876]: resolved hostgw-event01.4830.org’ successfully
Thu Mar 1 19:55:51 2018 daemon.info fastd[1876]: sending handshake to <mesh_vpn_event_peer_test01>[192.251.226.98:10000]…
Thu Mar 1 19:55:51 2018 daemon.info fastd[1876]: resolving hostgw-test01.4830.org' for peer <mesh_vpn_event_peer_test01>... Thu Mar 1 19:55:51 2018 daemon.info fastd[1876]: resolved hostgw-test01.4830.org’ successfully
root@33378-freifunk-a42bb0f43a87:~# ps |grep fastd
1876 root 3408 S /usr/bin/fastd --config - --daemon --pid-file /var/run/fastd.mesh_vpn.pid
25802 root 1384 S grep fastd
root@33378-freifunk-a42bb0f43a87:~# netstat -tulpn
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1633/uhttpd
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 1719/dnsmasq
tcp 0 0 0.0.0.0:54 0.0.0.0:* LISTEN 1734/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1206/dropbear
tcp 0 0 :::80 :::* LISTEN 1633/uhttpd
tcp 0 0 :::53 :::* LISTEN 1719/dnsmasq
tcp 0 0 :::54 :::* LISTEN 1734/dnsmasq
tcp 0 0 :::22 :::* LISTEN 1206/dropbear
udp 0 0 0.0.0.0:39425 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:42293 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:53 0.0.0.0:* 1719/dnsmasq
udp 0 0 0.0.0.0:54 0.0.0.0:* 1734/dnsmasq
udp 0 0 0.0.0.0:47703 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:48730 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:57235 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:53151 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:55720 0.0.0.0:* 1876/fastd
udp 0 0 0.0.0.0:36287 0.0.0.0:* 1876/fastd
udp 0 0 :::546 :::* 1472/odhcp6c
udp 0 0 :::546 :::* 1354/odhcp6c
udp 0 0 :::53 :::* 1719/dnsmasq
udp 0 0 :::54 :::* 1734/dnsmasq
udp 0 0 ff02::1:16962 :::* 1990/alfred
udp 0 0 fe80::a62b:b0ff:fef4:3a87:16962 :::* 1990/alfred
udp 0 0 :::33644 :::* 1876/fastd
udp 0 0 :::1001 :::* 2196/respondd
Hast du noch eine Idee was ich noch abfragen könnte? Haben den Knoten noch nicht neu gestartet
ein
/etc/init.d/fastd restart
half weiter.
Von daher gehe ich davon aus, dass der Tunnel nicht oben war, obwohl der Client lief.
Du hast doch mal irgendwas gebaut um mehr Lastverteilung über die GWs zu erreichen. Könnte da ein Zusammenhang bestehen?
Cool! Danke für’s ausprobieren!
Den Verdacht habe ich auch, aber warum tut’s manchmal/oft und gelegentlich nicht? 
Radio Eriwan, im Prinzip ja. Keine Ahnung, wie doof fastd wirklich ist; was gemacht wurde ist, für einige der in der Firmware hinterlegten Gateways …
"\"gw05.4830.org\" port 10000"
"\"gw04-neu.4830.org\" port 10000"
"\"gw02-neu.4830.org\" port 10000"
"\"gw03-neu.4830.org\" port 10000"
"\"gw01-neu.4830.org\" port 10000"
"\"gw06.4830.org\" port 10000"
"\"gw-test01.4830.org\" port 10000"
"\"gw-event02.4830.org\" port 10000"
"\"gw-event01.4830.org\" port 10000"
… z. T. mehrere IPs einzutragen:
gw05.4830.org has address 148.251.168.162
gw05.4830.org has IPv6 address 2a01:4f8:191:6323::1:5
gw04-neu.4830.org has address 192.251.226.26
gw04-neu.4830.org has address 192.251.226.68
gw04-neu.4830.org has address 192.251.226.69
gw04-neu.4830.org has address 192.251.226.109
gw02-neu.4830.org has address 192.251.226.101
gw02-neu.4830.org has address 192.251.226.17
gw03-neu.4830.org has address 192.251.226.18
gw01-neu.4830.org has address 192.251.226.16
gw01-neu.4830.org has address 192.251.226.5
gw06.4830.org has address 192.251.226.99
Um die Fehlermeldungen wg. der nicht erreichbaren “event”-Gateways loszuwerden, wurden dort ggf. 127er IPs eingetragen:
gw-test01.4830.org has address 192.251.226.98
gw-event02.4830.org has address 127.127.127.2
gw-event01.4830.org has address 127.127.127.1
Ich werden dann mal gw-event01 installieren und für die nächste FW das ganz rauswerfen … sigh
Kann es sein das Fastd an den Host sendet und wenn nach einer Zeit eine andere IP vom DNS aufgelöst wird, ist der Client die Daten an die falsche IP sendet ohne den Tunnel neu aufzubauen?
Nicht, wenn fastd mit etwas Verstand zusammengeschraubt wurde. Normalerweile löst man den Namen zu einer IP (oder mehreren) auf und nimmt dann diese IP für die Verbindung. Namen werden technisch nur als Platzhalter für IPs genutzt, technisch wird immer zwischen zwei IP-Adressen (und, bei UDP/TCP, Ports) eine Verbindung aufgebaut. Bei einem Fehler geht man dann eigentlich zurück auf Los: Name zu Nummer auflösen, Verbindung herstellen, …
Ich hab jetzt mal etwas experimentiert. Mein Router war an gw03 konnektiert.
Name: gw03.4830.org
Address 1: 2a06:e881:1700:1:400:c0ff:fefb:e212
Address 2: 192.251.226.18
die IPv4 Adresse habe ich “geeredet”:
$ ip route 192.251.226.18 gw 127.0.0.2
Der Knoten fällt aus dem Netz. http://map.4830.org/#!v:m;n:e894f66304a2
Strahlt aber trotzdem “KreisGT.Freifunk.net” aus.
Fehlermeldung im Log:
Fri Mar 2 21:20:01 2018 user.notice gluon-ssid-changer: There is something wrong (2): did neither find SSID KreisGT.freifunk.net nor FF_OFFLINE_e894f66304a2
Das wäre schon mal etwas was wir nicht wollen.
Schön wäre es nun, wenn der fastd begreift das gw03 nicht mehr erreichbar ist, und einen der anderen GWs nimmt. Tut er nicht. Erst nach einem fastd-Restart startet der connect und das Ding ist über gw02 wieder erreichbar.
Fri Mar 2 21:33:11 2018 daemon.info fastd[10826]: sending handshake to <mesh_vpn_backbone_peer_gw02>[192.251.226.101:10000]...
Fri Mar 2 21:33:11 2018 daemon.info fastd[10826]: received handshake response from <mesh_vpn_backbone_peer_gw02>[192.251.226.101:10000] using fastd v17
Fri Mar 2 21:33:11 2018 daemon.info fastd[10826]: 192.251.226.101:10000 authorized as <mesh_vpn_backbone_peer_gw02>
Fri Mar 2 21:33:11 2018 daemon.notice fastd[10826]: connection with <mesh_vpn_backbone_peer_gw02> established.
Fri Mar 2 21:33:11 2018 daemon.info fastd[10826]: new session with <mesh_vpn_backbone_peer_gw02> established using method `salsa2012+umac'.
Soweit ich sehen konnte reconnected fastd auch nicht erneut an einen GW wenn der zwischenzeitlich nicht erreichbar war.
nach dem fastd restart, dem connect an gw02 und dem erden von gw02 hat der fastd diesmal anstandslos auf gw01 umgeschwenkt…
in einem weiteren Versuch wieder nicht.
Danke, das paßt zum Fehlerbild. Lt. Doku sollte es mit mehreren IPs pro FQDN funktionieren, aber augenscheinlich tut’s dann doch nicht so Dann wird’s wohl eine neue FW geben müssen, die mit neuen FQDNs, die nur noch auf jeweils 1 IP auflösen, arbeitet. Denn die hohe Zahl ausgefallener Knoten korreliert schon erstaunlich gut mit der Erweiterung der Hostnamen (FQDNs) um weitere IPs für weitere Gateways …
1 „Gefällt mir“
Super das das Problem eingegrenzt werden konnte. Danke schön.
Hallo
Eine kleine Info zur Zeitlichen Eingrenzung.
Bei unserer Sonntagstour sind mir Knoten aufgefallen die das Freifunk Netz ausstrahlen, die aber garnicht mehr in der Karte sind. Ich Demnach muss das Problem schon seit über zwei Wochen bestehen.
Hallo! Du (Kai ‘wusel’ Siering) hast geschrieben:
Ich meine, daß erst nach dem DNS-Change das Netz ›komisch‹ wurde …
könnte man nicht den RR von gw04 auflösen und die
derzeit nicht laufenden gws (gw-event*)-DNS-EIntr�äge mit
den Kisten aktivieren, anstatt die ins Nirvana zu schicken?
Ich befürchte die ausgefallen GWs müssen jeweils
restarted werden, damit sie sich wieder konnektieren. Von selbst wirds
ja offenbar nicht wieder besser.
Cord
Neuer Anlauf …
[quote]
-------- Weitergeleitete Nachricht --------