Habe ich auch schon durchgeführt, einmal habe ich die Konfiguration beibehalten, das zweite mal komplett neu konfiguriert.(die 1.0)
Ich habe jetzt mal einfach die 0.9 installiert und den Autoupdater ausgeschaltet. Funktioniert ohne alles Probleme, auf allen Geräten. Verbindungen aktiviert und deaktiviert, bekomme immer die IPs zugewiesen. Seitenaufbau geht ohne Probleme, Pings gehen durch.
PING google.com (2a00:1450:4001:817::200e): 56 data bytes 64 bytes from 2a00:1450:4001:817::200e: seq=0 ttl=56 time=68.521 ms 64 bytes from 2a00:1450:4001:817::200e: seq=1 ttl=56 time=67.380 ms 64 bytes from 2a00:1450:4001:817::200e: seq=2 ttl=56 time=67.871 ms 64 bytes from 2a00:1450:4001:817::200e: seq=3 ttl=56 time=67.676 ms 64 bytes from 2a00:1450:4001:817::200e: seq=4 ttl=56 time=66.641 ms 64 bytes from 2a00:1450:4001:817::200e: seq=5 ttl=56 time=67.254 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 66.641/67.557/68.521 ms
PING default02.ffnw.de (2001:4ba0:fffa:23::): 56 data bytes 64 bytes from 2001:4ba0:fffa:23::: seq=0 ttl=54 time=75.894 ms 64 bytes from 2001:4ba0:fffa:23::: seq=1 ttl=54 time=78.235 ms 64 bytes from 2001:4ba0:fffa:23::: seq=2 ttl=54 time=76.116 ms 64 bytes from 2001:4ba0:fffa:23::: seq=3 ttl=54 time=77.905 ms 64 bytes from 2001:4ba0:fffa:23::: seq=4 ttl=54 time=75.721 ms 64 bytes from 2001:4ba0:fffa:23::: seq=5 ttl=54 time=93.088 ms
--- default02.ffnw.de ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 75.721/79.493/93.088 ms
Aber wie gesagt, mit der 0.9!
Am 5. Juni 2016 um 00:54 schrieb Stefan stefan@osnabrueck.freifunk.net:
Und soetwas wie srv12.ffnw.de kann er nicht auflösen? Hast du den router mal frisch geflashed?
Am 5. Juni 2016 00:48:52 MESZ, schrieb Viktor Grosch <grosch@novashape.de
:
PING google.com (216.58.213.238): 56 data bytes 64 bytes from 216.58.213.238: seq=0 ttl=54 time=27.681 ms 64 bytes from 216.58.213.238: seq=1 ttl=54 time=26.333 ms 64 bytes from 216.58.213.238: seq=2 ttl=54 time=26.781 ms 64 bytes from 216.58.213.238: seq=3 ttl=54 time=26.328 ms 64 bytes from 216.58.213.238: seq=4 ttl=54 time=26.591 ms 64 bytes from 216.58.213.238: seq=5 ttl=54 time=26.497 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 26.328/26.701/27.681 ms
ping: bad address 'default02.ffnw.de'
Am 5. Juni 2016 um 00:03 schrieb Stefan stefan@osnabrueck.freifunk.net:
Der Router bekommt nur kein DNS. Weise doch mal per configmode statisch dns zu
Am 4. Juni 2016 23:55:19 MESZ, schrieb Viktor Grosch < grosch@novashape.de>:
Was vergessen.
PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=53 time=27.323 ms 64 bytes from 8.8.8.8: seq=1 ttl=53 time=26.596 ms 64 bytes from 8.8.8.8: seq=2 ttl=53 time=27.029 ms 64 bytes from 8.8.8.8: seq=3 ttl=53 time=26.458 ms 64 bytes from 8.8.8.8: seq=4 ttl=53 time=26.064 ms 64 bytes from 8.8.8.8: seq=5 ttl=53 time=25.851 ms
Am 4. Juni 2016 um 23:38 schrieb Viktor Grosch grosch@novashape.de:
Nein, ist ein Telekom Anschluss. Alles außer Freifunk läuft ohne Probleme, auch mit den zugewiesen DNS Daten vom Provider. Wie bereits geschrieben tritt das Problem an zwei Standorten auf (Internet-Zugang an beiden von der Telekom)
Am 4. Juni 2016 um 23:20 schrieb Stefan < stefan@osnabrueck.freifunk.net>:
Dsnn Ping mal 8.8.8.8
Zufällig ein KD Anschluss? Dein Router bekommt kein DNS von deinem Anschluss
Am 4. Juni 2016 23:19:00 MESZ, schrieb Viktor Grosch < grosch@novashape.de>: > > Nein, leider nicht > > ping: bad address 'default02.ffnw.de' > > > Am 4. Juni 2016 um 23:04 schrieb Stefan < > stefan@osnabrueck.freifunk.net>: > >> Der Router hat kein VPN - kannst du von dem Router unsere Gateways ( >> default02.ffnw.de bspw) pingen? >> >> >> Am 4. Juni 2016 22:57:34 MESZ, schrieb Viktor Grosch < >> grosch@novashape.de>: >>> >>> >>> No VPN connection found >>> Testing neighboring adhoc networks for batman advanced gw >>> connection. >>> The following wireless networks have been found: >>> 0 2462 C0:25:06:21:85:A3 Skynet >>> 46 2412 34:81:C4:E1:0F:AE FRITZ!Box 7362 SL >>> After filtering we will test the following wireless networks: >>> No neighboring freifunk batman advanced mesh found. >>> Set hood "default" >>> Set defaulthood. >>> >>> >>> Am 4. Juni 2016 um 22:28 schrieb Stefan < >>> stefan@osnabrueck.freifunk.net>: >>> >>>> Hey, >>>> >>>> ist er da denn online gekommen? >>>> Wenn nein, führe mal.per ssh "hoodselector" aus >>>> >>>> >>>> Am 4. Juni 2016 21:56:48 MESZ, schrieb Viktor Grosch < >>>> grosch@novashape.de>: >>>>> >>>>> Der Router ist jetzt in WHV mit den manuell eingetragenen >>>>> Koordinaten von Hooksiel. >>>>> >>>>> >>>>> Am 4. Juni 2016 um 21:06 schrieb Stefan < >>>>> stefan@osnabrueck.freifunk.net>: >>>>> >>>>>> Hi, >>>>>> >>>>>> da scheinen grade die VPN Peers voll zu sein. >>>>>> Wo stehen die Router genau? Hooksiel landet mit richtigen >>>>>> Koordinaten in einer Hood.... da läuft es >>>>>> >>>>>> >>>>>> Am 4. Juni 2016 20:57:29 MESZ, schrieb Viktor Grosch < >>>>>> grosch@novashape.de>: >>>>>>> >>>>>>> FW 1.0 ist drauf. >>>>>>> >>>>>>> logread: >>>>>>> >>>>>>> Sat Jun 4 20:51:17 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0: STA >>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: authenticated >>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0: STA >>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: associated (aid 1) >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:51:42 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:51:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:51:55 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:24 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:52:34 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:52:35 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:01 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:53:09 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:53:12 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:53:13 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:53:14 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:53:38 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:53:51 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:19 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:54:30 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:54:32 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:54:33 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:54:34 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> Sat Jun 4 20:55:11 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>> Sat Jun 4 20:55:12 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>> Sat Jun 4 20:55:13 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>> Sat Jun 4 20:55:14 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default04.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default04.ffnw.de' successfully >>>>>>> Sat Jun 4 20:55:18 2016 authpriv.info dropbear[20682]: Child >>>>>>> connection from fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default05.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default05.ffnw.de' successfully >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default03.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default03.ffnw.de' successfully >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default02.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default02.ffnw.de' successfully >>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>> ]... >>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: resolving >>>>>>> host `default06.ffnw.de' for peer >>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: resolved >>>>>>> host `default06.ffnw.de' successfully >>>>>>> Sat Jun 4 20:55:36 2016 authpriv.notice dropbear[20682]: >>>>>>> Pubkey auth succeeded for 'root' with key md5 >>>>>>> af:61:57:d4:a7:b3:e7:22:cc:91:16:24:4b:28:ad:c2 from >>>>>>> fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>> Sat Jun 4 20:55:37 2016 daemon.info fastd[19930]: sending >>>>>>> handshake to >>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>> >>>>>>> >>>>>>> Am 4. Juni 2016 um 19:55 schrieb Stefan < >>>>>>> stefan@osnabrueck.freifunk.net>: >>>>>>> >>>>>>>> Hallo Viktor, >>>>>>>> >>>>>>>> Sind die Router auf FW 1.0? >>>>>>>> Magst du per ssh einmal die Ausgabe von logread hier posten? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Am 4. Juni 2016 19:44:52 MESZ, schrieb Viktor Grosch via >>>>>>>> Nordwest nordwest@lists.ffnw.de: >>>>>>>> >>>>>>>>> Hallo, >>>>>>>>> ich kann keine Verbindung aufbauen, bzw bekomme keine IP >>>>>>>>> Adressen zugewiesen zugewiesenen. >>>>>>>>> Ich habe es in Hooksiel und Wilhelmshaven einzelt getestet, >>>>>>>>> mit TPLINK 4300, 850RE und 860RE, an beiden Standorten. Konfiguration wurde >>>>>>>>> nicht verändert. >>>>>>>>> >>>>>>>>> Liegen aktuell Störungen vor oder weiß einer woran es liegen >>>>>>>>> kann. >>>>>>>>> >>>>>>>>> Schöne Grüße >>>>>>>>> >>>>>>>>> Viktor >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> Nordwest mailing list >>>>>>>>> Nordwest@lists.ffnw.de >>>>>>>>> https://lists.ffnw.de/mailman/listinfo/nordwest >>>>>>>>> >>>>>>>>> >>>>>>>> -- >>>>>>>> vg >>>>>>>> Stefan >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Schöne Grüße >>>>>>> >>>>>>> Viktor Grosch >>>>>>> >>>>>> >>>>>> -- >>>>>> vg >>>>>> Stefan >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Schöne Grüße >>>>> >>>>> Viktor Grosch >>>>> >>>> >>>> -- >>>> vg >>>> Stefan >>>> >>> >>> >>> >>> -- >>> Schöne Grüße >>> >>> Viktor Grosch >>> >> >> -- >> vg >> Stefan >> > > > > -- > Schöne Grüße > > Viktor Grosch >
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
Hey,
du müsstest mit der 1.0 im gleichen Netz sogar landen. Mehr als 1200 router bekommen das hin.
Ist das ein Anschluss mit geringer Bandbreite?
Am 5. Juni 2016 02:17:31 MESZ, schrieb Viktor Grosch via Nordwest nordwest@lists.ffnw.de:
Habe ich auch schon durchgeführt, einmal habe ich die Konfiguration beibehalten, das zweite mal komplett neu konfiguriert.(die 1.0)
Ich habe jetzt mal einfach die 0.9 installiert und den Autoupdater ausgeschaltet. Funktioniert ohne alles Probleme, auf allen Geräten. Verbindungen aktiviert und deaktiviert, bekomme immer die IPs zugewiesen. Seitenaufbau geht ohne Probleme, Pings gehen durch.
PING google.com (2a00:1450:4001:817::200e): 56 data bytes 64 bytes from 2a00:1450:4001:817::200e: seq=0 ttl=56 time=68.521 ms 64 bytes from 2a00:1450:4001:817::200e: seq=1 ttl=56 time=67.380 ms 64 bytes from 2a00:1450:4001:817::200e: seq=2 ttl=56 time=67.871 ms 64 bytes from 2a00:1450:4001:817::200e: seq=3 ttl=56 time=67.676 ms 64 bytes from 2a00:1450:4001:817::200e: seq=4 ttl=56 time=66.641 ms 64 bytes from 2a00:1450:4001:817::200e: seq=5 ttl=56 time=67.254 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 66.641/67.557/68.521 ms
PING default02.ffnw.de (2001:4ba0:fffa:23::): 56 data bytes 64 bytes from 2001:4ba0:fffa:23::: seq=0 ttl=54 time=75.894 ms 64 bytes from 2001:4ba0:fffa:23::: seq=1 ttl=54 time=78.235 ms 64 bytes from 2001:4ba0:fffa:23::: seq=2 ttl=54 time=76.116 ms 64 bytes from 2001:4ba0:fffa:23::: seq=3 ttl=54 time=77.905 ms 64 bytes from 2001:4ba0:fffa:23::: seq=4 ttl=54 time=75.721 ms 64 bytes from 2001:4ba0:fffa:23::: seq=5 ttl=54 time=93.088 ms
--- default02.ffnw.de ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 75.721/79.493/93.088 ms
Aber wie gesagt, mit der 0.9!
Am 5. Juni 2016 um 00:54 schrieb Stefan stefan@osnabrueck.freifunk.net:
Und soetwas wie srv12.ffnw.de kann er nicht auflösen? Hast du den
router
mal frisch geflashed?
Am 5. Juni 2016 00:48:52 MESZ, schrieb Viktor Grosch
<grosch@novashape.de
:
PING google.com (216.58.213.238): 56 data bytes 64 bytes from 216.58.213.238: seq=0 ttl=54 time=27.681 ms 64 bytes from 216.58.213.238: seq=1 ttl=54 time=26.333 ms 64 bytes from 216.58.213.238: seq=2 ttl=54 time=26.781 ms 64 bytes from 216.58.213.238: seq=3 ttl=54 time=26.328 ms 64 bytes from 216.58.213.238: seq=4 ttl=54 time=26.591 ms 64 bytes from 216.58.213.238: seq=5 ttl=54 time=26.497 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 26.328/26.701/27.681 ms
ping: bad address 'default02.ffnw.de'
Am 5. Juni 2016 um 00:03 schrieb Stefan
stefan@osnabrueck.freifunk.net:
Der Router bekommt nur kein DNS. Weise doch mal per configmode statisch dns zu
Am 4. Juni 2016 23:55:19 MESZ, schrieb Viktor Grosch < grosch@novashape.de>:
Was vergessen.
PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=53 time=27.323 ms 64 bytes from 8.8.8.8: seq=1 ttl=53 time=26.596 ms 64 bytes from 8.8.8.8: seq=2 ttl=53 time=27.029 ms 64 bytes from 8.8.8.8: seq=3 ttl=53 time=26.458 ms 64 bytes from 8.8.8.8: seq=4 ttl=53 time=26.064 ms 64 bytes from 8.8.8.8: seq=5 ttl=53 time=25.851 ms
Am 4. Juni 2016 um 23:38 schrieb Viktor Grosch
Nein, ist ein Telekom Anschluss. Alles außer Freifunk läuft ohne Probleme, auch mit den zugewiesen DNS Daten vom Provider. Wie bereits geschrieben tritt das Problem an zwei Standorten auf (Internet-Zugang an beiden von der Telekom)
Am 4. Juni 2016 um 23:20 schrieb Stefan < stefan@osnabrueck.freifunk.net>:
> Dsnn Ping mal 8.8.8.8 > > Zufällig ein KD Anschluss? Dein Router bekommt kein DNS von
deinem
> Anschluss > > Am 4. Juni 2016 23:19:00 MESZ, schrieb Viktor Grosch < > grosch@novashape.de>: >> >> Nein, leider nicht >> >> ping: bad address 'default02.ffnw.de' >> >> >> Am 4. Juni 2016 um 23:04 schrieb Stefan < >> stefan@osnabrueck.freifunk.net>: >> >>> Der Router hat kein VPN - kannst du von dem Router unsere
Gateways (
>>> default02.ffnw.de bspw) pingen? >>> >>> >>> Am 4. Juni 2016 22:57:34 MESZ, schrieb Viktor Grosch < >>> grosch@novashape.de>: >>>> >>>> >>>> No VPN connection found >>>> Testing neighboring adhoc networks for batman advanced gw >>>> connection. >>>> The following wireless networks have been found: >>>> 0 2462 C0:25:06:21:85:A3 Skynet >>>> 46 2412 34:81:C4:E1:0F:AE FRITZ!Box 7362 SL >>>> After filtering we will test the following wireless networks: >>>> No neighboring freifunk batman advanced mesh found. >>>> Set hood "default" >>>> Set defaulthood. >>>> >>>> >>>> Am 4. Juni 2016 um 22:28 schrieb Stefan < >>>> stefan@osnabrueck.freifunk.net>: >>>> >>>>> Hey, >>>>> >>>>> ist er da denn online gekommen? >>>>> Wenn nein, führe mal.per ssh "hoodselector" aus >>>>> >>>>> >>>>> Am 4. Juni 2016 21:56:48 MESZ, schrieb Viktor Grosch < >>>>> grosch@novashape.de>: >>>>>> >>>>>> Der Router ist jetzt in WHV mit den manuell eingetragenen >>>>>> Koordinaten von Hooksiel. >>>>>> >>>>>> >>>>>> Am 4. Juni 2016 um 21:06 schrieb Stefan < >>>>>> stefan@osnabrueck.freifunk.net>: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> da scheinen grade die VPN Peers voll zu sein. >>>>>>> Wo stehen die Router genau? Hooksiel landet mit richtigen >>>>>>> Koordinaten in einer Hood.... da läuft es >>>>>>> >>>>>>> >>>>>>> Am 4. Juni 2016 20:57:29 MESZ, schrieb Viktor Grosch < >>>>>>> grosch@novashape.de>: >>>>>>>> >>>>>>>> FW 1.0 ist drauf. >>>>>>>> >>>>>>>> logread: >>>>>>>> >>>>>>>> Sat Jun 4 20:51:17 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0:
STA
>>>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: authenticated >>>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0:
STA
>>>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: associated (aid 1) >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:51:42 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:51:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:51:55 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:24 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:52:34 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:52:35 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:01 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:53:09 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:53:12 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:53:13 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:53:14 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:53:38 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:53:51 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:19 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:54:30 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:54:32 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:54:33 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:54:34 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> Sat Jun 4 20:55:11 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]...
>>>>>>>> Sat Jun 4 20:55:12 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]...
>>>>>>>> Sat Jun 4 20:55:13 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]...
>>>>>>>> Sat Jun 4 20:55:14 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]...
>>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default04>[5.104.106.134:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default04.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:55:18 2016 authpriv.info dropbear[20682]:
Child
>>>>>>>> connection from fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default05>[188.40.140.188:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default05.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default03>[37.120.164.49:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default03.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default02>[5.104.106.218:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default02.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to
<mesh_vpn_backbone_peer_default06>[188.40.140.187:11111
>>>>>>>> ]... >>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]:
resolving
>>>>>>>> host `default06.ffnw.de' for peer >>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]:
resolved
>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>> Sat Jun 4 20:55:36 2016 authpriv.notice dropbear[20682]: >>>>>>>> Pubkey auth succeeded for 'root' with key md5 >>>>>>>> af:61:57:d4:a7:b3:e7:22:cc:91:16:24:4b:28:ad:c2 from >>>>>>>> fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>>> Sat Jun 4 20:55:37 2016 daemon.info fastd[19930]:
sending
>>>>>>>> handshake to >>>>>>>>
<mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]...
>>>>>>>> >>>>>>>> >>>>>>>> Am 4. Juni 2016 um 19:55 schrieb Stefan < >>>>>>>> stefan@osnabrueck.freifunk.net>: >>>>>>>> >>>>>>>>> Hallo Viktor, >>>>>>>>> >>>>>>>>> Sind die Router auf FW 1.0? >>>>>>>>> Magst du per ssh einmal die Ausgabe von logread hier
posten?
>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 4. Juni 2016 19:44:52 MESZ, schrieb Viktor Grosch via >>>>>>>>> Nordwest nordwest@lists.ffnw.de: >>>>>>>>> >>>>>>>>>> Hallo, >>>>>>>>>> ich kann keine Verbindung aufbauen, bzw bekomme keine
IP
>>>>>>>>>> Adressen zugewiesen zugewiesenen. >>>>>>>>>> Ich habe es in Hooksiel und Wilhelmshaven einzelt
getestet,
>>>>>>>>>> mit TPLINK 4300, 850RE und 860RE, an beiden Standorten.
Konfiguration wurde
>>>>>>>>>> nicht verändert. >>>>>>>>>> >>>>>>>>>> Liegen aktuell Störungen vor oder weiß einer woran es
liegen
>>>>>>>>>> kann. >>>>>>>>>> >>>>>>>>>> Schöne Grüße >>>>>>>>>> >>>>>>>>>> Viktor >>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> Nordwest mailing list >>>>>>>>>> Nordwest@lists.ffnw.de >>>>>>>>>> https://lists.ffnw.de/mailman/listinfo/nordwest >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> vg >>>>>>>>> Stefan >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Schöne Grüße >>>>>>>> >>>>>>>> Viktor Grosch >>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> vg >>>>>>> Stefan >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Schöne Grüße >>>>>> >>>>>> Viktor Grosch >>>>>> >>>>> >>>>> -- >>>>> vg >>>>> Stefan >>>>> >>>> >>>> >>>> >>>> -- >>>> Schöne Grüße >>>> >>>> Viktor Grosch >>>> >>> >>> -- >>> vg >>> Stefan >>> >> >> >> >> -- >> Schöne Grüße >> >> Viktor Grosch >> > > -- > vg > Stefan >
-- Schöne Grüße
Viktor Grosch
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
DSL 16000 an beiden Standorten. Keine Bandbreiten- und Portlimitierung. Habe heute nacht den WA860RE zurück auf 0.9 geflasht, das gleiche Phänomen. Mit der 1.0 läuft es nicht, die 0.9 läuft ohne Probleme.
Am 5. Juni 2016 um 12:38 schrieb Stefan stefan@osnabrueck.freifunk.net:
Hey,
du müsstest mit der 1.0 im gleichen Netz sogar landen. Mehr als 1200 router bekommen das hin.
Ist das ein Anschluss mit geringer Bandbreite?
Am 5. Juni 2016 02:17:31 MESZ, schrieb Viktor Grosch via Nordwest < nordwest@lists.ffnw.de>:
Habe ich auch schon durchgeführt, einmal habe ich die Konfiguration beibehalten, das zweite mal komplett neu konfiguriert.(die 1.0)
Ich habe jetzt mal einfach die 0.9 installiert und den Autoupdater ausgeschaltet. Funktioniert ohne alles Probleme, auf allen Geräten. Verbindungen aktiviert und deaktiviert, bekomme immer die IPs zugewiesen. Seitenaufbau geht ohne Probleme, Pings gehen durch.
PING google.com (2a00:1450:4001:817::200e): 56 data bytes 64 bytes from 2a00:1450:4001:817::200e: seq=0 ttl=56 time=68.521 ms 64 bytes from 2a00:1450:4001:817::200e: seq=1 ttl=56 time=67.380 ms 64 bytes from 2a00:1450:4001:817::200e: seq=2 ttl=56 time=67.871 ms 64 bytes from 2a00:1450:4001:817::200e: seq=3 ttl=56 time=67.676 ms 64 bytes from 2a00:1450:4001:817::200e: seq=4 ttl=56 time=66.641 ms 64 bytes from 2a00:1450:4001:817::200e: seq=5 ttl=56 time=67.254 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 66.641/67.557/68.521 ms
PING default02.ffnw.de (2001:4ba0:fffa:23::): 56 data bytes 64 bytes from 2001:4ba0:fffa:23::: seq=0 ttl=54 time=75.894 ms 64 bytes from 2001:4ba0:fffa:23::: seq=1 ttl=54 time=78.235 ms 64 bytes from 2001:4ba0:fffa:23::: seq=2 ttl=54 time=76.116 ms 64 bytes from 2001:4ba0:fffa:23::: seq=3 ttl=54 time=77.905 ms 64 bytes from 2001:4ba0:fffa:23::: seq=4 ttl=54 time=75.721 ms 64 bytes from 2001:4ba0:fffa:23::: seq=5 ttl=54 time=93.088 ms
--- default02.ffnw.de ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 75.721/79.493/93.088 ms
Aber wie gesagt, mit der 0.9!
Am 5. Juni 2016 um 00:54 schrieb Stefan stefan@osnabrueck.freifunk.net:
Und soetwas wie srv12.ffnw.de kann er nicht auflösen? Hast du den router mal frisch geflashed?
Am 5. Juni 2016 00:48:52 MESZ, schrieb Viktor Grosch < grosch@novashape.de>:
PING google.com (216.58.213.238): 56 data bytes 64 bytes from 216.58.213.238: seq=0 ttl=54 time=27.681 ms 64 bytes from 216.58.213.238: seq=1 ttl=54 time=26.333 ms 64 bytes from 216.58.213.238: seq=2 ttl=54 time=26.781 ms 64 bytes from 216.58.213.238: seq=3 ttl=54 time=26.328 ms 64 bytes from 216.58.213.238: seq=4 ttl=54 time=26.591 ms 64 bytes from 216.58.213.238: seq=5 ttl=54 time=26.497 ms
--- google.com ping statistics --- 6 packets transmitted, 6 packets received, 0% packet loss round-trip min/avg/max = 26.328/26.701/27.681 ms
ping: bad address 'default02.ffnw.de'
Am 5. Juni 2016 um 00:03 schrieb Stefan <stefan@osnabrueck.freifunk.net
:
Der Router bekommt nur kein DNS. Weise doch mal per configmode statisch dns zu
Am 4. Juni 2016 23:55:19 MESZ, schrieb Viktor Grosch < grosch@novashape.de>:
Was vergessen.
PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: seq=0 ttl=53 time=27.323 ms 64 bytes from 8.8.8.8: seq=1 ttl=53 time=26.596 ms 64 bytes from 8.8.8.8: seq=2 ttl=53 time=27.029 ms 64 bytes from 8.8.8.8: seq=3 ttl=53 time=26.458 ms 64 bytes from 8.8.8.8: seq=4 ttl=53 time=26.064 ms 64 bytes from 8.8.8.8: seq=5 ttl=53 time=25.851 ms
Am 4. Juni 2016 um 23:38 schrieb Viktor Grosch grosch@novashape.de:
> Nein, ist ein Telekom Anschluss. Alles außer Freifunk läuft ohne > Probleme, auch mit den zugewiesen DNS Daten vom Provider. > Wie bereits geschrieben tritt das Problem an zwei Standorten auf > (Internet-Zugang an beiden von der Telekom) > > Am 4. Juni 2016 um 23:20 schrieb Stefan < > stefan@osnabrueck.freifunk.net>: > >> Dsnn Ping mal 8.8.8.8 >> >> Zufällig ein KD Anschluss? Dein Router bekommt kein DNS von deinem >> Anschluss >> >> Am 4. Juni 2016 23:19:00 MESZ, schrieb Viktor Grosch < >> grosch@novashape.de>: >>> >>> Nein, leider nicht >>> >>> ping: bad address 'default02.ffnw.de' >>> >>> >>> Am 4. Juni 2016 um 23:04 schrieb Stefan < >>> stefan@osnabrueck.freifunk.net>: >>> >>>> Der Router hat kein VPN - kannst du von dem Router unsere >>>> Gateways (default02.ffnw.de bspw) pingen? >>>> >>>> >>>> Am 4. Juni 2016 22:57:34 MESZ, schrieb Viktor Grosch < >>>> grosch@novashape.de>: >>>>> >>>>> >>>>> No VPN connection found >>>>> Testing neighboring adhoc networks for batman advanced gw >>>>> connection. >>>>> The following wireless networks have been found: >>>>> 0 2462 C0:25:06:21:85:A3 Skynet >>>>> 46 2412 34:81:C4:E1:0F:AE FRITZ!Box 7362 SL >>>>> After filtering we will test the following wireless networks: >>>>> No neighboring freifunk batman advanced mesh found. >>>>> Set hood "default" >>>>> Set defaulthood. >>>>> >>>>> >>>>> Am 4. Juni 2016 um 22:28 schrieb Stefan < >>>>> stefan@osnabrueck.freifunk.net>: >>>>> >>>>>> Hey, >>>>>> >>>>>> ist er da denn online gekommen? >>>>>> Wenn nein, führe mal.per ssh "hoodselector" aus >>>>>> >>>>>> >>>>>> Am 4. Juni 2016 21:56:48 MESZ, schrieb Viktor Grosch < >>>>>> grosch@novashape.de>: >>>>>>> >>>>>>> Der Router ist jetzt in WHV mit den manuell eingetragenen >>>>>>> Koordinaten von Hooksiel. >>>>>>> >>>>>>> >>>>>>> Am 4. Juni 2016 um 21:06 schrieb Stefan < >>>>>>> stefan@osnabrueck.freifunk.net>: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> da scheinen grade die VPN Peers voll zu sein. >>>>>>>> Wo stehen die Router genau? Hooksiel landet mit richtigen >>>>>>>> Koordinaten in einer Hood.... da läuft es >>>>>>>> >>>>>>>> >>>>>>>> Am 4. Juni 2016 20:57:29 MESZ, schrieb Viktor Grosch < >>>>>>>> grosch@novashape.de>: >>>>>>>>> >>>>>>>>> FW 1.0 ist drauf. >>>>>>>>> >>>>>>>>> logread: >>>>>>>>> >>>>>>>>> Sat Jun 4 20:51:17 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:51:22 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0: STA >>>>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: authenticated >>>>>>>>> Sat Jun 4 20:51:31 2016 daemon.info hostapd: client0: STA >>>>>>>>> f4:f2:6d:1a:c7:e3 IEEE 802.11: associated (aid 1) >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:51:32 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:51:35 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:51:36 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:51:42 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:51:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:51:54 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:51:55 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:52:02 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:52:12 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:52:13 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:52:16 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:24 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:52:31 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:52:34 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:52:35 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:52:43 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:52:49 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:52:50 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:52:53 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:01 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:53:09 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:53:12 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:53:13 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:53:14 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:53:19 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:53:30 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:53:31 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:53:32 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:53:33 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:53:38 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:53:51 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:53:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:53:57 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:54:09 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:54:12 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:54:13 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:19 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:54:30 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:54:32 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:54:33 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:54:34 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:54:37 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:54:50 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:54:51 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:54:53 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:54:55 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> Sat Jun 4 20:55:11 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default02>[[2001:4ba0:fffa:23::]:11111]... >>>>>>>>> Sat Jun 4 20:55:12 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default05>[[2a01:4f8:101:3444::188]:11111]... >>>>>>>>> Sat Jun 4 20:55:13 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default03>[[2a03:4000:6:4022::1]:11111]... >>>>>>>>> Sat Jun 4 20:55:14 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default06>[[2a01:4f8:101:3444::187]:11111]... >>>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default04>[5.104.106.134:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default04.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default04>... >>>>>>>>> Sat Jun 4 20:55:16 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default04.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:55:18 2016 authpriv.info dropbear[20682]: >>>>>>>>> Child connection from fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default05>[188.40.140.188:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default05.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default05>... >>>>>>>>> Sat Jun 4 20:55:30 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default05.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default03>[37.120.164.49:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default03.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default03>... >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default03.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default02>[5.104.106.218:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default02.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default02>... >>>>>>>>> Sat Jun 4 20:55:31 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default02.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to <mesh_vpn_backbone_peer_default06>[188.40.140.187:11111 >>>>>>>>> ]... >>>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: >>>>>>>>> resolving host `default06.ffnw.de' for peer >>>>>>>>> <mesh_vpn_backbone_peer_default06>... >>>>>>>>> Sat Jun 4 20:55:33 2016 daemon.info fastd[19930]: resolved >>>>>>>>> host `default06.ffnw.de' successfully >>>>>>>>> Sat Jun 4 20:55:36 2016 authpriv.notice dropbear[20682]: >>>>>>>>> Pubkey auth succeeded for 'root' with key md5 >>>>>>>>> af:61:57:d4:a7:b3:e7:22:cc:91:16:24:4b:28:ad:c2 from >>>>>>>>> fd74:fdaa:9dc4:0:e88b:ca24:5c9b:3fce:4522 >>>>>>>>> Sat Jun 4 20:55:37 2016 daemon.info fastd[19930]: sending >>>>>>>>> handshake to >>>>>>>>> <mesh_vpn_backbone_peer_default04>[[2001:4ba0:fffa:65::1]:11111]... >>>>>>>>> >>>>>>>>> >>>>>>>>> Am 4. Juni 2016 um 19:55 schrieb Stefan < >>>>>>>>> stefan@osnabrueck.freifunk.net>: >>>>>>>>> >>>>>>>>>> Hallo Viktor, >>>>>>>>>> >>>>>>>>>> Sind die Router auf FW 1.0? >>>>>>>>>> Magst du per ssh einmal die Ausgabe von logread hier posten? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> Am 4. Juni 2016 19:44:52 MESZ, schrieb Viktor Grosch via >>>>>>>>>> Nordwest nordwest@lists.ffnw.de: >>>>>>>>>> >>>>>>>>>>> Hallo, >>>>>>>>>>> ich kann keine Verbindung aufbauen, bzw bekomme keine IP >>>>>>>>>>> Adressen zugewiesen zugewiesenen. >>>>>>>>>>> Ich habe es in Hooksiel und Wilhelmshaven einzelt >>>>>>>>>>> getestet, mit TPLINK 4300, 850RE und 860RE, an beiden Standorten. >>>>>>>>>>> Konfiguration wurde nicht verändert. >>>>>>>>>>> >>>>>>>>>>> Liegen aktuell Störungen vor oder weiß einer woran es >>>>>>>>>>> liegen kann. >>>>>>>>>>> >>>>>>>>>>> Schöne Grüße >>>>>>>>>>> >>>>>>>>>>> Viktor >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> Nordwest mailing list >>>>>>>>>>> Nordwest@lists.ffnw.de >>>>>>>>>>> https://lists.ffnw.de/mailman/listinfo/nordwest >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> vg >>>>>>>>>> Stefan >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Schöne Grüße >>>>>>>>> >>>>>>>>> Viktor Grosch >>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> vg >>>>>>>> Stefan >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Schöne Grüße >>>>>>> >>>>>>> Viktor Grosch >>>>>>> >>>>>> >>>>>> -- >>>>>> vg >>>>>> Stefan >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Schöne Grüße >>>>> >>>>> Viktor Grosch >>>>> >>>> >>>> -- >>>> vg >>>> Stefan >>>> >>> >>> >>> >>> -- >>> Schöne Grüße >>> >>> Viktor Grosch >>> >> >> -- >> vg >> Stefan >> > > > > -- > Schöne Grüße > > Viktor Grosch >
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
-- vg Stefan
-- Schöne Grüße
Viktor Grosch
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
-- vg Stefan
Könntest du nochmal mit 1.0 pings ausführen auf: 5.104.106.218 2001:4ba0:fffa:23::
Das ist default02.ffnw.de aufgelöst.
Außerdem ein traceroute auf die IPv4.
Hier sind erstmal die Ergebnisse auf Anfrage von Simon:
PING 5.104.106.218 (5.104.106.218): 56 data bytes 64 bytes from 5.104.106.218: seq=0 ttl=57 time=28.445 ms 64 bytes from 5.104.106.218: seq=1 ttl=57 time=27.618 ms 64 bytes from 5.104.106.218: seq=2 ttl=57 time=26.740 ms 64 bytes from 5.104.106.218: seq=3 ttl=57 time=27.370 ms 64 bytes from 5.104.106.218: seq=4 ttl=57 time=29.171 ms 64 bytes from 5.104.106.218: seq=5 ttl=57 time=27.981 ms
PING 2001:4ba0:fffa:23:: (2001:4ba0:fffa:23::): 56 data bytes ping: sendto: Network is unreachable
traceroute to 5.104.106.218 (5.104.106.218), 30 hops max, 38 byte packets 1 192.168.0.1 (192.168.0.1) 1.608 ms 0.438 ms 0.408 ms 2 217.0.119.83 (217.0.119.83) 18.491 ms 18.361 ms 18.203 ms 3 217.0.72.254 (217.0.72.254) 19.473 ms 19.119 ms 21.625 ms 4 62.154.15.226 (62.154.15.226) 27.743 ms 217.239.50.70 (217.239.50.70) 28. 976 ms 217.239.50.94 (217.239.50.94) 27.295 ms 5 62.157.251.170 (62.157.251.170) 27.868 ms 26.736 ms 28.770 ms 6 62.141.47.185 (62.141.47.185) 39.722 ms 28.222 ms 134.949 ms 7 62.141.47.106 (62.141.47.106) 28.195 ms 27.261 ms 27.545 ms 8 5.104.106.218 (5.104.106.218) 28.863 ms 27.108 ms 27.979 ms
Johannes hat noch ein Tipp gegeben, den hoodselector umbenennen, damit der Chronjob den nicht jede Minute ausführt. Das hat schon mal dazu geführt, dass ich eine Verbindung aufbauen kann, IPs werden zugewiesen, Seitenaufbau geht, selbst YouTube läuft ohne Probleme.
Status VOR der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] No gateways in range ...
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1'
config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000'
config peer_group 'sample_group' option enabled '0' option net 'sample_config'
config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac'
config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn'
config peer 'mesh_vpn_backbone_peer_lk_fri01' option enabled '1' option key '613ffbc8a5a2b1a8602866c0bd44afddecee79c49cde52ee4dd5df73c88d0437' option net 'mesh_vpn' list remote '"lk-fri01.sn.ffnw.de" port 10001' option group 'mesh_vpn_backbone'
Status NACH der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] 2e:99:b2:0a:25:a1 (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit => 8e:95:b6:13:6f:1e (215) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit ce:47:d3:02:f5:bd (166) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 12:b2:19:08:61:6c (175) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 52:ba:56:97:9f:2e (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1' config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000' config peer_group 'sample_group' option enabled '0' option net 'sample_config' config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac' config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn' config peer 'mesh_vpn_backbone_peer_default02' option enabled '1' option key '32a02dd5e6b9233926e178ac609023ad30bcf26954d38d410088bbdc0b2258cb' option net 'mesh_vpn' list remote '"default02.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default03' option enabled '1' option key '9737c65a17cfaa8339315ee53d2b9e02520733780362efacf9503737f5a23204' option net 'mesh_vpn' list remote '"default03.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default04' option enabled '1' option key '18199a10620dbd13728a09402ca2364436ca27e46e669a2ebdfe20976dc45e6f' option net 'mesh_vpn' list remote '"default04.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default05' option enabled '1' option key '5c1738236ba6930f654fd5e815e0c63ac03f81551ee2b183045b256fb133f77d' option net 'mesh_vpn' list remote '"default05.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default06' option enabled '1' option key '22e270ff9b2d1017c3a0b00dd22a58ef7e5915a355eeb16f0b8b52d7eb377869' option net 'mesh_vpn' list remote '"default06.ffnw.de" port 11111' option group 'mesh_vpn_backbone'
Am 5. Juni 2016 um 13:53 schrieb Simon Kurka via Nordwest < nordwest@lists.ffnw.de>:
Könntest du nochmal mit 1.0 pings ausführen auf: 5.104.106.218 2001:4ba0:fffa:23::
Das ist default02.ffnw.de aufgelöst.
Außerdem ein traceroute auf die IPv4.
-- Viele Grüße, Simon
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
Das sieht doch schon besser aus. Wo steht der router laut Koordinaten denn genau?
Am 5. Juni 2016 21:08:14 MESZ, schrieb Viktor Grosch via Nordwest nordwest@lists.ffnw.de:
Hier sind erstmal die Ergebnisse auf Anfrage von Simon:
PING 5.104.106.218 (5.104.106.218): 56 data bytes 64 bytes from 5.104.106.218: seq=0 ttl=57 time=28.445 ms 64 bytes from 5.104.106.218: seq=1 ttl=57 time=27.618 ms 64 bytes from 5.104.106.218: seq=2 ttl=57 time=26.740 ms 64 bytes from 5.104.106.218: seq=3 ttl=57 time=27.370 ms 64 bytes from 5.104.106.218: seq=4 ttl=57 time=29.171 ms 64 bytes from 5.104.106.218: seq=5 ttl=57 time=27.981 ms
PING 2001:4ba0:fffa:23:: (2001:4ba0:fffa:23::): 56 data bytes ping: sendto: Network is unreachable
traceroute to 5.104.106.218 (5.104.106.218), 30 hops max, 38 byte packets 1 192.168.0.1 (192.168.0.1) 1.608 ms 0.438 ms 0.408 ms 2 217.0.119.83 (217.0.119.83) 18.491 ms 18.361 ms 18.203 ms 3 217.0.72.254 (217.0.72.254) 19.473 ms 19.119 ms 21.625 ms 4 62.154.15.226 (62.154.15.226) 27.743 ms 217.239.50.70 (217.239.50.70) 28. 976 ms 217.239.50.94 (217.239.50.94) 27.295 ms 5 62.157.251.170 (62.157.251.170) 27.868 ms 26.736 ms 28.770 ms 6 62.141.47.185 (62.141.47.185) 39.722 ms 28.222 ms 134.949 ms 7 62.141.47.106 (62.141.47.106) 28.195 ms 27.261 ms 27.545 ms 8 5.104.106.218 (5.104.106.218) 28.863 ms 27.108 ms 27.979 ms
Johannes hat noch ein Tipp gegeben, den hoodselector umbenennen, damit der Chronjob den nicht jede Minute ausführt. Das hat schon mal dazu geführt, dass ich eine Verbindung aufbauen kann, IPs werden zugewiesen, Seitenaufbau geht, selbst YouTube läuft ohne Probleme.
Status VOR der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] No gateways in range ...
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1'
config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000'
config peer_group 'sample_group' option enabled '0' option net 'sample_config'
config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac'
config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn'
config peer 'mesh_vpn_backbone_peer_lk_fri01' option enabled '1' option key '613ffbc8a5a2b1a8602866c0bd44afddecee79c49cde52ee4dd5df73c88d0437' option net 'mesh_vpn' list remote '"lk-fri01.sn.ffnw.de" port 10001' option group 'mesh_vpn_backbone'
Status NACH der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] 2e:99:b2:0a:25:a1 (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit => 8e:95:b6:13:6f:1e (215) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit ce:47:d3:02:f5:bd (166) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 12:b2:19:08:61:6c (175) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 52:ba:56:97:9f:2e (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1' config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000' config peer_group 'sample_group' option enabled '0' option net 'sample_config' config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac' config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn' config peer 'mesh_vpn_backbone_peer_default02' option enabled '1' option key '32a02dd5e6b9233926e178ac609023ad30bcf26954d38d410088bbdc0b2258cb' option net 'mesh_vpn' list remote '"default02.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default03' option enabled '1' option key '9737c65a17cfaa8339315ee53d2b9e02520733780362efacf9503737f5a23204' option net 'mesh_vpn' list remote '"default03.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default04' option enabled '1' option key '18199a10620dbd13728a09402ca2364436ca27e46e669a2ebdfe20976dc45e6f' option net 'mesh_vpn' list remote '"default04.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default05' option enabled '1' option key '5c1738236ba6930f654fd5e815e0c63ac03f81551ee2b183045b256fb133f77d' option net 'mesh_vpn' list remote '"default05.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default06' option enabled '1' option key '22e270ff9b2d1017c3a0b00dd22a58ef7e5915a355eeb16f0b8b52d7eb377869' option net 'mesh_vpn' list remote '"default06.ffnw.de" port 11111' option group 'mesh_vpn_backbone'
Am 5. Juni 2016 um 13:53 schrieb Simon Kurka via Nordwest < nordwest@lists.ffnw.de>:
Könntest du nochmal mit 1.0 pings ausführen auf: 5.104.106.218 2001:4ba0:fffa:23::
Das ist default02.ffnw.de aufgelöst.
Außerdem ein traceroute auf die IPv4.
-- Viele Grüße, Simon
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
laut Koordinate (manuell eingetragen) steht der in Hooksiel.
2016-06-05 21:21 GMT+02:00 Stefan stefan@osnabrueck.freifunk.net:
Das sieht doch schon besser aus. Wo steht der router laut Koordinaten denn genau?
Am 5. Juni 2016 21:08:14 MESZ, schrieb Viktor Grosch via Nordwest < nordwest@lists.ffnw.de>:
Hier sind erstmal die Ergebnisse auf Anfrage von Simon:
PING 5.104.106.218 (5.104.106.218): 56 data bytes 64 bytes from 5.104.106.218: seq=0 ttl=57 time=28.445 ms 64 bytes from 5.104.106.218: seq=1 ttl=57 time=27.618 ms 64 bytes from 5.104.106.218: seq=2 ttl=57 time=26.740 ms 64 bytes from 5.104.106.218: seq=3 ttl=57 time=27.370 ms 64 bytes from 5.104.106.218: seq=4 ttl=57 time=29.171 ms 64 bytes from 5.104.106.218: seq=5 ttl=57 time=27.981 ms
PING 2001:4ba0:fffa:23:: (2001:4ba0:fffa:23::): 56 data bytes ping: sendto: Network is unreachable
traceroute to 5.104.106.218 (5.104.106.218), 30 hops max, 38 byte packets 1 192.168.0.1 (192.168.0.1) 1.608 ms 0.438 ms 0.408 ms 2 217.0.119.83 (217.0.119.83) 18.491 ms 18.361 ms 18.203 ms 3 217.0.72.254 (217.0.72.254) 19.473 ms 19.119 ms 21.625 ms 4 62.154.15.226 (62.154.15.226) 27.743 ms 217.239.50.70 (217.239.50.70) 28. 976 ms 217.239.50.94 (217.239.50.94) 27.295 ms 5 62.157.251.170 (62.157.251.170) 27.868 ms 26.736 ms 28.770 ms 6 62.141.47.185 (62.141.47.185) 39.722 ms 28.222 ms 134.949 ms 7 62.141.47.106 (62.141.47.106) 28.195 ms 27.261 ms 27.545 ms 8 5.104.106.218 (5.104.106.218) 28.863 ms 27.108 ms 27.979 ms
Johannes hat noch ein Tipp gegeben, den hoodselector umbenennen, damit der Chronjob den nicht jede Minute ausführt. Das hat schon mal dazu geführt, dass ich eine Verbindung aufbauen kann, IPs werden zugewiesen, Seitenaufbau geht, selbst YouTube läuft ohne Probleme.
Status VOR der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] No gateways in range ...
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1'
config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000'
config peer_group 'sample_group' option enabled '0' option net 'sample_config'
config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac'
config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn'
config peer 'mesh_vpn_backbone_peer_lk_fri01' option enabled '1' option key '613ffbc8a5a2b1a8602866c0bd44afddecee79c49cde52ee4dd5df73c88d0437' option net 'mesh_vpn' list remote '"lk-fri01.sn.ffnw.de" port 10001' option group 'mesh_vpn_backbone'
Status NACH der Umbenennung:
batctl gwl Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth ... [B.A.T.M.A.N. adv 2015.1, MainIF/MAC: mesh-vpn/a2:f7:c1:77:e2:5a (bat0)] 2e:99:b2:0a:25:a1 (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit => 8e:95:b6:13:6f:1e (215) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit ce:47:d3:02:f5:bd (166) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 12:b2:19:08:61:6c (175) 8e:95:b6:13:6f:1e [ mesh-vpn]: 1000.0/1000.0 MBit 52:ba:56:97:9f:2e (194) 8e:95:b6:13:6f:1e [ mesh-vpn]: 100.0/100.0 MBit
/etc/config/fastd
config fastd 'sample_config' option enabled '0' option syslog_level 'info' list method 'salsa2012+umac' option mode 'tap' option interface 'tap0' option mtu '1426' option forward '0' option secure_handshakes '1' config peer 'sample_peer' option enabled '0' option net 'sample_config' option key '0000000000000000000000000000000000000000000000000000000000000000' config peer_group 'sample_group' option enabled '0' option net 'sample_config' config fastd 'mesh_vpn' option enabled '1' option mtu '1312' option group 'gluon-fastd' option status_socket '/var/run/fastd.mesh_vpn.socket' option packet_mark '1' option syslog_level 'verbose' option mode 'tap' option secure_handshakes '1' option interface 'mesh-vpn' option secret '78c43014df4787ea79d0e78a2fbe4d546e6eb27714831f57a8a58becc0ac1153' list method 'salsa2012+umac' config peer_group 'mesh_vpn_backbone' option enabled '1' option peer_limit '1' option net 'mesh_vpn' config peer 'mesh_vpn_backbone_peer_default02' option enabled '1' option key '32a02dd5e6b9233926e178ac609023ad30bcf26954d38d410088bbdc0b2258cb' option net 'mesh_vpn' list remote '"default02.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default03' option enabled '1' option key '9737c65a17cfaa8339315ee53d2b9e02520733780362efacf9503737f5a23204' option net 'mesh_vpn' list remote '"default03.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default04' option enabled '1' option key '18199a10620dbd13728a09402ca2364436ca27e46e669a2ebdfe20976dc45e6f' option net 'mesh_vpn' list remote '"default04.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default05' option enabled '1' option key '5c1738236ba6930f654fd5e815e0c63ac03f81551ee2b183045b256fb133f77d' option net 'mesh_vpn' list remote '"default05.ffnw.de" port 11111' option group 'mesh_vpn_backbone' config peer 'mesh_vpn_backbone_peer_default06' option enabled '1' option key '22e270ff9b2d1017c3a0b00dd22a58ef7e5915a355eeb16f0b8b52d7eb377869' option net 'mesh_vpn' list remote '"default06.ffnw.de" port 11111' option group 'mesh_vpn_backbone'
Am 5. Juni 2016 um 13:53 schrieb Simon Kurka via Nordwest < nordwest@lists.ffnw.de>:
Könntest du nochmal mit 1.0 pings ausführen auf: 5.104.106.218 2001:4ba0:fffa:23::
Das ist default02.ffnw.de aufgelöst.
Außerdem ein traceroute auf die IPv4.
-- Viele Grüße, Simon
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest
-- vg Stefan
hey,
Am 06/04/2016 um 07:44 PM schrieb Viktor Grosch via Nordwest:
Hallo, ich kann keine Verbindung aufbauen, bzw bekomme keine IP Adressen zugewiesen zugewiesenen. Ich habe es in Hooksiel und Wilhelmshaven einzelt getestet, mit TPLINK 4300, 850RE und 860RE, an beiden Standorten. Konfiguration wurde nicht verändert.
Liegen aktuell Störungen vor oder weiß einer woran es liegen kann.
ich hatte nach fw1.0 update ein ähnliches problem, da ich den freifunk router in einem eigenen netz habe, mit nur gewissen ports die erlaubt sind.
https://wiki.nordwest.freifunk.net/Freifunk%20in%20sicherheitsbed%C3%BCrftig... die grundlagen waren nicht mehr aktuell seit den neuen fastD Instanzen ports der hood umstellung.
meine aktuelle freifunk router verbindung schaut so aus in lkfri Int Proto Source -> Router -> Destination State FREIFUNK udp 46.38.241.104:10001 <- 192.168.2.2:48152 MULTIPLE:MULTIPLE
die ports sind hier zu finden https://wiki.nordwest.freifunk.net/Technik/Hood-Server "fastD Instanzen:"
-
picard -
Simon Kurka -
Stefan -
Viktor Grosch -
Viktor Grosch