Hallo,
der von mir betriebene Freifunkknoten hatte sich seit dem Morgen des 8.6.17 sich seltsam verhalten. WLAN-Verbindung stand, Datenübertragung war nicht möglich. Ich habe den FF-Router mehrere Stunden stromlos gehabt. Am Problem hat sich kaum was geändert. Auffällig war, dass die WLAN-LED sonst immer blinkte, jetzt leuchtete sie einige Zeit und fing wieder an zu blinken.
Am 16.6.17 habe ich mich auf die Routeroberfläche eingeloggt und wollte den Router auf Werkseinstellungen zurücksetzen. Die Möglichkeit habe ich nicht gefunden. Ich ergänzte meine Kontaktadresse und aktivierte eine private SSID. Bis zum Abend des 18.6.17 war alles i.O., bis das Spiel wieder anfing.
Heute nach der Arbeit brach der Internetzugriff innerhalb von ca. 1 Minute nach dem Herstellen der WLAN-Verbindung der Internetzugriff ab. Zeitweise war auch über die private SSID kein Internetzugriff möglich (Verbindung brach ab und laut Windows war weder die nordwest.freifunk.net noch die private SSID (des FF-Routers) sichtbar). Was kann ich machen, um das Problem einzugrenzen / zu beheben? Vielen Dank.
Internetzugriff über meinen privaten Router ist i.O. und unauffällig
Provider: Telekom
Speedtest siehe http://www.speedtest.net/my-result/6389922187 (ping 27 mS / down 45,37 Mbit/S / up 9,37 Mbit/S)
OpenWRT Version: OpenWrt Chaos Calmer 15.05.1 (r49389)
Gluon Version: v2016.2.5-6-g97f44c20 Gluon Release: 20170530
Selected Hood: rastede
------------------------------------------------------
root@WesterstedeGaststr19Indoor:~# hoodselector
VPN connection found.
Position found.
Set hood "rastede"
Hood set by VPN mode.
root@WesterstedeGaststr19Indoor:~# logread
Mon Jun 19 18:00:51 2017 daemon.notice netifd: Interface 'ibss_radio0' is now up
Mon Jun 19 18:00:51 2017 kern.info kernel: [ 2839.540000] br-client: port 2(client0) entered forwarding state
Mon Jun 19 18:00:51 2017 kern.info kernel: [ 2839.620000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:00:52 2017 daemon.notice netifd: Interface 'client' is now up
Mon Jun 19 18:00:52 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Mon Jun 19 18:01:17 2017 daemon.info dnsmasq[1606]: reading /tmp/resolv.conf.auto
Mon Jun 19 18:01:17 2017 daemon.info dnsmasq[1606]: using local addresses only for domain lan
Mon Jun 19 18:01:17 2017 daemon.info dnsmasq[1606]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53
Mon Jun 19 18:01:17 2017 daemon.info dnsmasq[1606]: using nameserver 2001:67c:18e8:0:2::181#53
Mon Jun 19 18:01:17 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
Mon Jun 19 18:02:00 2017 daemon.notice fastd[3691]: terminating fastd
Mon Jun 19 18:02:00 2017 daemon.notice fastd[3691]: connection with <mesh_vpn_backbone_peer_default06_11111> disestablished.
Mon Jun 19 18:02:00 2017 daemon.info fastd[3691]: deleting peer <mesh_vpn_backbone_peer_default06_11111>
Mon Jun 19 18:02:00 2017 daemon.info fastd[3691]: deleting peer <mesh_vpn_backbone_peer_default06_11112>
Mon Jun 19 18:02:00 2017 daemon.notice netifd: Network device 'mesh-vpn' link is down
Mon Jun 19 18:02:00 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity loss
Mon Jun 19 18:02:00 2017 kern.info kernel: [ 2908.200000] batman_adv: bat0: Interface deactivated: mesh-vpn
Mon Jun 19 18:02:00 2017 kern.info kernel: [ 2908.240000] batman_adv: bat0: Removing interface: mesh-vpn
Mon Jun 19 18:02:00 2017 daemon.notice netifd: Interface 'mesh_vpn' is disabled
Mon Jun 19 18:02:01 2017 daemon.notice netifd: Interface 'ibss_radio0' is disabled
Mon Jun 19 18:02:01 2017 daemon.notice netifd: Interface 'ibss_radio0' has link connectivity loss
Mon Jun 19 18:02:01 2017 kern.info kernel: [ 2909.850000] batman_adv: bat0: Interface deactivated: ibss0
Mon Jun 19 18:02:01 2017 kern.info kernel: [ 2909.860000] batman_adv: bat0: Removing interface: ibss0
Mon Jun 19 18:02:01 2017 daemon.notice netifd: Interface 'ibss_radio0' is now down
Mon Jun 19 18:02:02 2017 daemon.notice netifd: Network device 'wlan0-3' link is down
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2909.990000] br-wan: port 2(wlan0-3) entered disabled state
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2909.990000] device wlan0-3 left promiscuous mode
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2910.000000] br-wan: port 2(wlan0-3) entered disabled state
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2910.080000] device client0 left promiscuous mode
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2910.080000] br-client: port 2(client0) entered disabled state
Mon Jun 19 18:02:02 2017 daemon.notice netifd: Network device 'client0' link is down
Mon Jun 19 18:02:02 2017 daemon.notice netifd: Interface 'mesh_radio0' is disabled
Mon Jun 19 18:02:02 2017 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2910.340000] batman_adv: bat0: Interface deactivated: mesh0
Mon Jun 19 18:02:02 2017 daemon.notice netifd: Network device 'mesh0' link is down
Mon Jun 19 18:02:02 2017 daemon.notice netifd: wan (1399): Performing a DHCP renew
Mon Jun 19 18:02:02 2017 daemon.notice netifd: wan (1399): Sending renew...
Mon Jun 19 18:02:02 2017 daemon.notice netifd: wan (1399): Lease of 192.168.2.100 obtained, lease time 1814400
Mon Jun 19 18:02:02 2017 kern.info kernel: [ 2910.500000] batman_adv: bat0: Removing interface: mesh0
Mon Jun 19 18:02:03 2017 kern.info kernel: [ 2911.180000] batman_adv: bat0: Interface deactivated: primary0
Mon Jun 19 18:02:03 2017 kern.info kernel: [ 2911.220000] batman_adv: bat0: Removing interface: primary0
Mon Jun 19 18:02:03 2017 kern.info kernel: [ 2911.220000] br-client: port 3(bat0) entered disabled state
Mon Jun 19 18:02:03 2017 daemon.notice netifd: Network device 'bat0' link is down
Mon Jun 19 18:02:03 2017 daemon.notice netifd: Interface 'bat0' has link connectivity loss
Mon Jun 19 18:02:03 2017 daemon.notice netifd: Interface 'bat0' is now down
Mon Jun 19 18:02:03 2017 kern.info kernel: [ 2911.260000] device bat0 left promiscuous mode
Mon Jun 19 18:02:03 2017 kern.info kernel: [ 2911.260000] br-client: port 3(bat0) entered disabled state
Mon Jun 19 18:02:03 2017 daemon.notice netifd: Interface 'bat0' is disabled
Mon Jun 19 18:02:03 2017 daemon.notice netifd: Interface 'mesh_radio0' is now down
Mon Jun 19 18:02:04 2017 daemon.notice fastd[4872]: fastd v18 starting
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'mesh_vpn' is enabled
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Network device 'mesh-vpn' link is up
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'mesh_vpn' is setting up now
Mon Jun 19 18:02:04 2017 daemon.notice fastd[4872]: changed to UID 0, GID 800
Mon Jun 19 18:02:04 2017 daemon.info fastd[4872]: adding peer <mesh_vpn_backbone_peer_ras01_10000>
Mon Jun 19 18:02:04 2017 daemon.info fastd[4872]: resolving host `ras01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_ras01_10000>...
Mon Jun 19 18:02:04 2017 daemon.info fastd[4872]: resolved host `ras01.sn.ffnw.de' successfully
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Bridge 'br-client' link is down
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'client' has link connectivity loss
Mon Jun 19 18:02:04 2017 kern.info kernel: [ 2912.370000] br-client: port 1(eth0.1) entered disabled state
Mon Jun 19 18:02:04 2017 kern.info kernel: [ 2912.380000] br-client: port 1(eth0.1) entered forwarding state
Mon Jun 19 18:02:04 2017 kern.info kernel: [ 2912.390000] br-client: port 1(eth0.1) entered forwarding state
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Bridge 'br-client' link is up
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'client' has link connectivity
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'client' is setting up now
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'client' is now down
Mon Jun 19 18:02:04 2017 daemon.notice netifd: Interface 'client' is setting up now
Mon Jun 19 18:02:04 2017 daemon.warn dnsmasq[1606]: no servers found in /tmp/resolv.conf.auto, will retry
Mon Jun 19 18:02:05 2017 daemon.notice netifd: radio0 (4662): Configuration file: /var/run/hostapd-phy0.conf
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.200000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.250000] batman_adv: bat0: Adding interface: primary0
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.260000] batman_adv: bat0: Interface activated: primary0
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.270000] 8021q: adding VLAN 0 to HW filter on device bat0
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.270000] device bat0 entered promiscuous mode
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.280000] br-client: port 2(bat0) entered forwarding state
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.280000] br-client: port 2(bat0) entered forwarding state
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Interface 'bat0' is enabled
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.300000] batman_adv: bat0: Adding interface: mesh-vpn
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.300000] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1312) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem.
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.330000] batman_adv: bat0: Interface activated: mesh-vpn
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.340000] device client0 entered promiscuous mode
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.350000] br-client: port 3(client0) entered forwarding state
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.350000] br-client: port 3(client0) entered forwarding state
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.400000] device wlan0-3 entered promiscuous mode
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Network device 'bat0' link is up
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Interface 'bat0' has link connectivity
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Interface 'bat0' is setting up now
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Interface 'bat0' is now up
Mon Jun 19 18:02:05 2017 daemon.notice netifd: radio0 (4662): client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Mon Jun 19 18:02:05 2017 daemon.notice netifd: radio0 (4662): Using interface client0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid "nordwest.freifunk.net"
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.410000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.470000] IPv6: ADDRCONF(NETDEV_UP): wlan0-3: link is not ready
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.470000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.480000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:02:05 2017 daemon.notice netifd: radio0 (4662): Using interface wlan0-3 with hwaddr 36:e2:c4:c7:fc:a3 and ssid "WLAN-871921"
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.510000] br-wan: port 2(wlan0-3) entered disabled state
Mon Jun 19 18:02:05 2017 kern.info kernel: [ 2913.520000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
Mon Jun 19 18:02:05 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.390000] br-client: port 1(eth0.1) entered forwarding state
Mon Jun 19 18:02:06 2017 daemon.info fastd[4872]: sending handshake to <mesh_vpn_backbone_peer_ras01_10000>[[2a01:4f8:161:5205::23]:10000]...
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.740000] batman_adv: bat0: Changing gw mode from: off to: client
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.760000] batman_adv: bat0: gw_sel_class: Changing from: 20 to: 1
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.760000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.780000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-3: link becomes ready
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.780000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.790000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:02:06 2017 daemon.notice netifd: radio0 (4662): client0: interface state COUNTRY_UPDATE->ENABLED
Mon Jun 19 18:02:06 2017 daemon.notice netifd: radio0 (4662): client0: AP-ENABLED
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.800000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled
Mon Jun 19 18:02:06 2017 kern.info kernel: [ 2914.840000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2914.960000] IPv6: ADDRCONF(NETDEV_UP): ibss0: link is not ready
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.000000] ibss0: Created IBSS using preconfigured BSSID 02:00:0a:12:a0:00
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.000000] ibss0: Creating new IBSS network, BSSID 02:00:0a:12:a0:00
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.010000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss0: link becomes ready
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.120000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.130000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.280000] br-client: port 2(bat0) entered forwarding state
Mon Jun 19 18:02:07 2017 kern.info kernel: [ 2915.350000] br-client: port 3(client0) entered forwarding state
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Network device 'ibss0' link is up
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'ibss_radio0' is enabled
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'ibss_radio0' has link connectivity
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'ibss_radio0' is setting up now
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Network device 'mesh0' link is up
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'mesh_radio0' is enabled
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Network device 'client0' link is up
Mon Jun 19 18:02:07 2017 daemon.notice netifd: Network device 'wlan0-3' link is up
Mon Jun 19 18:02:07 2017 daemon.notice netifd: wan (1399): Performing a DHCP renew
Mon Jun 19 18:02:07 2017 daemon.notice netifd: wan (1399): Sending renew...
Mon Jun 19 18:02:07 2017 daemon.notice netifd: wan (1399): Lease of 192.168.2.100 obtained, lease time 1814400
Mon Jun 19 18:02:08 2017 kern.info kernel: [ 2916.130000] batman_adv: bat0: Adding interface: mesh0
Mon Jun 19 18:02:08 2017 kern.info kernel: [ 2916.140000] batman_adv: bat0: Interface activated: mesh0
Mon Jun 19 18:02:08 2017 kern.info kernel: [ 2916.160000] batman_adv: bat0: Adding interface: ibss0
Mon Jun 19 18:02:08 2017 kern.info kernel: [ 2916.170000] batman_adv: bat0: Interface activated: ibss0
Mon Jun 19 18:02:08 2017 daemon.notice netifd: Interface 'mesh_radio0' is now up
Mon Jun 19 18:02:08 2017 daemon.notice netifd: Interface 'ibss_radio0' is now up
Mon Jun 19 18:02:08 2017 kern.info kernel: [ 2916.790000] br-wan: port 2(wlan0-3) entered forwarding state
Mon Jun 19 18:02:16 2017 daemon.notice netifd: Interface 'client' is now up
Mon Jun 19 18:02:17 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Mon Jun 19 18:02:26 2017 daemon.info fastd[4872]: sending handshake to <mesh_vpn_backbone_peer_ras01_10000>[5.9.56.23:10000]...
Mon Jun 19 18:02:26 2017 daemon.info fastd[4872]: resolving host `ras01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_ras01_10000>...
Mon Jun 19 18:02:26 2017 daemon.info fastd[4872]: resolved host `ras01.sn.ffnw.de' successfully
Mon Jun 19 18:02:47 2017 daemon.info fastd[4872]: sending handshake to <mesh_vpn_backbone_peer_ras01_10000>[[2a01:4f8:161:5205::23]:10000]...
Mon Jun 19 18:02:47 2017 daemon.info fastd[4872]: received handshake response from <mesh_vpn_backbone_peer_ras01_10000>[[2a01:4f8:161:5205::23]:10000] using fastd v18
Mon Jun 19 18:02:47 2017 daemon.info fastd[4872]: [2a01:4f8:161:5205::23]:10000 authorized as <mesh_vpn_backbone_peer_ras01_10000>
Mon Jun 19 18:02:47 2017 daemon.notice fastd[4872]: connection with <mesh_vpn_backbone_peer_ras01_10000> established.
Mon Jun 19 18:02:47 2017 daemon.info fastd[4872]: new session with <mesh_vpn_backbone_peer_ras01_10000> established using method `salsa2012+umac'.
Mon Jun 19 18:02:54 2017 daemon.info dnsmasq[1606]: reading /tmp/resolv.conf.auto
Mon Jun 19 18:02:54 2017 daemon.info dnsmasq[1606]: using local addresses only for domain lan
Mon Jun 19 18:02:54 2017 daemon.info dnsmasq[1606]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53
Mon Jun 19 18:02:54 2017 daemon.info dnsmasq[1606]: using nameserver 2001:67c:18e8:0:2::181#53
Mon Jun 19 18:02:54 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
Mon Jun 19 18:10:00 2017 user.notice root: netmon-node-client[5713]: Netmon Node Client is disabled.
Mon Jun 19 18:14:46 2017 kern.warn kernel: [ 3674.240000] br-client: Multicast hash table maximum of 512 reached, disabling snooping: bat0
Mon Jun 19 18:20:00 2017 user.notice root: netmon-node-client[6033]: Netmon Node Client is disabled.
Mon Jun 19 18:23:20 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Mon Jun 19 18:23:20 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Mon Jun 19 18:23:20 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d WPA: pairwise key handshake completed (RSN)
Mon Jun 19 18:25:50 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: disassociated
Mon Jun 19 18:25:50 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Mon Jun 19 18:25:50 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Mon Jun 19 18:26:20 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Jun 19 18:27:12 2017 kern.info kernel: [ 4420.650000] IPv6: udp checksum is 0 for [2a01:4f8:161:5205::23]:10000->[2003:d2:bc8:eb34:34e2:c4ff:fec7:fca0]:41056
Mon Jun 19 18:30:00 2017 user.notice root: netmon-node-client[6365]: Netmon Node Client is disabled.
Mon Jun 19 18:31:46 2017 kern.info kernel: [ 4694.570000] IPv6: udp checksum is 0 for [2a01:4f8:161:5205::23]:10000->[2003:d2:bc8:eb34:34e2:c4ff:fec7:fca0]:41056
Mon Jun 19 18:40:00 2017 user.notice root: netmon-node-client[6691]: Netmon Node Client is disabled.
Mon Jun 19 18:42:33 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: disassociated
Mon Jun 19 18:42:34 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mon Jun 19 18:44:49 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Mon Jun 19 18:44:49 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Mon Jun 19 18:46:06 2017 kern.info kernel: [ 5554.470000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Mon Jun 19 18:46:35 2017 authpriv.info dropbear[6910]: Child connection from fd74:fdaa:9dc4:0:144d:6027:4826:37c0:47896
Mon Jun 19 18:47:42 2017 authpriv.notice dropbear[6910]: Password auth succeeded for 'root' from fd74:fdaa:9dc4:0:144d:6027:4826:37c0:47896
Mon Jun 19 18:47:51 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: disassociated
Mon Jun 19 18:47:51 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Mon Jun 19 18:47:51 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Mon Jun 19 18:47:51 2017 daemon.info hostapd: wlan0-3: STA b0:89:00:fb:54:3d WPA: pairwise key handshake completed (RSN)
Mon Jun 19 18:48:21 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Codeformatierung durch Moderation korrigiert
Hallo,
wir benutzen als offizielles Kommunikationsmittel unsere Mailinglisten - hier liest kaum jemand von uns mit.
Hast du den Router schon komplett neugeflascht?
Nein. Reicht es die aktuellste Version der FF-Nordwest Firmware für meinen Router über die graphische Oberfläche einzuspielen?
Das könnte reichen, oder auch nicht.
Das ist extrem schwer zu sagen, zumindest erkenne ich aus den obigen Logs nicht, was darauf hindeutet.
Ich würde daher vorschlagen, es eher wie empfohlen zu machen, also komplett zu flashen.
Ich gehe jedoch davon aus, dass es sich nicht um ein Setup-Problem am Freifunk-Knoten handelt.
Ich habe mit „firstboot“ alle Einstellungen zurückgesetzt, dieser Befehl war doch mit „neu flaschen“ gemeint, oder? Und anschließend habe ich die meine Einstellungen wieder manuell über die graphische Oberfläche eingegeben. Internetzugriff klappt nicht vom Laptop per LAN und Smartphone per WLAN über das Freifunknetz. Seltsamerweise war die Suche über google.de i.O. (ich habe Begriffe eingegeben, die ich nicht täglich suche bzw. ich vermeide sonst Google zu nutzen), Seitenaufbau war sehr langsam.
Ich habe den FF-Router und meinen privaten Router für 5 Minuten stromlos gehabt. Anschließend konnte ich einige Minuten lang über den FF-Router Daten übertragen, wobei die Geschwindigkeit vom Seitenaufruf zum Seitenaufruf immer langsamer wurde. Jetzt geht wieder nichts, Seiten können nur sporadisch aufgerufen werden.
*OpenWRT Version: OpenWrt Chaos Calmer 15.05.1 (r49389)
Gluon Version: v2016.2.5-6-g97f44c20 Gluon Release: 20170530
Selected Hood: default
root@WesterstedeGaststr19Indoor:~# hoodselector
VPN connection found.
No position found
Set hood „default“
Set defaulthood.
root@WesterstedeGaststr19Indoor:~# logread
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚local_node‘ is enabled
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚local_node‘ is setting up now
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚local_node‘ is now up
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚loopback‘ is enabled
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚loopback‘ is setting up now
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚loopback‘ is now up
Tue May 30 23:28:10 2017 daemon.notice netifd: Network device ‚lo‘ link is up
Tue May 30 23:28:10 2017 daemon.notice netifd: Interface ‚loopback‘ has link connectivity
Tue May 30 23:28:10 2017 user.notice sysctl: net.ipv6.conf.br-client.forwarding = 0
Tue May 30 23:28:11 2017 user.notice firewall: Reloading firewall due to ifup of local_node (local-node)
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.640000] eth0: link up (1000Mbps/Full duplex)
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.640000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Tue May 30 23:28:11 2017 daemon.notice netifd: Network device ‚eth0‘ link is up
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.660000] br-client: port 1(eth0.1) entered forwarding state
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.670000] br-client: port 1(eth0.1) entered forwarding state
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.680000] br-wan: port 1(eth0.2) entered forwarding state
Tue May 30 23:28:11 2017 kern.info kernel: [ 20.680000] br-wan: port 1(eth0.2) entered forwarding state
Tue May 30 23:28:11 2017 daemon.notice netifd: VLAN ‚eth0.1‘ link is up
Tue May 30 23:28:11 2017 daemon.notice netifd: VLAN ‚eth0.2‘ link is up
Tue May 30 23:28:12 2017 kern.info kernel: [ 20.820000] IPv6: ADDRCONF(NETDEV_CHANGE): br-client: link becomes ready
Tue May 30 23:28:12 2017 kern.info kernel: [ 20.830000] IPv6: ADDRCONF(NETDEV_CHANGE): br-wan: link becomes ready
Tue May 30 23:28:12 2017 daemon.notice netifd: Bridge ‚br-client‘ link is up
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚client‘ has link connectivity
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚client‘ is setting up now
Tue May 30 23:28:12 2017 daemon.notice netifd: Bridge ‚br-wan‘ link is up
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚wan6‘ has link connectivity
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚wan6‘ is setting up now
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚wan‘ has link connectivity
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚wan‘ is setting up now
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚mesh_wan‘ has link connectivity
Tue May 30 23:28:12 2017 daemon.notice netifd: MAC VLAN ‚local-node‘ link is up
Tue May 30 23:28:12 2017 daemon.notice netifd: Interface ‚local_node‘ has link connectivity
Tue May 30 23:28:12 2017 kern.info kernel: [ 20.890000] IPv6: ADDRCONF(NETDEV_CHANGE): local-node: link becomes ready
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: EEPROM regdomain: 0x8114
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: EEPROM indicates we should expect a country code
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: doing EEPROM country->regdmn map search
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: country maps to regdmn code: 0x37
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: Country alpha2 being used: DE
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: Regpair used: 0x37
Tue May 30 23:28:12 2017 kern.debug kernel: [ 21.170000] ath: regdomain 0x8114 dynamically updated by user
Tue May 30 23:28:12 2017 daemon.notice netifd: wan (1399): udhcpc (v1.23.2) started
Tue May 30 23:28:13 2017 daemon.notice netifd: wan (1399): Sending discover…
Tue May 30 23:28:13 2017 kern.info kernel: [ 22.670000] br-client: port 1(eth0.1) entered forwarding state
Tue May 30 23:28:13 2017 kern.info kernel: [ 22.680000] br-wan: port 1(eth0.2) entered forwarding state
Tue May 30 23:28:14 2017 daemon.notice netifd: wan (1399): Sending select for 192.168.2.101…
Tue May 30 23:28:14 2017 daemon.notice netifd: wan (1399): Lease of 192.168.2.101 obtained, lease time 1814400
Tue May 30 23:28:15 2017 daemon.info dnsmasq[1547]: started, version 2.73 cachesize 150
Tue May 30 23:28:15 2017 daemon.info dnsmasq[1547]: 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
Tue May 30 23:28:15 2017 daemon.info dnsmasq[1547]: DNS service limited to local subnets
Tue May 30 23:28:15 2017 daemon.info dnsmasq[1547]: using local addresses only for domain lan
Tue May 30 23:28:15 2017 daemon.warn dnsmasq[1547]: no servers found in /tmp/resolv.conf.auto, will retry
Tue May 30 23:28:15 2017 daemon.info dnsmasq[1547]: read /etc/hosts - 1 addresses
Tue May 30 23:28:15 2017 daemon.notice netifd: Interface ‚wan‘ is now up
Tue May 30 23:28:15 2017 daemon.notice netifd: radio0 (1186): Configuration file: /var/run/hostapd-phy0.conf
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.230000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
Tue May 30 23:28:15 2017 daemon.notice netifd: radio0 (1186): client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.280000] device client0 entered promiscuous mode
Tue May 30 23:28:15 2017 daemon.notice netifd: radio0 (1186): Using interface client0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid „nordwest.freifunk.net“
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.320000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.320000] br-client: port 2(client0) entered forwarding state
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.330000] br-client: port 2(client0) entered forwarding state
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.430000] device wlan0-3 entered promiscuous mode
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.440000] IPv6: ADDRCONF(NETDEV_UP): wlan0-3: link is not ready
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.450000] br-wan: port 2(wlan0-3) entered forwarding state
Tue May 30 23:28:15 2017 kern.info kernel: [ 24.450000] br-wan: port 2(wlan0-3) entered forwarding state
Tue May 30 23:28:15 2017 daemon.notice netifd: radio0 (1186): Using interface wlan0-3 with hwaddr 36:e2:c4:c7:fc:a3 and ssid „WLAN-871921“
Tue May 30 23:28:16 2017 daemon.info dnsmasq[1630]: started, version 2.73 cachesize 150
Tue May 30 23:28:16 2017 daemon.info dnsmasq[1630]: 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
Tue May 30 23:28:16 2017 daemon.info dnsmasq[1630]: reading /var/gluon/wan-dnsmasq/resolv.conf
Tue May 30 23:28:16 2017 daemon.info dnsmasq[1630]: using nameserver 192.168.2.1#53
Tue May 30 23:28:16 2017 daemon.info dnsmasq[1630]: cleared cache
Tue May 30 23:28:16 2017 kern.info kernel: [ 25.340000] br-wan: port 2(wlan0-3) entered disabled state
Tue May 30 23:28:16 2017 kern.info kernel: [ 25.520000] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0-3: link becomes ready
Tue May 30 23:28:16 2017 kern.info kernel: [ 25.530000] br-wan: port 2(wlan0-3) entered forwarding state
Tue May 30 23:28:16 2017 kern.info kernel: [ 25.540000] br-wan: port 2(wlan0-3) entered forwarding state
Tue May 30 23:28:16 2017 daemon.notice netifd: radio0 (1186): client0: interface state COUNTRY_UPDATE->ENABLED
Tue May 30 23:28:16 2017 daemon.notice netifd: radio0 (1186): client0: AP-ENABLED
Tue May 30 23:28:17 2017 kern.info kernel: [ 25.810000] IPv6: ADDRCONF(NETDEV_UP): ibss0: link is not ready
Tue May 30 23:28:17 2017 kern.info kernel: [ 25.860000] ibss0: Created IBSS using preconfigured BSSID 02:ca:ff:ee:ba:bf
Tue May 30 23:28:17 2017 kern.info kernel: [ 25.870000] ibss0: Creating new IBSS network, BSSID 02:ca:ff:ee:ba:bf
Tue May 30 23:28:17 2017 kern.info kernel: [ 26.000000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss0: link becomes ready
Tue May 30 23:28:17 2017 kern.info kernel: [ 26.010000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Tue May 30 23:28:17 2017 kern.info kernel: [ 26.050000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚wan6‘ is now up
Tue May 30 23:28:17 2017 kern.info kernel: [ 26.330000] br-client: port 2(client0) entered forwarding state
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1547]: exiting on receipt of SIGTERM
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: started, version 2.73 cachesize 150
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: 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
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: DNS service limited to local subnets
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: using local addresses only for domain lan
Tue May 30 23:28:17 2017 daemon.warn dnsmasq[1761]: no servers found in /tmp/resolv.conf.auto, will retry
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: read /etc/hosts - 1 addresses
Tue May 30 23:28:17 2017 daemon.info dnsmasq[1761]: read /tmp/hosts/dhcp - 0 addresses
Tue May 30 23:28:17 2017 daemon.notice netifd: Network device ‚ibss0‘ link is up
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is enabled
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ has link connectivity
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is setting up now
Tue May 30 23:28:17 2017 daemon.notice netifd: Network device ‚mesh0‘ link is up
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is enabled
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ has link connectivity
Tue May 30 23:28:17 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is setting up now
Tue May 30 23:28:17 2017 daemon.notice netifd: Network device ‚client0‘ link is up
Tue May 30 23:28:17 2017 daemon.notice netifd: Network device ‚wlan0-3‘ link is up
Tue May 30 23:28:18 2017 daemon.notice fastd[1796]: fastd v18 starting
Tue May 30 23:28:18 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is enabled
Tue May 30 23:28:18 2017 daemon.notice netifd: Network device ‚mesh-vpn‘ link is up
Tue May 30 23:28:18 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ has link connectivity
Tue May 30 23:28:18 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is setting up now
Tue May 30 23:28:18 2017 daemon.notice fastd[1796]: changed to UID 0, GID 800
Tue May 30 23:28:18 2017 daemon.notice netifd: wan (1399): Performing a DHCP renew
Tue May 30 23:28:18 2017 daemon.notice netifd: wan (1399): Sending renew…
Tue May 30 23:28:18 2017 daemon.notice netifd: wan (1399): Lease of 192.168.2.101 obtained, lease time 1814400
Tue May 30 23:28:18 2017 daemon.info fastd[1796]: adding peer <mesh_vpn_backbone_peer_default06_11112>
Tue May 30 23:28:18 2017 daemon.info fastd[1796]: adding peer <mesh_vpn_backbone_peer_default06_11111>
Tue May 30 23:28:18 2017 daemon.info fastd[1796]: resolving host default06.ffnw.de' for peer <mesh_vpn_backbone_peer_default06_11111>... Tue May 30 23:28:18 2017 daemon.info fastd[1796]: resolving host default06.ffnw.de’ for peer <mesh_vpn_backbone_peer_default06_11112>…
Tue May 30 23:28:18 2017 kern.info kernel: [ 27.540000] br-wan: port 2(wlan0-3) entered forwarding state
Tue May 30 23:28:18 2017 daemon.info fastd[1796]: resolved host default06.ffnw.de' successfully Tue May 30 23:28:18 2017 daemon.info fastd[1796]: resolved host default06.ffnw.de’ successfully
Tue May 30 23:28:18 2017 user.notice firewall: Reloading firewall due to ifup of wan (br-wan)
Tue May 30 23:28:18 2017 user.emerg syslog: setting up led USB
Tue May 30 23:28:18 2017 user.emerg syslog: Skipping trigger ‚usbdev‘ for led ‚USB‘ due to missing kernel module
Tue May 30 23:28:18 2017 user.emerg syslog: setting up led WLAN
Tue May 30 23:28:18 2017 user.emerg syslog: setting up led WAN
Tue May 30 23:28:18 2017 user.emerg syslog: setting up led LAN1
Tue May 30 23:28:18 2017 user.emerg syslog: setting up led LAN2
Tue May 30 23:28:19 2017 user.emerg syslog: setting up led LAN3
Tue May 30 23:28:19 2017 user.emerg syslog: setting up led LAN4
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.910000] batman_adv: bat0: Adding interface: primary0
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.920000] batman_adv: bat0: Interface activated: primary0
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.930000] 8021q: adding VLAN 0 to HW filter on device bat0
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.930000] device bat0 entered promiscuous mode
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.940000] br-client: port 3(bat0) entered forwarding state
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.940000] br-client: port 3(bat0) entered forwarding state
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚bat0‘ is enabled
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.970000] batman_adv: bat0: Adding interface: ibss0
Tue May 30 23:28:19 2017 kern.info kernel: [ 27.970000] batman_adv: bat0: Interface activated: ibss0
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.100000] batman_adv: bat0: Adding interface: mesh0
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.110000] batman_adv: bat0: Interface activated: mesh0
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.180000] batman_adv: bat0: Adding interface: mesh-vpn
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.180000] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1312) to handle the transport of batman-adv packets. Packets going over this interface will be fragmented on layer2 which could impact the performance. Setting the MTU to 1532 would solve the problem.
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.210000] batman_adv: bat0: Interface activated: mesh-vpn
Tue May 30 23:28:19 2017 daemon.notice netifd: Network device ‚bat0‘ link is up
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚bat0‘ has link connectivity
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚bat0‘ is setting up now
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚bat0‘ is now up
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is now up
Tue May 30 23:28:19 2017 daemon.notice netifd: mesh_radio0 (1765): ip: RTNETLINK answers: File exists
Tue May 30 23:28:19 2017 kern.info kernel: [ 28.440000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is now up
Tue May 30 23:28:19 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is now up
Tue May 30 23:28:20 2017 daemon.info fastd[1796]: sending handshake to <mesh_vpn_backbone_peer_default06_11112>[[2a01:4f8:221:1ec4::179]:11112]…
Tue May 30 23:28:20 2017 kern.info kernel: [ 29.080000] batman_adv: bat0: Changing gw mode from: off to: client
Tue May 30 23:28:20 2017 kern.info kernel: [ 29.120000] batman_adv: bat0: gw_sel_class: Changing from: 20 to: 1
Tue May 30 23:28:20 2017 kern.info kernel: [ 29.120000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15
Tue May 30 23:28:20 2017 kern.info kernel: [ 29.160000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled
Tue May 30 23:28:20 2017 kern.info kernel: [ 29.160000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000
Tue May 30 23:28:20 2017 daemon.info fastd[1796]: received handshake response from <mesh_vpn_backbone_peer_default06_11112>[[2a01:4f8:221:1ec4::179]:11112] using fastd v18
Tue May 30 23:28:20 2017 daemon.info procd: - init complete -
Tue May 30 23:28:20 2017 daemon.info fastd[1796]: [2a01:4f8:221:1ec4::179]:11112 authorized as <mesh_vpn_backbone_peer_default06_11112>
Tue May 30 23:28:20 2017 daemon.notice fastd[1796]: connection with <mesh_vpn_backbone_peer_default06_11112> established.
Tue May 30 23:28:20 2017 daemon.info fastd[1796]: new session with <mesh_vpn_backbone_peer_default06_11112> established using method `salsa2012+umac’.
Tue May 30 23:28:21 2017 daemon.info dnsmasq[1630]: reading /var/gluon/wan-dnsmasq/resolv.conf
Tue May 30 23:28:21 2017 daemon.info dnsmasq[1630]: using nameserver fe80::1%br-wan#53
Tue May 30 23:28:21 2017 daemon.info dnsmasq[1630]: using nameserver 192.168.2.1#53
Tue May 30 23:28:21 2017 kern.info kernel: [ 29.940000] br-client: port 3(bat0) entered forwarding state
Tue May 30 23:28:21 2017 user.notice firewall: Reloading firewall due to ifup of wan6 (br-wan)
Tue May 30 23:28:24 2017 daemon.notice netifd: Interface ‚client‘ is now up
Tue May 30 23:28:24 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Tue May 30 23:28:31 2017 kern.notice kernel: [ 40.260000] random: nonblocking pool is initialized
Tue May 30 23:28:37 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Tue May 30 23:28:37 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Tue May 30 23:29:12 2017 daemon.info dnsmasq[1761]: reading /tmp/resolv.conf.auto
Tue May 30 23:29:12 2017 daemon.info dnsmasq[1761]: using local addresses only for domain lan
Tue May 30 23:29:12 2017 daemon.info dnsmasq[1761]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53
Tue May 30 23:29:12 2017 daemon.info dnsmasq[1761]: using nameserver 2001:67c:18e8:0:2::181#53
Tue May 30 23:29:13 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
Tue May 30 23:29:13 2017 daemon.warn fastd[1796]: sendmsg: Operation not permitted
Tue May 30 23:29:46 2017 kern.info kernel: [ 115.110000] Atheros AR8216/AR8236/AR8316 ag71xx-mdio.0:00: Port 1 is up
Tue May 30 23:30:01 2017 user.notice root: netmon-node-client[2419]: Netmon Node Client is disabled.
Thu Jun 22 20:26:26 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: disassociated
Thu Jun 22 20:26:27 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Thu Jun 22 20:28:22 2017 authpriv.info dropbear[3105]: Child connection from fd74:fdaa:9dc4:0:5ac:f53:275a:4a0a:46696
Thu Jun 22 20:28:23 2017 authpriv.info dropbear[3105]: Exit before auth: Exited normally
Thu Jun 22 20:30:01 2017 user.notice root: netmon-node-client[3152]: Netmon Node Client is disabled.
Thu Jun 22 20:30:15 2017 authpriv.info dropbear[3271]: Child connection from fd74:fdaa:9dc4:0:5ac:f53:275a:4a0a:46710
Thu Jun 22 20:30:57 2017 authpriv.notice dropbear[3271]: Password auth succeeded for ‚root‘ from fd74:fdaa:9dc4:0:5ac:f53:275a:4a0a:46710
*
Du bist auch noch mit deinem Router in unserem großen alten Netz - wie sehen vom Router folgende Sachen aus:
- batctl gwl
- ping6 autoupdate.ffnw
?
Ist das schon eine Abweichung vom Sollzustand? Was bedeutet das für den Knoten konkret?
root@WesterstedeGaststr19Indoor:~# batctl gwl
Gateway (#/255) Nexthop [outgoingIF]: advertised uplink bandwidth … [B.A.T.M.A.N. adv 2016.2, MainIF/MAC: primary0/36:e2:c4:c7:fc:a3 (bat0)]
=> 02:81:b4:00:2a:18 (247) 02:81:b4:00:2a:18 [ mesh-vpn]: 1000.0/1000.0 MBit
root@WesterstedeGaststr19Indoor:~# ping6 autoupdate.ffnw
PING autoupdate.ffnw (2a03:4000:6:8025::1): 56 data bytes
64 bytes from 2a03:4000:6:8025::1: seq=0 ttl=59 time=92.098 ms
64 bytes from 2a03:4000:6:8025::1: seq=1 ttl=59 time=52.276 ms
64 bytes from 2a03:4000:6:8025::1: seq=2 ttl=59 time=49.219 ms
64 bytes from 2a03:4000:6:8025::1: seq=3 ttl=59 time=48.397 ms
64 bytes from 2a03:4000:6:8025::1: seq=4 ttl=59 time=46.453 ms
64 bytes from 2a03:4000:6:8025::1: seq=5 ttl=59 time=45.824 ms
64 bytes from 2a03:4000:6:8025::1: seq=6 ttl=59 time=51.677 ms
64 bytes from 2a03:4000:6:8025::1: seq=7 ttl=59 time=47.842 ms
64 bytes from 2a03:4000:6:8025::1: seq=8 ttl=59 time=45.305 ms
64 bytes from 2a03:4000:6:8025::1: seq=9 ttl=59 time=45.854 ms
64 bytes from 2a03:4000:6:8025::1: seq=10 ttl=59 time=44.393 ms
64 bytes from 2a03:4000:6:8025::1: seq=11 ttl=59 time=61.712 ms
64 bytes from 2a03:4000:6:8025::1: seq=12 ttl=59 time=51.309 ms
64 bytes from 2a03:4000:6:8025::1: seq=13 ttl=59 time=52.240 ms
64 bytes from 2a03:4000:6:8025::1: seq=14 ttl=59 time=56.240 ms
64 bytes from 2a03:4000:6:8025::1: seq=15 ttl=59 time=68.529 ms
64 bytes from 2a03:4000:6:8025::1: seq=16 ttl=59 time=50.201 ms
64 bytes from 2a03:4000:6:8025::1: seq=17 ttl=59 time=58.899 ms
64 bytes from 2a03:4000:6:8025::1: seq=18 ttl=59 time=61.270 ms
64 bytes from 2a03:4000:6:8025::1: seq=19 ttl=59 time=46.574 ms
64 bytes from 2a03:4000:6:8025::1: seq=20 ttl=59 time=57.736 ms
64 bytes from 2a03:4000:6:8025::1: seq=21 ttl=59 time=55.299 ms
64 bytes from 2a03:4000:6:8025::1: seq=22 ttl=59 time=46.737 ms
64 bytes from 2a03:4000:6:8025::1: seq=23 ttl=59 time=66.136 ms
64 bytes from 2a03:4000:6:8025::1: seq=24 ttl=59 time=56.749 ms
64 bytes from 2a03:4000:6:8025::1: seq=25 ttl=59 time=59.833 ms
64 bytes from 2a03:4000:6:8025::1: seq=26 ttl=59 time=55.091 ms
64 bytes from 2a03:4000:6:8025::1: seq=27 ttl=59 time=54.846 ms
64 bytes from 2a03:4000:6:8025::1: seq=28 ttl=59 time=51.903 ms
64 bytes from 2a03:4000:6:8025::1: seq=29 ttl=59 time=60.634 ms
64 bytes from 2a03:4000:6:8025::1: seq=30 ttl=59 time=70.933 ms
64 bytes from 2a03:4000:6:8025::1: seq=31 ttl=59 time=68.584 ms
64 bytes from 2a03:4000:6:8025::1: seq=32 ttl=59 time=48.319 ms
64 bytes from 2a03:4000:6:8025::1: seq=34 ttl=59 time=68.366 ms
64 bytes from 2a03:4000:6:8025::1: seq=35 ttl=59 time=60.524 ms
64 bytes from 2a03:4000:6:8025::1: seq=36 ttl=59 time=65.093 ms
64 bytes from 2a03:4000:6:8025::1: seq=37 ttl=59 time=65.785 ms
64 bytes from 2a03:4000:6:8025::1: seq=38 ttl=59 time=57.937 ms
64 bytes from 2a03:4000:6:8025::1: seq=39 ttl=59 time=45.157 ms
64 bytes from 2a03:4000:6:8025::1: seq=40 ttl=59 time=55.621 ms
64 bytes from 2a03:4000:6:8025::1: seq=41 ttl=59 time=55.638 ms
64 bytes from 2a03:4000:6:8025::1: seq=42 ttl=59 time=45.262 ms
64 bytes from 2a03:4000:6:8025::1: seq=43 ttl=59 time=58.180 ms
64 bytes from 2a03:4000:6:8025::1: seq=44 ttl=59 time=58.238 ms
64 bytes from 2a03:4000:6:8025::1: seq=45 ttl=59 time=50.398 ms
64 bytes from 2a03:4000:6:8025::1: seq=46 ttl=59 time=51.560 ms
64 bytes from 2a03:4000:6:8025::1: seq=47 ttl=59 time=48.116 ms
64 bytes from 2a03:4000:6:8025::1: seq=48 ttl=59 time=45.497 ms
64 bytes from 2a03:4000:6:8025::1: seq=49 ttl=59 time=45.116 ms
64 bytes from 2a03:4000:6:8025::1: seq=50 ttl=59 time=50.312 ms
64 bytes from 2a03:4000:6:8025::1: seq=51 ttl=59 time=53.371 ms
64 bytes from 2a03:4000:6:8025::1: seq=52 ttl=59 time=50.018 ms
64 bytes from 2a03:4000:6:8025::1: seq=53 ttl=59 time=53.557 ms
64 bytes from 2a03:4000:6:8025::1: seq=54 ttl=59 time=47.279 ms
64 bytes from 2a03:4000:6:8025::1: seq=55 ttl=59 time=55.888 ms
64 bytes from 2a03:4000:6:8025::1: seq=56 ttl=59 time=52.958 ms
64 bytes from 2a03:4000:6:8025::1: seq=57 ttl=59 time=50.438 ms
64 bytes from 2a03:4000:6:8025::1: seq=58 ttl=59 time=54.061 ms
64 bytes from 2a03:4000:6:8025::1: seq=59 ttl=59 time=60.419 ms
64 bytes from 2a03:4000:6:8025::1: seq=60 ttl=59 time=44.515 ms
64 bytes from 2a03:4000:6:8025::1: seq=61 ttl=59 time=60.511 ms
64 bytes from 2a03:4000:6:8025::1: seq=62 ttl=59 time=55.702 ms
64 bytes from 2a03:4000:6:8025::1: seq=63 ttl=59 time=48.466 ms
64 bytes from 2a03:4000:6:8025::1: seq=64 ttl=59 time=50.789 ms
64 bytes from 2a03:4000:6:8025::1: seq=65 ttl=59 time=48.814 ms
64 bytes from 2a03:4000:6:8025::1: seq=66 ttl=59 time=48.865 ms
64 bytes from 2a03:4000:6:8025::1: seq=67 ttl=59 time=48.151 ms
64 bytes from 2a03:4000:6:8025::1: seq=68 ttl=59 time=49.511 ms
64 bytes from 2a03:4000:6:8025::1: seq=69 ttl=59 time=57.969 ms
64 bytes from 2a03:4000:6:8025::1: seq=70 ttl=59 time=50.735 ms
64 bytes from 2a03:4000:6:8025::1: seq=71 ttl=59 time=55.944 ms
64 bytes from 2a03:4000:6:8025::1: seq=72 ttl=59 time=46.916 ms
64 bytes from 2a03:4000:6:8025::1: seq=73 ttl=59 time=48.126 ms
64 bytes from 2a03:4000:6:8025::1: seq=74 ttl=59 time=54.451 ms
64 bytes from 2a03:4000:6:8025::1: seq=75 ttl=59 time=64.815 ms
64 bytes from 2a03:4000:6:8025::1: seq=76 ttl=59 time=46.700 ms
64 bytes from 2a03:4000:6:8025::1: seq=77 ttl=59 time=45.689 ms
64 bytes from 2a03:4000:6:8025::1: seq=78 ttl=59 time=62.753 ms
64 bytes from 2a03:4000:6:8025::1: seq=79 ttl=59 time=52.019 ms
64 bytes from 2a03:4000:6:8025::1: seq=80 ttl=59 time=65.040 ms
64 bytes from 2a03:4000:6:8025::1: seq=81 ttl=59 time=69.480 ms
64 bytes from 2a03:4000:6:8025::1: seq=82 ttl=59 time=53.793 ms
64 bytes from 2a03:4000:6:8025::1: seq=83 ttl=59 time=57.366 ms
64 bytes from 2a03:4000:6:8025::1: seq=84 ttl=59 time=48.900 ms
64 bytes from 2a03:4000:6:8025::1: seq=85 ttl=59 time=52.968 ms
64 bytes from 2a03:4000:6:8025::1: seq=86 ttl=59 time=59.484 ms
64 bytes from 2a03:4000:6:8025::1: seq=87 ttl=59 time=56.175 ms
64 bytes from 2a03:4000:6:8025::1: seq=88 ttl=59 time=47.582 ms
64 bytes from 2a03:4000:6:8025::1: seq=89 ttl=59 time=55.338 ms
64 bytes from 2a03:4000:6:8025::1: seq=90 ttl=59 time=47.545 ms
64 bytes from 2a03:4000:6:8025::1: seq=91 ttl=59 time=47.586 ms
64 bytes from 2a03:4000:6:8025::1: seq=92 ttl=59 time=46.762 ms
64 bytes from 2a03:4000:6:8025::1: seq=93 ttl=59 time=61.301 ms
64 bytes from 2a03:4000:6:8025::1: seq=94 ttl=59 time=48.670 ms
64 bytes from 2a03:4000:6:8025::1: seq=95 ttl=59 time=69.831 ms
64 bytes from 2a03:4000:6:8025::1: seq=97 ttl=59 time=54.245 ms
64 bytes from 2a03:4000:6:8025::1: seq=98 ttl=59 time=58.284 ms
64 bytes from 2a03:4000:6:8025::1: seq=99 ttl=59 time=51.176 ms
64 bytes from 2a03:4000:6:8025::1: seq=100 ttl=59 time=64.379 ms
64 bytes from 2a03:4000:6:8025::1: seq=101 ttl=59 time=52.980 ms
64 bytes from 2a03:4000:6:8025::1: seq=102 ttl=59 time=46.629 ms
Hi,
es gibt in dem Netz halt viel mehr Router => mehr Originators, schlechtere Durchsätze.
Tunnel steht und auch die pings sehen gut aus
Hi Stefan,
habe an FFN-Router ganz ähnliche Probleme … (subjektiv; keine technischen Auswertungen)
Wie ist denn hier jetzt das Fazit?
kann man was machen oder ist mit „mehreren Originators“ der Durchsatz permanent schlechter?
Hallo,
natürlich, desto mehr Originators, desto mehr haben auch die Router zu tun.
Es ist immer schwer, aus der Ferne zu sagen, was da los.
Ggf. helfen uns auch schon Traces zu Zielen die Probleme machen weiter.
Stefan
Hallo,
gestern musste ich meine Steckdose umstecken und startete in diesem Zusammenhang die beiden Router durch. Das Spiel ging von vorne los: Ist eine Ursache / Grund erkennbar? Danke
OpenWRT Version: OpenWrt Chaos Calmer 15.05.1 (r49389)
Gluon Version: v2016.2.5-6-g97f44c20 Gluon Release: 20170530
Selected Hood: rastede
root@WesterstedeGaststr19Indoor:~# hoodselector
No VPN connection found
Testing neighboring adhoc networks for batman advanced gw connection.
The following wireless networks have been found:
0 2437 02:00:0a:12:a0:00 mesh.ffnw
After filtering we will test the following wireless networks:
0 2437 02:00:0a:12:a0:00 mesh.ffnw
Prepare configuration for testing wireless networks…
VPN stopped.
Testing IBSS 02:00:0a:12:a0:00…
VPN started.
Interface br-client restarted.
Wireless restarted.
Finished testing wireless networks, restored previous configuration
No neighboring freifunk batman advanced mesh found.
gluon-neighbour-info -i mesh-vpn -p 1001 -d ff02::2 -r hoodselector -t 0.5
Error in sendto(): Cannot assign requested address
No VPN routers over mesh on lan or wan
No molwm neighbors found
currend configuration are not defined as hood
VPN stopped.
Wireless restarted.
IBSS needed reconfiguration. Applied new settings and restarted.
Wireless restarted.
MESH needed reconfiguration. Applied new settings and restarted.
Fastd needed reconfiguration. Stopped and applied new settings.
VPN enable.
VPN started.
Interface br-client restarted.
VPN needed reconfiguration. Applied new settings and restarted.
Set hood „default“
Set defaulthood.
root@WesterstedeGaststr19Indoor:~# logread
Sun Jul 2 23:33:31 2017 kern.info kernel: [21337.680000] br-wan: port 2(wlan0-3 ) entered disabled state
Sun Jul 2 23:33:31 2017 kern.info kernel: [21337.680000] device wlan0-3 left pr omiscuous mode
Sun Jul 2 23:33:31 2017 kern.info kernel: [21337.690000] br-wan: port 2(wlan0-3 ) entered disabled state
Sun Jul 2 23:33:31 2017 kern.info kernel: [21337.730000] device client0 left pr omiscuous mode
Sun Jul 2 23:33:31 2017 kern.info kernel: [21337.740000] br-client: port 2(clie nt0) entered disabled state
Sun Jul 2 23:33:31 2017 daemon.notice netifd: Network device ‚ibss0‘ link is do wn
Sun Jul 2 23:33:31 2017 daemon.notice netifd: Network device ‚mesh0‘ link is do wn
Sun Jul 2 23:33:32 2017 daemon.notice netifd: Interface ‚client‘ is now up
Sun Jul 2 23:33:32 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Sun Jul 2 23:33:33 2017 daemon.notice netifd: radio0 (32707): Configuration fil e: /var/run/hostapd-phy0.conf
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.720000] IPv6: ADDRCONF(NETDEV_ UP): client0: link is not ready
Sun Jul 2 23:33:33 2017 daemon.notice netifd: radio0 (32707): client0: interfac e state UNINITIALIZED->COUNTRY_UPDATE
Sun Jul 2 23:33:33 2017 daemon.notice netifd: radio0 (32707): Using interface c lient0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid „nordwest.freifunk.net“
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.740000] device client0 entered promiscuous mode
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.770000] IPv6: ADDRCONF(NETDEV_ CHANGE): client0: link becomes ready
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.770000] br-client: port 2(clie nt0) entered forwarding state
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.780000] br-client: port 2(clie nt0) entered forwarding state
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.810000] device wlan0-3 entered promiscuous mode
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.820000] IPv6: ADDRCONF(NETDEV_ UP): wlan0-3: link is not ready
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.820000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:33:33 2017 kern.info kernel: [21339.830000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:33:33 2017 daemon.notice netifd: radio0 (32707): Using interface w lan0-3 with hwaddr 36:e2:c4:c7:fc:a3 and ssid „WLAN-871921“
Sun Jul 2 23:33:34 2017 daemon.notice netifd: radio0 (32707): client0: interfac e state COUNTRY_UPDATE->ENABLED
Sun Jul 2 23:33:34 2017 daemon.notice netifd: radio0 (32707): client0: AP-ENABL ED
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.540000] IPv6: ADDRCONF(NETDEV_ CHANGE): wlan0-3: link becomes ready
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.640000] IPv6: ADDRCONF(NETDEV_ UP): ibss0: link is not ready
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.680000] ibss0: Created IBSS us ing preconfigured BSSID 02:ca:ff:ee:ba:bf
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.680000] ibss0: Creating new IB SS network, BSSID 02:ca:ff:ee:ba:bf
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.690000] IPv6: ADDRCONF(NETDEV_ CHANGE): ibss0: link becomes ready
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Network device ‚ibss0‘ link is up
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.790000] IPv6: ADDRCONF(NETDEV_ UP): mesh0: link is not ready
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Network device ‚mesh0‘ link is up
Sun Jul 2 23:33:34 2017 kern.info kernel: [21340.820000] IPv6: ADDRCONF(NETDEV_ CHANGE): mesh0: link becomes ready
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is enable d
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ has link connectivity
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is setting up now
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is enabled
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ has link connectivity
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is setting up now
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Network device ‚client0‘ link is up
Sun Jul 2 23:33:34 2017 daemon.notice netifd: Network device ‚wlan0-3‘ link is up
Sun Jul 2 23:33:34 2017 daemon.notice netifd: wan (1373): Performing a DHCP renew
Sun Jul 2 23:33:34 2017 daemon.notice netifd: wan (1373): Sending renew…
Sun Jul 2 23:33:34 2017 daemon.notice netifd: wan (1373): Lease of 192.168.2.10 1 obtained, lease time 7200
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.460000] batman_adv: bat0: Adding interface: ibss0
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.470000] batman_adv: bat0: Interface activated: ibss0
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.520000] batman_adv: bat0: Adding interface: mesh0
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.530000] batman_adv: bat0: Interface activated: mesh0
Sun Jul 2 23:33:35 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is now up
Sun Jul 2 23:33:35 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is now up
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.780000] br-client: port 2(client0) entered forwarding state
Sun Jul 2 23:33:35 2017 kern.info kernel: [21341.830000] br-wan: port 2(wlan0-3) entered forwarding state
Sun Jul 2 23:33:45 2017 kern.info kernel: [21351.870000] IPv6: udp checksum is 0 for [2a01:4f8:221:1ec4::179]:11111->[2003:d2:be1:e219:34e2:c4ff:fec7:fca0]:49527
Sun Jul 2 23:33:49 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: authenticated
Sun Jul 2 23:33:49 2017 daemon.info hostapd: client0: STA b0:89:00:fb:54:3d IEEE 802.11: associated (aid 1)
Sun Jul 2 23:34:01 2017 daemon.notice fastd[32458]: terminating fastd
Sun Jul 2 23:34:01 2017 daemon.notice fastd[32458]: connection with <mesh_vpn_backbone_peer_default06_11111> disestablished.
Sun Jul 2 23:34:01 2017 daemon.info fastd[32458]: deleting peer <mesh_vpn_backbone_peer_default06_11111>
Sun Jul 2 23:34:01 2017 daemon.info fastd[32458]: deleting peer <mesh_vpn_backbone_peer_default06_11112>
Sun Jul 2 23:34:01 2017 kern.info kernel: [21367.380000] batman_adv: bat0: Interface deactivated: mesh-vpn
Sun Jul 2 23:34:01 2017 daemon.notice netifd: Network device ‚mesh-vpn‘ link is down
Sun Jul 2 23:34:01 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ has link connectivity loss
Sun Jul 2 23:34:01 2017 kern.info kernel: [21367.410000] batman_adv: bat0: Removing interface: mesh-vpn
Sun Jul 2 23:34:01 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is disabled
Sun Jul 2 23:34:02 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is disabled
Sun Jul 2 23:34:02 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ has link connectivity loss
Sun Jul 2 23:34:02 2017 kern.info kernel: [21369.050000] batman_adv: bat0: Interface deactivated: ibss0
Sun Jul 2 23:34:02 2017 kern.info kernel: [21369.060000] batman_adv: bat0: Removing interface: ibss0
Sun Jul 2 23:34:02 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is now down
Sun Jul 2 23:34:02 2017 daemon.notice netifd: Network device ‚wlan0-3‘ link is down
Sun Jul 2 23:34:02 2017 kern.info kernel: [21369.190000] br-wan: port 2(wlan0-3) entered disabled state
Sun Jul 2 23:34:02 2017 kern.info kernel: [21369.190000] device wlan0-3 left promiscuous mode
Sun Jul 2 23:34:02 2017 kern.info kernel: [21369.200000] br-wan: port 2(wlan0-3) entered disabled state
Sun Jul 2 23:34:03 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is disabled
Sun Jul 2 23:34:03 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ has link connectivity loss
Sun Jul 2 23:34:03 2017 kern.info kernel: [21369.290000] device client0 left promiscuous mode
Sun Jul 2 23:34:03 2017 kern.info kernel: [21369.290000] br-client: port 2(client0) entered disabled state
Sun Jul 2 23:34:03 2017 daemon.notice netifd: Network device ‚client0‘ link is down
Sun Jul 2 23:34:03 2017 kern.info kernel: [21369.630000] batman_adv: bat0: Interface deactivated: mesh0
Sun Jul 2 23:34:03 2017 daemon.notice netifd: Network device ‚mesh0‘ link is down
Sun Jul 2 23:34:03 2017 kern.info kernel: [21369.650000] batman_adv: bat0: Removing interface: mesh0
Sun Jul 2 23:34:03 2017 daemon.notice netifd: wan (1373): Performing a DHCP renew
Sun Jul 2 23:34:03 2017 daemon.notice netifd: wan (1373): Sending renew…
Sun Jul 2 23:34:03 2017 daemon.notice netifd: wan (1373): Lease of 192.168.2.10 1 obtained, lease time 7200
Sun Jul 2 23:34:03 2017 kern.info kernel: [21370.240000] batman_adv: bat0: Inte rface deactivated: primary0
Sun Jul 2 23:34:04 2017 kern.info kernel: [21370.290000] batman_adv: bat0: Remo ving interface: primary0
Sun Jul 2 23:34:04 2017 daemon.notice netifd: Network device ‚bat0‘ link is dow n
Sun Jul 2 23:34:04 2017 daemon.notice netifd: Interface ‚bat0‘ has link connect ivity loss
Sun Jul 2 23:34:04 2017 daemon.notice netifd: Interface ‚bat0‘ is now down
Sun Jul 2 23:34:04 2017 kern.info kernel: [21370.310000] br-client: port 3(bat0 ) entered disabled state
Sun Jul 2 23:34:04 2017 kern.info kernel: [21370.360000] device bat0 left promi scuous mode
Sun Jul 2 23:34:04 2017 kern.info kernel: [21370.360000] br-client: port 3(bat0 ) entered disabled state
Sun Jul 2 23:34:04 2017 daemon.notice netifd: Interface ‚bat0‘ is disabled
Sun Jul 2 23:34:04 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is now do wn
Sun Jul 2 23:34:05 2017 daemon.notice fastd[1120]: fastd v18 starting
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is enabled
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Network device ‚mesh-vpn‘ link is up
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ has link con nectivity
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is setting u p now
Sun Jul 2 23:34:05 2017 daemon.notice fastd[1120]: changed to UID 0, GID 800
Sun Jul 2 23:34:05 2017 daemon.info fastd[1120]: adding peer <mesh_vpn_backbone peer_ras01_10000>
Sun Jul 2 23:34:05 2017 daemon.info fastd[1120]: resolving host ras01.sn.ffnw. de' for peer <mesh_vpn_backbone_peer_ras01_10000>... Sun Jul 2 23:34:05 2017 daemon.info fastd[1120]: resolved host ras01.sn.ffnw.d e’ successfully
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Bridge ‚br-client‘ link is down
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚client‘ has link conne ctivity loss
Sun Jul 2 23:34:05 2017 kern.info kernel: [21371.470000] br-client: port 1(eth0 .1) entered disabled state
Sun Jul 2 23:34:05 2017 kern.info kernel: [21371.490000] br-client: port 1(eth0 .1) entered forwarding state
Sun Jul 2 23:34:05 2017 kern.info kernel: [21371.500000] br-client: port 1(eth0 .1) entered forwarding state
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Bridge ‚br-client‘ link is up
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚client‘ has link conne ctivity
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚client‘ is setting up now
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.100000] batman_adv: bat0: Addi ng interface: primary0
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.100000] batman_adv: bat0: Inte rface activated: primary0
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.110000] 8021q: adding VLAN 0 t o HW filter on device bat0
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.150000] batman_adv: bat0: Addi ng interface: mesh-vpn
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.150000] batman_adv: bat0: The MTU of interface mesh-vpn is too small (1312) to handle the transport of batman- adv packets. Packets going over this interface will be fragmented on layer2 whic h could impact the performance. Setting the MTU to 1532 would solve the problem.
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.180000] batman_adv: bat0: Inte rface activated: mesh-vpn
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚bat0‘ is enabled
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.190000] device bat0 entered pr omiscuous mode
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.190000] br-client: port 2(bat0 ) entered forwarding state
Sun Jul 2 23:34:05 2017 kern.info kernel: [21372.200000] br-client: port 2(bat0 ) entered forwarding state
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Network device ‚bat0‘ link is up
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚bat0‘ has link connect ivity
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚bat0‘ is setting up no w
Sun Jul 2 23:34:05 2017 daemon.notice netifd: Interface ‚bat0‘ is now up
Sun Jul 2 23:34:06 2017 kern.info kernel: [21372.460000] batman_adv: bat0: no_r ebroadcast: Changing from: disabled to: enabled
Sun Jul 2 23:34:06 2017 daemon.notice netifd: Interface ‚client‘ is now down
Sun Jul 2 23:34:06 2017 daemon.notice netifd: Interface ‚client‘ is setting up now
Sun Jul 2 23:34:06 2017 daemon.notice netifd: Interface ‚mesh_vpn‘ is now up
Sun Jul 2 23:34:06 2017 daemon.notice netifd: radio0 (922): Configuration file: /var/run/hostapd-phy0.conf
Sun Jul 2 23:34:06 2017 kern.info kernel: [21372.920000] IPv6: ADDRCONF(NETDEV UP): client0: link is not ready
Sun Jul 2 23:34:06 2017 daemon.info fastd[1120]: sending handshake to <mesh_vpn backbone_peer_ras01_10000>[[2a01:4f8:161:5205::23]:10000]…
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.010000] device client0 entered promiscuous mode
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.020000] br-client: port 3(clie nt0) entered forwarding state
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.020000] br-client: port 3(clie nt0) entered forwarding state
Sun Jul 2 23:34:06 2017 daemon.notice netifd: radio0 (922): client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Sun Jul 2 23:34:06 2017 daemon.notice netifd: radio0 (922): Using interface cli ent0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid „nordwest.freifunk.net“
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.120000] IPv6: ADDRCONF(NETDEV CHANGE): client0: link becomes ready
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.170000] device wlan0-3 entered promiscuous mode
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.180000] IPv6: ADDRCONF(NETDEV_ UP): wlan0-3: link is not ready
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.190000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:34:06 2017 kern.info kernel: [21373.200000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:34:07 2017 daemon.notice netifd: radio0 (922): Using interface wla n0-3 with hwaddr 36:e2:c4:c7:fc:a3 and ssid „WLAN-871921“
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.480000] br-wan: port 2(wlan0-3 ) entered disabled state
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.500000] br-client: port 1(eth0 .1) entered forwarding state
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.650000] batman_adv: bat0: Chan ging gw mode from: off to: client
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.680000] batman_adv: bat0: gw_s el_class: Changing from: 20 to: 1
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.680000] batman_adv: bat0: hop_ penalty: Changing from: 30 to: 15
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.710000] batman_adv: bat0: mult icast_mode: Changing from: enabled to: disabled
Sun Jul 2 23:34:07 2017 kern.info kernel: [21373.710000] batman_adv: bat0: orig interval: Changing from: 1000 to: 5000
Sun Jul 2 23:34:07 2017 kern.info kernel: [21374.200000] br-client: port 2(bat0 ) entered forwarding state
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.260000] IPv6: ADDRCONF(NETDEV CHANGE): wlan0-3: link becomes ready
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.270000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.280000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:34:08 2017 daemon.notice netifd: radio0 (922): client0: interface state COUNTRY_UPDATE->ENABLED
Sun Jul 2 23:34:08 2017 daemon.notice netifd: radio0 (922): client0: AP-ENABLED
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.480000] IPv6: ADDRCONF(NETDEV_ UP): ibss0: link is not ready
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.510000] ibss0: Created IBSS us ing preconfigured BSSID 02:00:0a:12:a0:00
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.520000] ibss0: Creating new IB SS network, BSSID 02:00:0a:12:a0:00
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.530000] IPv6: ADDRCONF(NETDEV_ CHANGE): ibss0: link becomes ready
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.650000] IPv6: ADDRCONF(NETDEV_ UP): mesh0: link is not ready
Sun Jul 2 23:34:08 2017 kern.info kernel: [21374.680000] IPv6: ADDRCONF(NETDEV_ CHANGE): mesh0: link becomes ready
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Network device ‚ibss0‘ link is up
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is enabled
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ has link connectivity
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is setting up now
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Network device ‚mesh0‘ link is up
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is enabled
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ has link connectivity
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is setting up now
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Network device ‚client0‘ link is up
Sun Jul 2 23:34:08 2017 kern.info kernel: [21375.020000] br-client: port 3(clie nt0) entered forwarding state
Sun Jul 2 23:34:08 2017 daemon.notice netifd: Network device ‚wlan0-3‘ link is up
Sun Jul 2 23:34:09 2017 daemon.notice netifd: wan (1373): Performing a DHCP ren ew
Sun Jul 2 23:34:09 2017 daemon.notice netifd: wan (1373): Sending renew…
Sun Jul 2 23:34:09 2017 daemon.notice netifd: wan (1373): Lease of 192.168.2.10 1 obtained, lease time 7200
Sun Jul 2 23:34:09 2017 kern.info kernel: [21375.680000] batman_adv: bat0: Addi ng interface: ibss0
Sun Jul 2 23:34:09 2017 kern.info kernel: [21375.690000] batman_adv: bat0: Inte rface activated: ibss0
Sun Jul 2 23:34:09 2017 kern.info kernel: [21375.700000] batman_adv: bat0: Addi ng interface: mesh0
Sun Jul 2 23:34:09 2017 kern.info kernel: [21375.710000] batman_adv: bat0: Inte rface activated: mesh0
Sun Jul 2 23:34:09 2017 daemon.notice netifd: Interface ‚ibss_radio0‘ is now up
Sun Jul 2 23:34:09 2017 daemon.notice netifd: Interface ‚mesh_radio0‘ is now up
Sun Jul 2 23:34:10 2017 kern.info kernel: [21376.280000] br-wan: port 2(wlan0-3 ) entered forwarding state
Sun Jul 2 23:34:17 2017 daemon.notice netifd: Interface ‚client‘ is now up
Sun Jul 2 23:34:17 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client)
Sun Jul 2 23:34:26 2017 daemon.info fastd[1120]: sending handshake to <mesh_vpn _backbone_peer_ras01_10000>[5.9.56.23:10000]…
Sun Jul 2 23:34:26 2017 daemon.info fastd[1120]: resolving host ras01.sn.ffnw. de' for peer <mesh_vpn_backbone_peer_ras01_10000>... Sun Jul 2 23:34:26 2017 daemon.info fastd[1120]: resolved host ras01.sn.ffnw.d e’ successfully
root@WesterstedeGaststr19Indoor:~# batctl gwl
Gateway (#/255) Nexthop [outgoingIF]: advertised uplink ban dwidth … [B.A.T.M.A.N. adv 2016.2, MainIF/MAC: primary0/36:e2:c4:c7:fc:a3 (bat 0)]
No gateways in range …
root@WesterstedeGaststr19Indoor:~# ping6 autoupdate.ffnw
PING autoupdate.ffnw (2a03:4000:6:8025::1): 56 data bytes
64 bytes from 2a03:4000:6:8025::1: seq=0 ttl=59 time=33.937 ms
64 bytes from 2a03:4000:6:8025::1: seq=1 ttl=59 time=32.242 ms
64 bytes from 2a03:4000:6:8025::1: seq=2 ttl=59 time=32.244 ms
64 bytes from 2a03:4000:6:8025::1: seq=3 ttl=59 time=31.935 ms
64 bytes from 2a03:4000:6:8025::1: seq=4 ttl=59 time=31.985 ms
64 bytes from 2a03:4000:6:8025::1: seq=5 ttl=59 time=32.096 ms
64 bytes from 2a03:4000:6:8025::1: seq=6 ttl=59 time=31.612 ms
64 bytes from 2a03:4000:6:8025::1: seq=7 ttl=59 time=32.059 ms
64 bytes from 2a03:4000:6:8025::1: seq=8 ttl=59 time=32.073 ms
64 bytes from 2a03:4000:6:8025::1: seq=9 ttl=59 time=31.881 ms
64 bytes from 2a03:4000:6:8025::1: seq=10 ttl=59 time=31.863 ms
Nein, uns ist nichts bekannt - alles läuft.
Bitte einmal Traceroutes zu diversen Zielen!