Bist Du sicher, das die Ports in der Firewall der Fritzbox offen sind?
Paste doch bitte mal einen Screenshot der entsprechenden Seiten…
Standard Empfehlung z.B. hier:
http://freifunk-burscheid.de/gast-zugang-und-prioritaeten-bei-der-fritzbox-setzen
Entschuldige bitte, ich habe heute Nacht am Netzwerk gewerkelt und dachte dein Problem sei mit der Veränderung verbunden.
Router Testweise mit einer ffw-wup geflasht, alles gut. Zugriff ins Internet von den Clients aus funktioniert. Züruckgeflasht auf die gluon-ffgl-bgl-2016022222-tp-link-tl-wr841n-nd-v10-sysupgrade.bin, der Zugriff ins Internet funktioniert nicht.
Ich gehe nach dem Test davon aus: das der 841 v10 OK ist, mein Provider nicht blockt, das die Fritz!box 7490 auch korrekt eingestellt ist.
Welcher Provider ist das? Ich hätte jetzt eigentlich auf Unitymedia getippt, aber das passt nicht zu der initialen Beschreibung „16/50MBits-Umstellung“
(DSLite, MTU-Probleme, Erreichbarkeit der Supernodes per IPv6)
Provider ist Vodafone
logread per SSH in config mode auslesen, oder was ist damit gemeint?
Im Configmode versucht das Gerät nicht, eine Verbindung aufzubauen.
Das müsstest Du schon im Vollbetrieb machen. Dafür wirst Du entweder die IPv6-Nextnode-Adresse oder die Iv4-Nextnode-Adresse nutzen müssen, letzteres allerdings dann mit deaktiviertem DHCP am Rechner (für das Interface)
Adressen in
hier das logread, sehe ich es richtig, dass die namensauflösung nicht funktioniert?
root@bgl-60e327b7a956:~# logread
Mon Feb 22 23:22:33 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:34 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper2>…
Mon Feb 22 23:22:34 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:34 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl7>…
Mon Feb 22 23:22:34 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:35 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper7>…
Mon Feb 22 23:22:35 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:36 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl0>…
Mon Feb 22 23:22:36 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:37 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper3>…
Mon Feb 22 23:22:37 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:38 2016 authpriv.info dropbear[3423]: Child connection from fda0:747e:ab29:5142:654e:9077:2ae5:cfd5:41271 Mon Feb 22 23:22:39 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl9>…
Mon Feb 22 23:22:39 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:39 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl2>…
Mon Feb 22 23:22:39 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:41 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper8>…
Mon Feb 22 23:22:41 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:43 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl4>…
Mon Feb 22 23:22:43 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:43 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper4>…
Mon Feb 22 23:22:43 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:45 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl6>…
Mon Feb 22 23:22:45 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:45 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper9>…
Mon Feb 22 23:22:45 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:47 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl1>…
Mon Feb 22 23:22:47 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:47 2016 authpriv.notice dropbear[3423]: Password auth succeeded for 'root' from fda0:747e:ab29:5142:654e:9077:2ae5:cfd5:41271 Mon Feb 22 23:22:48 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper1>…
Mon Feb 22 23:22:48 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:49 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl5>…
Mon Feb 22 23:22:49 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:50 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl8>…
Mon Feb 22 23:22:50 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:51 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper6>…
Mon Feb 22 23:22:51 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:53 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper5>…
Mon Feb 22 23:22:53 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:53 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper7>…
Mon Feb 22 23:22:53 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl7>…
Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl3>…
Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper0>…
Mon Feb 22 23:22:54 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:56 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper2>…
Mon Feb 22 23:22:56 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:56 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper3>…
Mon Feb 22 23:22:56 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:57 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl2>…
Mon Feb 22 23:22:57 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:22:58 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl0>…
Mon Feb 22 23:22:58 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:00 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper8>…
Mon Feb 22 23:23:00 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:00 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl9>…
Mon Feb 22 23:23:00 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:01 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper4>…
Mon Feb 22 23:23:01 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:01 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl4>…
Mon Feb 22 23:23:01 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:04 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl6>…
Mon Feb 22 23:23:04 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:05 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper9>…
Mon Feb 22 23:23:05 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:06 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl1>…
Mon Feb 22 23:23:06 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:08 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper1>…
Mon Feb 22 23:23:08 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:10 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl5>…
Mon Feb 22 23:23:10 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper5>…
Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper6>…
Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl8>…
Mon Feb 22 23:23:11 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:13 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper2>…
Mon Feb 22 23:23:13 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:14 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl3>…
Mon Feb 22 23:23:14 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:14 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl7>…
Mon Feb 22 23:23:14 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:15 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper7>…
Mon Feb 22 23:23:15 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:16 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper0>…
Mon Feb 22 23:23:16 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:17 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl2>…
Mon Feb 22 23:23:17 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:18 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl0>…
Mon Feb 22 23:23:18 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:18 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper3>…
Mon Feb 22 23:23:18 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:20 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper8>…
Mon Feb 22 23:23:20 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:20 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper4>…
Mon Feb 22 23:23:20 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:21 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl9>…
Mon Feb 22 23:23:21 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:22 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl4>…
Mon Feb 22 23:23:22 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:24 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl6>…
Mon Feb 22 23:23:24 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:24 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl1>…
Mon Feb 22 23:23:24 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:26 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper9>…
Mon Feb 22 23:23:26 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:29 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl8>…
Mon Feb 22 23:23:29 2016 daemon.info fastd[1527]: resolving host gl8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:31 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl5>…
Mon Feb 22 23:23:31 2016 daemon.info fastd[1527]: resolving host gl5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:31 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper1>…
Mon Feb 22 23:23:31 2016 daemon.info fastd[1527]: resolving host wupper1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper2>…
Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host wupper2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl7>…
Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host gl7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper5>…
Mon Feb 22 23:23:32 2016 daemon.info fastd[1527]: resolving host wupper5.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:33 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper6>…
Mon Feb 22 23:23:33 2016 daemon.info fastd[1527]: resolving host wupper6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:33 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl3>…
Mon Feb 22 23:23:33 2016 daemon.info fastd[1527]: resolving host gl3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:34 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper0>…
Mon Feb 22 23:23:34 2016 daemon.info fastd[1527]: resolving host wupper0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl2>…
Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host gl2.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl0>…
Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host gl0.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper7>…
Mon Feb 22 23:23:36 2016 daemon.info fastd[1527]: resolving host wupper7.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:37 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper3>…
Mon Feb 22 23:23:37 2016 daemon.info fastd[1527]: resolving host wupper3.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:40 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper8>…
Mon Feb 22 23:23:40 2016 daemon.info fastd[1527]: resolving host wupper8.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:40 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl9>…
Mon Feb 22 23:23:40 2016 daemon.info fastd[1527]: resolving host gl9.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:41 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl4>…
Mon Feb 22 23:23:41 2016 daemon.info fastd[1527]: resolving host gl4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:43 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl1>…
Mon Feb 22 23:23:43 2016 daemon.info fastd[1527]: resolving host gl1.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:43 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper4>…
Mon Feb 22 23:23:43 2016 daemon.info fastd[1527]: resolving host wupper4.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:45 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu’ for peer <mesh_vpn_backbone_peer_gl6>…
Mon Feb 22 23:23:45 2016 daemon.info fastd[1527]: resolving host gl6.ffgl.eu' failed: Name or service not known Mon Feb 22 23:23:46 2016 daemon.info fastd[1527]: resolving host wupper9.ffgl.eu’ for peer <mesh_vpn_backbone_peer_wupper9>…
Mon Feb 22 23:23:46 2016 daemon.info fastd[1527]: resolving host `wupper9.ffgl.eu’ failed: Name or service not known
root@bgl-60e327b7a956:~#
Dein Freifunk-Router bekommt also die Namensauflösung der Wupper-Server nicht hin.
Sage dem Freifunk-Router mal im Expert-Setup, dass er als Nameserver (DNS) die 8.8.8.8 befragen soll.
Nameserver auf 8.8.8.8 gesetzt. Problem besteht weiterhin. Logread unverändert. 
@PetaByteBoy scheint ein DNS-Problem zu sein
bitte probiere folgendes aus:
uci set fastd.mesh_vpn_backbone_peer_wupper2.remote="ipv4 \"2.wupper.ffrl.de\" port 51399"
/etc/init.d/fastd reload
logread -f
auf keinen Fall einen uci commit … durchführen, das ist nur ein Test.
DNS im Netz läuft. Gerade nochmal getestet…
eine TTL eines CNAME Eintrages von 60 s ist vlt zu extrem.
Clients haben weiterhin kein Zugriff ins Internet, hier ein Auszug von Logread,
Tue Feb 23 04:19:11 2016 daemon.info fastd[1540]: resolving host gl5.ffgl.eu' for peer <mesh_vpn_backbone_peer_gl5>... Tue Feb 23 04:19:11 2016 daemon.info fastd[1540]: resolving host gl5.ffgl.eu’ failed: Name or service not known
Tue Feb 23 04:19:11 2016 daemon.info fastd[1540]: resolving host gl2.ffgl.eu' for peer <mesh_vpn_backbone_peer_gl2>...** **Tue Feb 23 04:19:11 2016 daemon.info fastd[1540]: resolving host gl2.ffgl.eu’ failed: Name or service not known
Tue Feb 23 04:19:12 2016 daemon.info fastd[1540]: resolving host 2.wupper.ffrl.de' for peer <mesh_vpn_backbone_peer_wupper2>... Tue Feb 23 04:19:12 2016 daemon.info fastd[1540]: resolving host 2.wupper.ffrl.de’ failed: Name or service not known
Dann scheint es nicht am DNS von ffgl.eu zu liegen, sondern der Router lernt „mit dieser Firmware“ nicht den DNS Deines Provider-Routers. Oder Port 53 UDP/TCP sind aus einem nicht erkennbaren Grund für den Freifunk-Router gesperrt worden.
Nicht über Deinen C-Name, sondern weil pcon das als fqdn auf Phips Empfehlung direkt eingetragen hat.
Mein Ansatz wäre jetzt, die Supernode-IPs direkt in de /etc/hosts zu setzen, wenn irgendwer den DNS des FF-Routers blockiert.
Clients an SSID Freifunk Burscheid - Router bekommen kein DNS etc.
Also keine Internetverbindung
Edit, auch Testrouter mit SSID Freifunk bekommt hier nichts
(Hab jetzt keine Zeit, jetzt irgend was weiter zu testen, bin bis mindestens morgen weg)
Heute Morgen den Node wieder eingeschaltet und siehe da alles geht wieder. Keine Änderungen am Router oder am Node durchgeführt. Alles wieder gut, trotzdem würde mich interessieren was vorgegangen ist😉
Hier ein Speedtest
Danke an alle die Mitgeholfen haben.
cu pcon