# Verbindungsproblem TP-Link WDR4900 **URL:** \ **Category:** Herne\ **Created:** [3. März 2016 um 16:18 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113 "2016-03-03T16:18:49Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [3. März 2016 um 16:18 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/1 "2016-03-03T16:18:50Z")
Hallo euch da draußen, habe heuten meinen zweiten Freifunkrouter fertiggeflasht für einen Standort in Herne. Leider bekommt er wie es scheint keine Verbindung zum Freifunkserver. Hab mich mal durch die „Mein Freifunk funktioniert nicht mehr“ Seite gearbeitet, ssh auf den router ping von Adressen funktioniert ohne Probleme. next\_nodes anpingen dagegen nicht, hab versucht die aus den site.conf Dateien zu pingen da kommt keine Reaktion. eine IP für ffher hab ich auf github auch nicht gefunden. Ich hoffe ihr könnt mir hierbei helfen ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [3. März 2016 um 16:19 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/2 "2016-03-03T16:19:31Z")
Häng direkt mal das ifconfig an: bat0 Link encap:Ethernet HWaddr F8:1A:67:5A:60:31 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:0 dropped:0 overruns:0 frame:0 TX packets:3 errors:0 dropped:4 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:42 (42.0 B) TX bytes:270 (270.0 B) br-client Link encap:Ethernet HWaddr F8:1A:67:5A:60:31 inet6 addr: 2a03:2260:50:a000:fa1a:67ff:fe5a:6031/64 Scope:Global inet6 addr: fe80::fa1a:67ff:fe5a:6031/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:122 errors:0 dropped:0 overruns:0 frame:0 TX packets:419 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:14983 (14.6 KiB) TX bytes:59704 (58.3 KiB) br-wan Link encap:Ethernet HWaddr FA:1B:67:5A:60:31 inet addr:192.168.146.222 Bcast:192.168.146.255 Mask:255.255.255.0 inet6 addr: fdc3:e3f9:5040::801/128 Scope:Global inet6 addr: fdc3:e3f9:5040:0:f81b:67ff:fe5a:6031/64 Scope:Global inet6 addr: fe80::f81b:67ff:fe5a:6031/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8400 errors:0 dropped:0 overruns:0 frame:0 TX packets:2914 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:603669 (589.5 KiB) TX bytes:1800237 (1.7 MiB) client0 Link encap:Ethernet HWaddr FA:1C:68:5A:60:31 inet6 addr: fe80::f81c:68ff:fe5a:6031/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:13 errors:0 dropped:0 overruns:0 frame:0 TX packets:202 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2431 (2.3 KiB) TX bytes:19782 (19.3 KiB) client1 Link encap:Ethernet HWaddr FA:1C:69:5A:60:31 inet6 addr: fe80::f81c:69ff:fe5a:6031/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:68 errors:0 dropped:0 overruns:0 frame:0 TX packets:204 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12736 (12.4 KiB) TX bytes:20038 (19.5 KiB) eth0 Link encap:Ethernet HWaddr F8:1A:67:5A:60:32 inet6 addr: fe80::fa1a:67ff:fe5a:6032/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8502 errors:0 dropped:0 overruns:0 frame:0 TX packets:3130 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:877786 (857.2 KiB) TX bytes:1830571 (1.7 MiB) Base address:0xe000 eth0.1 Link encap:Ethernet HWaddr FA:1B:68:5A:60:31 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:209 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:17024 (16.6 KiB) eth0.2 Link encap:Ethernet HWaddr F8:1A:67:5A:60:32 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8500 errors:0 dropped:68 overruns:0 frame:0 TX packets:2914 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:622570 (607.9 KiB) TX bytes:1800237 (1.7 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:2696 errors:0 dropped:0 overruns:0 frame:0 TX packets:2696 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:209224 (204.3 KiB) TX bytes:209224 (204.3 KiB) local-node Link encap:Ethernet HWaddr 16:41:95:40:F7:DC inet addr:10.162.0.254 Bcast:10.162.31.255 Mask:255.255.224.0 inet6 addr: 2a03:2260:50:a000::cafe/128 Scope:Global inet6 addr: fe80::1441:95ff:fe40:f7dc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:79 errors:0 dropped:0 overruns:0 frame:0 TX packets:9 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12973 (12.6 KiB) TX bytes:1006 (1006.0 B) mesh-vpn Link encap:Ethernet HWaddr BE:2B:4B:60:C8:63 inet6 addr: fe80::bc2b:4bff:fe60:c863/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1364 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:14 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:1413 (1.3 KiB) ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [9. März 2016 um 17:59 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/3 "2016-03-09T17:59:46Z")
Kleines update: Hab den AP jetzt an drei verschiedenen Internetzugängen getestet, keine Besserung ---
**Author:** ![adorfer](https://forum.freifunk.net/user_avatar/forum.freifunk.net/adorfer/32/17910_2.png) [@adorfer](https://forum.freifunk.net/u/adorfer)\ **Post date:** [9. März 2016 um 18:03 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/4 "2016-03-09T18:03:15Z")
Das Problem, warum hier keine Antworten kommen, ist dass nicht so recht klar ist, was Du da eigentlich verwendest als Firmware. Zumindest warten vermutlich viele auf diese Angabe. ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [9. März 2016 um 18:22 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/5 "2016-03-09T18:22:49Z")
Entschuldigung, dachte, dass wäre klar, für die Herner Domäne gab es ja noch nicht wirklich viele Images. Auf dem WDR4900 läuft die hier: gluon-ffher-0.8.0+stable+ffher-tp-link-tl-wdr4900 ---
**Author:** ![adorfer](https://forum.freifunk.net/user_avatar/forum.freifunk.net/adorfer/32/17910_2.png) [@adorfer](https://forum.freifunk.net/u/adorfer)\ **Post date:** [9. März 2016 um 18:24 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/6 "2016-03-09T18:24:23Z")
> [@thartung](#): > > gluon-ffher-0.8.0+stable+ffher-tp-link-tl-wdr4900 > Es wurden keine mit Ihrer Suchanfrage - gluon-ffher-0.8.0+stable+ffher-tp-link-tl-wdr4900 - übereinstimmenden Dokumente gefunden. Sagt google. ---
**Author:** ![adorfer](https://forum.freifunk.net/user_avatar/forum.freifunk.net/adorfer/32/17910_2.png) [@adorfer](https://forum.freifunk.net/u/adorfer)\ **Post date:** [9. März 2016 um 18:26 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/7 "2016-03-09T18:26:59Z")
ich habe das File jetzt gefunden. Aber leider keine site.conf/site.mk dazu. Da muss wohl wirklich jemand „vor Ort“ helfen. ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [13. März 2016 um 14:34 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/8 "2016-03-13T14:34:59Z")
Es scheint, es liegt wirklich im Herner Image. Hab jetzt Testweise die Bochumer Firmware drauf, geht sofort ---
**Author:** ![CHRlS](https://forum.freifunk.net/user_avatar/forum.freifunk.net/chrls/32/74_2.png) [@CHRlS](https://forum.freifunk.net/u/CHRlS)\ **Post date:** [13. März 2016 um 20:41 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/9 "2016-03-13T20:41:50Z")
Was sagt denn **logread**? ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [14. März 2016 um 08:25 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/10 "2016-03-14T08:25:35Z")
Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.615317] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829481] ath: EEPROM regdomain: 0x0 Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829494] ath: EEPROM indicates default country code should be used Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829498] ath: doing EEPROM country-\>regdmn map search Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829509] ath: country maps to regdmn code: 0x3a Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829515] ath: Country alpha2 being used: US Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.829520] ath: Regpair used: 0x3a Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.836842] ieee80211 phy0: Selected rate control algorithm ‚minstrel\_ht‘ Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.838789] ieee80211 phy0: Atheros AR9300 Rev:4 mem=0xc9840000, irq=17 Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.846441] cfg80211: Regulatory domain changed to country: US Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.852299] cfg80211: DFS Master region: FCC Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.856477] cfg80211: (start\_freq - end\_freq @ bandwidth), (max\_antenna\_gain, max\_eirp), (dfs\_cac\_time) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.866219] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.874221] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 1700 mBm), (N/A) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.883700] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.893178] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.901266] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A) Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.909269] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936795] ath: EEPROM regdomain: 0x0 Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936808] ath: EEPROM indicates default country code should be used Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936813] ath: doing EEPROM country-\>regdmn map search Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936823] ath: country maps to regdmn code: 0x3a Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936829] ath: Country alpha2 being used: US Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.936834] ath: Regpair used: 0x3a Mon Mar 14 09:21:21 2016 kern.debug kernel: [10.944180] ieee80211 phy1: Selected rate control algorithm ‚minstrel\_ht‘ Mon Mar 14 09:21:21 2016 [kern.info](http://kern.info) kernel: [10.946045] ieee80211 phy1: Atheros AR9300 Rev:3 mem=0xc98c0000, irq=18 Mon Mar 14 09:21:21 2016 daemon.notice haveged: haveged starting up Mon Mar 14 09:21:22 2016 [daemon.info](http://daemon.info) haveged: haveged: ver: 1.9.1; arch: ppc; vend: ; build: (gcc 4.8.3 V); collect: 128K Mon Mar 14 09:21:22 2016 [daemon.info](http://daemon.info) haveged: haveged: cpu: (); data: 32K (P); inst: 32K (P); idx: 15/40; sz: 31924/83032 Mon Mar 14 09:21:22 2016 [daemon.info](http://daemon.info) haveged: haveged: fills: 0, generated: 0 Mon Mar 14 09:21:23 2016 [cron.info](http://cron.info) crond[2590]: crond (busybox 1.23.2) started, log level 5 Mon Mar 14 09:21:24 2016 [authpriv.info](http://authpriv.info) dropbear[2610]: Not backgrounding Mon Mar 14 09:21:25 2016 daemon.warn netifd: You have delegated IPv6-prefixes but haven’t assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces? Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.324016] device eth0 entered promiscuous mode Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚mesh\_lan‘ is enabled Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.332755] device eth0.1 entered promiscuous mode Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.340681] br-client: port 1(eth0.1) entered forwarding state Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.346561] br-client: port 1(eth0.1) entered forwarding state Mon Mar 14 09:21:25 2016 user.notice sysctl: net.ipv6.conf.br-client.forwarding = 0 Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚client‘ is enabled Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.413513] device eth0.2 entered promiscuous mode Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.421767] br-wan: port 1(eth0.2) entered forwarding state Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.427388] br-wan: port 1(eth0.2) entered forwarding state Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan6‘ is enabled Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan‘ is enabled Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚mesh\_wan‘ is enabled Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan‘ is setting up now Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan‘ is now up Mon Mar 14 09:21:25 2016 [kern.info](http://kern.info) kernel: [16.504123] device br-client entered promiscuous mode Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚local\_node‘ is enabled Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚local\_node‘ is setting up now Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚local\_node‘ is now up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚loopback‘ is enabled Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚loopback‘ is setting up now Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚loopback‘ is now up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Bridge ‚br-client‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚client‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚client‘ is setting up now Mon Mar 14 09:21:25 2016 daemon.notice netifd: MAC VLAN ‚local-node‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚local\_node‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: Network device ‚eth0‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: VLAN ‚eth0.1‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚mesh\_lan‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: VLAN ‚eth0.2‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Bridge ‚br-wan‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan6‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan6‘ is setting up now Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚wan‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚mesh\_wan‘ has link connectivity Mon Mar 14 09:21:25 2016 daemon.notice netifd: Network device ‚lo‘ link is up Mon Mar 14 09:21:25 2016 daemon.notice netifd: Interface ‚loopback‘ has link connectivity Mon Mar 14 09:21:26 2016 [daemon.info](http://daemon.info) dnsmasq[2876]: started, version 2.73 cachesize 150 Mon Mar 14 09:21:26 2016 [daemon.info](http://daemon.info) dnsmasq[2876]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Mon Mar 14 09:21:26 2016 daemon.warn dnsmasq[2876]: no servers found in /var/gluon/wan-dnsmasq/resolv.conf, will retry Mon Mar 14 09:21:26 2016 [daemon.info](http://daemon.info) dnsmasq[2876]: cleared cache Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.172014] cfg80211: Regulatory domain changed to country: DE Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.177868] cfg80211: DFS Master region: ETSI Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.182139] cfg80211: (start\_freq - end\_freq @ bandwidth), (max\_antenna\_gain, max\_eirp), (dfs\_cac\_time) Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.191881] cfg80211: (2400000 KHz - 2483000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.199884] cfg80211: (5150000 KHz - 5250000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (N/A) Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.209464] cfg80211: (5250000 KHz - 5350000 KHz @ 80000 KHz, 200000 KHz AUTO), (N/A, 2000 mBm), (0 s) Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.218971] cfg80211: (5470000 KHz - 5725000 KHz @ 160000 KHz), (N/A, 2700 mBm), (0 s) Mon Mar 14 09:21:26 2016 [kern.info](http://kern.info) kernel: [17.227066] cfg80211: (57000000 KHz - 66000000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A) Mon Mar 14 09:21:26 2016 user.emerg syslog: Starting tunneldigger on mesh-vpn Mon Mar 14 09:21:26 2016 user.notice firewall: Reloading firewall due to ifup of wan (br-wan) Mon Mar 14 09:21:26 2016 [daemon.info](http://daemon.info) td-client: Performing broker selection… Mon Mar 14 09:21:26 2016 daemon.err td-client: Failed to resolve hostname ‚node02.her.freifunk.ruhr‘. Mon Mar 14 09:21:27 2016 user.emerg syslog: /etc/rc.d/S99alfred: waiting 30 secs for bat0 interface… Mon Mar 14 09:21:27 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: started, version 2.73 cachesize 150 Mon Mar 14 09:21:27 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-auth no-DNSSEC loop-detect inotify Mon Mar 14 09:21:27 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using local addresses only for domain lan Mon Mar 14 09:21:27 2016 daemon.warn dnsmasq[3008]: no servers found in /tmp/resolv.conf.auto, will retry Mon Mar 14 09:21:27 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: read /etc/hosts - 1 addresses Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.315773] fsl-gianfar soc@ffe00000:ethernet@b0000 eth0: Link is Up - 1Gbps/Full - flow control off Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.347501] br-client: port 1(eth0.1) entered forwarding state Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.427499] br-wan: port 1(eth0.2) entered forwarding state Mon Mar 14 09:21:27 2016 daemon.err td-client: Failed to resolve hostname ‚node01.her.freifunk.ruhr‘. Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.636833] IPv6: ADDRCONF(NETDEV\_UP): client0: link is not ready Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.653128] IPv6: ADDRCONF(NETDEV\_UP): client1: link is not ready Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.667599] device client0 entered promiscuous mode Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.683395] br-client: port 2(client0) entered forwarding state Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.689384] br-client: port 2(client0) entered forwarding state Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.695339] IPv6: ADDRCONF(NETDEV\_CHANGE): client0: link becomes ready Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.706999] device client1 entered promiscuous mode Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.712056] br-client: port 3(client1) entered forwarding state Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.718003] br-client: port 3(client1) entered forwarding state Mon Mar 14 09:21:27 2016 [kern.info](http://kern.info) kernel: [18.744928] IPv6: ADDRCONF(NETDEV\_CHANGE): client1: link becomes ready Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio0 (2757): Configuration file: /var/run/hostapd-phy0.conf Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio0 (2757): client0: interface state UNINITIALIZED-\>COUNTRY\_UPDATE Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio0 (2757): Using interface client0 with hwaddr fa:1c:68:5a:60:31 and ssid „Freifunk“ Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio0 (2757): client0: interface state COUNTRY\_UPDATE-\>ENABLED Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio0 (2757): client0: AP-ENABLED Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio1 (2758): Configuration file: /var/run/hostapd-phy1.conf Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio1 (2758): client1: interface state UNINITIALIZED-\>COUNTRY\_UPDATE Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio1 (2758): Using interface client1 with hwaddr fa:1c:69:5a:60:31 and ssid „Freifunk“ Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio1 (2758): client1: interface state COUNTRY\_UPDATE-\>ENABLED Mon Mar 14 09:21:27 2016 daemon.notice netifd: radio1 (2758): client1: AP-ENABLED Mon Mar 14 09:21:27 2016 user.notice firewall: Reloading firewall due to ifup of local\_node (local-node) Mon Mar 14 09:21:27 2016 daemon.notice netifd: Network device ‚client0‘ link is up Mon Mar 14 09:21:27 2016 daemon.notice netifd: Network device ‚client1‘ link is up Mon Mar 14 09:21:29 2016 [authpriv.info](http://authpriv.info) dropbear[3228]: Child connection from 192.168.146.126:49909 Mon Mar 14 09:21:29 2016 [kern.info](http://kern.info) kernel: [20.323969] Atheros AR8216/AR8236/AR8316 mdio@ffe24000:00: Port 1 is up Mon Mar 14 09:21:29 2016 [kern.info](http://kern.info) kernel: [20.691481] br-client: port 2(client0) entered forwarding state Mon Mar 14 09:21:29 2016 [kern.info](http://kern.info) kernel: [20.719471] br-client: port 3(client1) entered forwarding state Mon Mar 14 09:21:30 2016 daemon.warn netifd: You have delegated IPv6-prefixes but haven’t assigned them to any interface. Did you forget to set option ip6assign on your lan-interfaces? Mon Mar 14 09:21:30 2016 daemon.notice netifd: Interface ‚wan6‘ is now up Mon Mar 14 09:21:30 2016 user.notice firewall: Reloading firewall due to ifup of wan6 (br-wan) Mon Mar 14 09:21:30 2016 [daemon.info](http://daemon.info) dnsmasq[2876]: reading /var/gluon/wan-dnsmasq/resolv.conf Mon Mar 14 09:21:30 2016 [daemon.info](http://daemon.info) dnsmasq[2876]: using nameserver fdc3:e3f9:5040::1#53 Mon Mar 14 09:21:34 2016 authpriv.notice dropbear[3228]: Password auth succeeded for ‚root‘ from 192.168.146.126:49909 Mon Mar 14 09:21:36 2016 daemon.notice netifd: Interface ‚client‘ is now up Mon Mar 14 09:21:36 2016 user.notice firewall: Reloading firewall due to ifup of client (br-client) Mon Mar 14 09:21:42 2016 [daemon.info](http://daemon.info) td-client: Reinitializing tunnel context. Mon Mar 14 09:21:42 2016 [daemon.info](http://daemon.info) td-client: Reinitializing tunnel context. Mon Mar 14 09:21:45 2016 daemon.debug td-client: Broker usage: 0x104cad68 node02.her.freifunk.ruhr 16640 Mon Mar 14 09:21:45 2016 daemon.debug td-client: Broker usage: 0x104c6630 node01.her.freifunk.ruhr 393 Mon Mar 14 09:21:46 2016 [daemon.info](http://daemon.info) td-client: Selected node01.her.freifunk.ruhr:10000 as the best broker. Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚mesh\_vpn‘ is enabled Mon Mar 14 09:21:48 2016 [daemon.info](http://daemon.info) td-client: Tunnel successfully established. Mon Mar 14 09:21:48 2016 daemon.notice netifd: Network device ‚mesh-vpn‘ link is up Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚mesh\_vpn‘ has link connectivity Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚mesh\_vpn‘ is setting up now Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.652684] batman\_adv: bat0: Adding interface: mesh-vpn Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.658066] batman\_adv: bat0: The MTU of interface mesh-vpn is too small (1364) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1528 would solve the problem. Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.682386] batman\_adv: bat0: Interface activated: mesh-vpn Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚bat0‘ is enabled Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.690683] device bat0 entered promiscuous mode Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.695373] br-client: port 4(bat0) entered forwarding state Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.701095] br-client: port 4(bat0) entered forwarding state Mon Mar 14 09:21:48 2016 daemon.notice netifd: Network device ‚bat0‘ link is up Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚bat0‘ has link connectivity Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚bat0‘ is setting up now Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚bat0‘ is now up Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.711403] batman\_adv: bat0: no\_rebroadcast: Changing from: disabled to: enabled Mon Mar 14 09:21:48 2016 daemon.notice netifd: Interface ‚mesh\_vpn‘ is now up Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.870726] batman\_adv: bat0: Changing gw mode from: off to: client Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.887752] batman\_adv: bat0: hop\_penalty: Changing from: 30 to: 15 Mon Mar 14 09:21:48 2016 [kern.info](http://kern.info) kernel: [39.899657] batman\_adv: bat0: orig\_interval: Changing from: 1000 to: 5000 Mon Mar 14 09:21:49 2016 user.emerg syslog: /etc/rc.d/S99alfred: waiting 30 secs for br-client address… Mon Mar 14 09:21:49 2016 user.emerg syslog: /etc/rc.d/S99alfred: starting alfred Mon Mar 14 09:21:49 2016 user.emerg syslog: /etc/rc.d/S99alfred: starting batadv-vis Mon Mar 14 09:21:49 2016 [daemon.info](http://daemon.info) procd: - init complete - Mon Mar 14 09:21:50 2016 [kern.info](http://kern.info) kernel: [41.703469] br-client: port 4(bat0) entered forwarding state Mon Mar 14 09:22:00 2016 user.notice gluon-offline-ssid: TQ is 6, SSID is Freifunk, change to FF\_OFFLINE\_FF-Flott…hallen01 Mon Mar 14 09:22:00 2016 user.notice gluon-offline-ssid: TQ is 6, SSID is Freifunk, change to FF\_OFFLINE\_FF-Flott…hallen01 Mon Mar 14 09:22:31 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: reading /tmp/resolv.conf.auto Mon Mar 14 09:22:31 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using local addresses only for domain lan Mon Mar 14 09:22:31 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2001:4860:4860::8888#53 Mon Mar 14 09:22:31 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2a03:2260:50:a000::a#53 Mon Mar 14 09:22:42 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: reading /tmp/resolv.conf.auto Mon Mar 14 09:22:42 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using local addresses only for domain lan Mon Mar 14 09:22:42 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2001:4860:4860::8888#53 Mon Mar 14 09:22:42 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2a03:2260:50:a000::a#53 Mon Mar 14 09:22:42 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2a03:2260:50:a000::b#53 Mon Mar 14 09:23:39 2016 user.notice gluon-offline-ssid: TQ is 110, SSID is FF\_OFFLINE\_FF-Flott…hallen01, change to Freifunk Mon Mar 14 09:23:39 2016 user.notice gluon-offline-ssid: TQ is 110, SSID is FF\_OFFLINE\_FF-Flott…hallen01, change to Freifunk Mon Mar 14 09:23:41 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: reading /tmp/resolv.conf.auto Mon Mar 14 09:23:41 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using local addresses only for domain lan Mon Mar 14 09:23:41 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2a03:2260:50:a000::a#53 Mon Mar 14 09:23:41 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2001:4860:4860::8888#53 Mon Mar 14 09:23:41 2016 [daemon.info](http://daemon.info) dnsmasq[3008]: using nameserver 2a03:2260:50:a000::b#53 Mon Mar 14 09:23:41 2016 user.notice firewall: Reloading firewall due to ifupdate of client (br-client) ---
**Author:** ![CHRlS](https://forum.freifunk.net/user_avatar/forum.freifunk.net/chrls/32/74_2.png) [@CHRlS](https://forum.freifunk.net/u/CHRlS)\ **Post date:** [14. März 2016 um 10:44 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/11 "2016-03-14T10:44:37Z")
Der Router war vorhin online: [http://map.her.freifunk.ruhr/#!v:m;n:f81a675a6031](http://map.her.freifunk.ruhr/#!v:m;n:f81a675a6031) Im Logfile geht er um 9:21 Uhr online: > [@thartung](#): > > Mon Mar 14 09:21:46 2016 [daemon.info](http://daemon.info) td-client: Selected node01.her.freifunk.ruhr:10000 as the best broker.Mon > Mar 14 09:21:48 2016 [daemon.info](http://daemon.info) td-client: Tunnel successfully established. und ändert um 9:23 Uhr seine offline SSID zur SSID Freifunk, hat also eine ausreichend gute TQ zu den Freifunk Servern: > [@thartung](#): > > Mon Mar 14 09:23:39 2016 user.notice gluon-offline-ssid: TQ is 110, SSID is FF\_OFFLINE\_FF-Flott…hallen01, change to Freifunk Ins WLAN Netz Freifunk kannst Du Dich einloggen? Der Router funktioniert laut Logfile. Was genau ist der Fehler? Kannst Du das ein wenig detaillieren? ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [14. März 2016 um 10:48 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/12 "2016-03-14T10:48:54Z")
Online geht er ja. Kann ja auch wenn ich via ssh drauf bin Adressen pingen ohne Probleme. Wie es scheint wird er nut nicht Teil von Freifunk, denn nach dem ändern der SSID auf Freifunk ändert er sie ganz fix auf freifunk offline: > Mon Mar 14 09:22:00 2016 user.notice gluon-offline-ssid: TQ is 6, SSID is Freifunk, change to FF\_OFFLINE\_FF-Flott…hallen01 Wenn ich mich mit einem Gerät am AP anmelde kommt das Gerät auch nicht online, der Knoten erscheint auch nie auf der Karte ---
**Author:** ![CHRlS](https://forum.freifunk.net/user_avatar/forum.freifunk.net/chrls/32/74_2.png) [@CHRlS](https://forum.freifunk.net/u/CHRlS)\ **Post date:** [14. März 2016 um 10:54 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/13 "2016-03-14T10:54:26Z")
Doch, war vorhin auf der Karte, als er online war: [http://map.her.freifunk.ruhr/#!v:m;n:f81a675a6031](http://map.her.freifunk.ruhr/#!v:m;n:f81a675a6031) Mach ihn an, warte im Logread darauf, dass die SSID zu Freifunk geändert wird und warte dann mal ein paar Minuten ab, während Du Dir parallel das Logread immer mal wieder ansiehst, ob noch weitere Meldungen kommen. Wenn er dann danach wieder seine SSID zu Offline wechseln sollte, dann brauchen wir genau den Logread Auszug zwischen SSID change zu Freifunk und SSID change wieder zu offline, denn da muss dann was zwischendrin passieren. ---
**Author:** ![thartung](https://forum.freifunk.net/letter_avatar_proxy/v4/letter/t/7bcc69/32.png) [@thartung](https://forum.freifunk.net/u/thartung)\ **Post date:** [14. März 2016 um 11:27 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/14 "2016-03-14T11:27:09Z")
Stimmt, momentan macht er was er soll… werde ihn testweise etwas laufen lassen und dann am Wochenende an seinem finalen Standort verbauen. Danke schon mal für die Hilfe. ---
**Author:** ![CHRlS](https://forum.freifunk.net/user_avatar/forum.freifunk.net/chrls/32/74_2.png) [@CHRlS](https://forum.freifunk.net/u/CHRlS)\ **Post date:** [14. März 2016 um 11:27 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/15 "2016-03-14T11:27:18Z")
Da ist er wieder. TQ ist super (100%). ![](https://forum.freifunk.net/uploads/default/original/2X/a/ab11c15c2656a671bf5562102c6a59ae88b438ad.png) ---
**Author:** ![CHRlS](https://forum.freifunk.net/user_avatar/forum.freifunk.net/chrls/32/74_2.png) [@CHRlS](https://forum.freifunk.net/u/CHRlS)\ **Post date:** [14. März 2016 um 11:27 UTC](https://forum.freifunk.net/t/verbindungsproblem-tp-link-wdr4900/11113/16 "2016-03-14T11:27:58Z")
> [@thartung](#): > > Stimmt, momentan macht er was er soll… werde ihn testweise etwas laufen lassen und dann am Wochenende an seinem finalen Standort verbauen.Danke schon mal für die Hilfe. Kein Thema, freut mich das es jetzt läuft.