Hallo Malte,

root@WesterstedeGaststr19Indoor:~# hoodselector VPN connection found. Position found. 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 "rastede" Hood set by VPN mode.

Gruß Philipp

-----Original-Nachricht----- Betreff: Re: [Nordwest] Knoten kommt nicht mehr online Datum: 2017-06-08T22:23:32+0200 Von: "Malte Modler via Nordwest" nordwest@lists.ffnw.de An: "nordwest@lists.ffnw.de" nordwest@lists.ffnw.de

Hallo Philipp,

Für mich klingt es so, als würde der VPN-Tunnel nicht aufgebaut werden, das kann mehrere Ursachen haben, um diese zu ergründen bräuchtest du Zugriff auf deinen Router. Sofern du bei der Ersteinrichtung de Routers den Zugriff eingerichtet hast, kannst diesen kannst du diesen vor Ort mit SSH erreichen ( als Adresse kannst du dann node.ffnw verwenden, Username ist root)

Du kann dort den Befehl "hoodselector" ausführen, und dessen Ausgabe schreibst du hier als Antwort, dann sehen wir weiter.

Dieses Vorgehen hilft uns beim Verbessern der Software. :-)

Falls dir dieses Vorgehen zu langwierig ist, kannst du auch den Router über den Config-Modus zurück auf des Auslieferungszustand setzen.

LG Malte

_______________________________________________ Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest ?

Hallo,

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 Fri Jun 9 18:08:00 2017 daemon.notice netifd: Interface 'bat0' is enabled Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2483.600000] batman_adv: bat0: Adding interface: ibss0 Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2483.610000] batman_adv: bat0: Interface activated: ibss0 Fri Jun 9 18:08:00 2017 daemon.notice netifd: Network device 'bat0' link is up Fri Jun 9 18:08:00 2017 daemon.notice netifd: Interface 'bat0' has link connectivity Fri Jun 9 18:08:00 2017 daemon.notice netifd: Interface 'bat0' is setting up now Fri Jun 9 18:08:00 2017 daemon.notice netifd: Interface 'bat0' is now up Fri Jun 9 18:08:00 2017 daemon.notice netifd: Interface 'ibss_radio0' is now up Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2484.200000] batman_adv: bat0: Changing gw mode from: off to: client Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2484.240000] batman_adv: bat0: gw_sel_class: Changing from: 20 to: 1 Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2484.250000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15 Fri Jun 9 18:08:00 2017 kern.info kernel: [ 2484.250000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled Fri Jun 9 18:08:00 2017 user.notice root: hoodselector[29960]: The hoodselector is still running. Fri Jun 9 18:08:01 2017 kern.info kernel: [ 2484.280000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000 Fri Jun 9 18:08:02 2017 kern.info kernel: [ 2485.560000] br-client: port 2(bat0) entered forwarding state Fri Jun 9 18:08:23 2017 daemon.notice fastd[30186]: fastd v18 starting Fri Jun 9 18:08:23 2017 daemon.notice fastd[30186]: changed to UID 0, GID 800 Fri Jun 9 18:08:23 2017 daemon.info fastd[30186]: adding peer <mesh_vpn_backbone_peer_ras01_10000> Fri Jun 9 18:08:23 2017 daemon.info fastd[30186]: resolving host `ras01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer_ras01_10000>... Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'mesh_vpn' is enabled Fri Jun 9 18:08:23 2017 daemon.notice netifd: Network device 'mesh-vpn' link is up Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'mesh_vpn' is setting up now Fri Jun 9 18:08:23 2017 daemon.info fastd[30186]: resolved host `ras01.sn.ffnw.de' successfully Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.030000] br-client: port 2(bat0) entered disabled state Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.040000] br-client: port 1(eth0.1) entered disabled state Fri Jun 9 18:08:23 2017 daemon.notice netifd: Bridge 'br-client' link is down Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'client' has link connectivity loss Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.180000] br-client: port 2(bat0) entered forwarding state Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.180000] br-client: port 2(bat0) entered forwarding state Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.190000] br-client: port 1(eth0.1) entered forwarding state Fri Jun 9 18:08:23 2017 kern.info kernel: [ 2507.200000] br-client: port 1(eth0.1) entered forwarding state Fri Jun 9 18:08:23 2017 daemon.notice netifd: Bridge 'br-client' link is up Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'client' has link connectivity Fri Jun 9 18:08:23 2017 daemon.notice netifd: Interface 'client' is setting up now Fri Jun 9 18:08:24 2017 kern.info kernel: [ 2507.630000] batman_adv: bat0: Adding interface: mesh-vpn Fri Jun 9 18:08:24 2017 kern.info kernel: [ 2507.630000] 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. Fri Jun 9 18:08:24 2017 kern.info kernel: [ 2507.660000] batman_adv: bat0: Interface activated: mesh-vpn Fri Jun 9 18:08:24 2017 kern.info kernel: [ 2507.660000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled Fri Jun 9 18:08:24 2017 daemon.notice netifd: Interface 'client' is now down Fri Jun 9 18:08:24 2017 daemon.notice netifd: Interface 'client' is setting up now Fri Jun 9 18:08:24 2017 daemon.info fastd[30186]: sending handshake to <mesh_vpn_backbone_peer_ras01_10000>[[2a01:4f8:161:5205::23]:10000]... Fri Jun 9 18:08:24 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Fri Jun 9 18:08:25 2017 daemon.notice fastd[30186]: terminating fastd Fri Jun 9 18:08:25 2017 daemon.info fastd[30186]: deleting peer <mesh_vpn_backbone_peer_ras01_10000> Fri Jun 9 18:08:25 2017 daemon.notice netifd: Network device 'mesh-vpn' link is down Fri Jun 9 18:08:25 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity loss Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2508.430000] batman_adv: bat0: Interface deactivated: mesh-vpn Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2508.480000] batman_adv: bat0: Removing interface: mesh-vpn Fri Jun 9 18:08:25 2017 daemon.err respondd[30314]: Could not join multicast group on mesh-vpn: No such device Fri Jun 9 18:08:25 2017 daemon.notice netifd: Interface 'mesh_vpn' is disabled Fri Jun 9 18:08:25 2017 daemon.notice netifd: Network device 'ibss0' link is down Fri Jun 9 18:08:25 2017 daemon.notice netifd: Interface 'ibss_radio0' has link connectivity loss Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2508.790000] batman_adv: bat0: Interface deactivated: ibss0 Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2508.810000] batman_adv: bat0: Removing interface: ibss0 Fri Jun 9 18:08:25 2017 daemon.notice netifd: Interface 'ibss_radio0' is disabled Fri Jun 9 18:08:25 2017 daemon.notice netifd: Interface 'mesh_radio0' is disabled Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2509.180000] br-client: port 2(bat0) entered forwarding state Fri Jun 9 18:08:25 2017 kern.info kernel: [ 2509.200000] br-client: port 1(eth0.1) entered forwarding state Fri Jun 9 18:08:26 2017 kern.info kernel: [ 2509.290000] batman_adv: bat0: Interface deactivated: primary0 Fri Jun 9 18:08:26 2017 kern.info kernel: [ 2509.350000] batman_adv: bat0: Removing interface: primary0 Fri Jun 9 18:08:26 2017 kern.info kernel: [ 2509.410000] br-client: port 2(bat0) entered disabled state Fri Jun 9 18:08:26 2017 daemon.notice netifd: Network device 'bat0' link is down Fri Jun 9 18:08:26 2017 daemon.notice netifd: Interface 'bat0' has link connectivity loss Fri Jun 9 18:08:26 2017 daemon.notice netifd: Interface 'bat0' is now down Fri Jun 9 18:08:26 2017 kern.info kernel: [ 2509.470000] device bat0 left promiscuous mode Fri Jun 9 18:08:26 2017 kern.info kernel: [ 2509.470000] br-client: port 2(bat0) entered disabled state Fri Jun 9 18:08:26 2017 daemon.notice netifd: Interface 'bat0' is disabled Fri Jun 9 18:08:26 2017 daemon.notice netifd: ibss_radio0 (30360): ip: can't find device 'primary0' Fri Jun 9 18:08:27 2017 daemon.notice netifd: radio0 (30372): Configuration file: /var/run/hostapd-phy0.conf Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2510.880000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2510.910000] device client0 entered promiscuous mode Fri Jun 9 18:08:27 2017 daemon.notice netifd: radio0 (30372): client0: interface state UNINITIALIZED->COUNTRY_UPDATE Fri Jun 9 18:08:27 2017 daemon.notice netifd: radio0 (30372): Using interface client0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid "nordwest.freifunk.net" Fri Jun 9 18:08:27 2017 daemon.notice netifd: radio0 (30372): client0: interface state COUNTRY_UPDATE->ENABLED Fri Jun 9 18:08:27 2017 daemon.notice netifd: radio0 (30372): client0: AP-ENABLED Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2510.990000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2510.990000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2511.000000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2511.160000] IPv6: ADDRCONF(NETDEV_UP): ibss0: link is not ready Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2511.260000] ibss0: Created IBSS using preconfigured BSSID 02:00:0a:12:a0:00 Fri Jun 9 18:08:27 2017 kern.info kernel: [ 2511.260000] ibss0: Creating new IBSS network, BSSID 02:00:0a:12:a0:00 Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2511.270000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss0: link becomes ready Fri Jun 9 18:08:28 2017 daemon.notice netifd: Network device 'ibss0' link is up Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2511.480000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready Fri Jun 9 18:08:28 2017 daemon.notice netifd: Network device 'mesh0' link is up Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2511.520000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready Fri Jun 9 18:08:28 2017 daemon.notice fastd[30739]: fastd v18 starting Fri Jun 9 18:08:28 2017 daemon.notice fastd[30739]: changed to UID 0, GID 800 Fri Jun 9 18:08:28 2017 daemon.info fastd[30739]: adding peer <mesh_vpn_backbone_peer_default06_11112> Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'mesh_vpn' is enabled Fri Jun 9 18:08:28 2017 daemon.notice netifd: Network device 'mesh-vpn' link is up Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'mesh_vpn' is setting up now Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.090000] br-client: port 2(client0) entered disabled state Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.100000] br-client: port 1(eth0.1) entered disabled state Fri Jun 9 18:08:28 2017 daemon.notice netifd: Bridge 'br-client' link is down Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'client' has link connectivity loss Fri Jun 9 18:08:28 2017 daemon.info fastd[30739]: adding peer <mesh_vpn_backbone_peer_default06_11111> Fri Jun 9 18:08:28 2017 daemon.info fastd[30739]: resolving host `default06.ffnw.de' for peer <mesh_vpn_backbone_peer_default06_11111>... Fri Jun 9 18:08:28 2017 daemon.info fastd[30739]: resolving host `default06.ffnw.de' for peer <mesh_vpn_backbone_peer_default06_11112>... Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.150000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.160000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.170000] br-client: port 1(eth0.1) entered forwarding state Fri Jun 9 18:08:28 2017 kern.info kernel: [ 2512.170000] br-client: port 1(eth0.1) entered forwarding state Fri Jun 9 18:08:28 2017 daemon.notice netifd: Bridge 'br-client' link is up Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'client' has link connectivity Fri Jun 9 18:08:28 2017 daemon.notice netifd: Interface 'client' is setting up now Fri Jun 9 18:08:28 2017 daemon.info fastd[30739]: resolved host `default06.ffnw.de' successfully Fri Jun 9 18:08:29 2017 daemon.info fastd[30739]: resolved host `default06.ffnw.de' successfully Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.400000] batman_adv: bat0: Adding interface: primary0 Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.400000] batman_adv: bat0: Interface activated: primary0 Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.410000] 8021q: adding VLAN 0 to HW filter on device bat0 Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.420000] batman_adv: bat0: Adding interface: mesh-vpn Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.420000] 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. Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.450000] batman_adv: bat0: Interface activated: mesh-vpn Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'bat0' is enabled Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.460000] device bat0 entered promiscuous mode Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.460000] br-client: port 3(bat0) entered forwarding state Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.470000] br-client: port 3(bat0) entered forwarding state Fri Jun 9 18:08:29 2017 daemon.notice netifd: Network device 'bat0' link is up Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'bat0' has link connectivity Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'bat0' is setting up now Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'bat0' is now up Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2512.540000] batman_adv: bat0: no_rebroadcast: Changing from: disabled to: enabled Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'mesh_vpn' is now up Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2513.060000] batman_adv: bat0: Changing gw mode from: off to: client Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2513.060000] batman_adv: bat0: gw_sel_class: Changing from: 20 to: 1 Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'client' is now down Fri Jun 9 18:08:29 2017 daemon.notice netifd: Interface 'client' is setting up now Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2513.110000] batman_adv: bat0: hop_penalty: Changing from: 30 to: 15 Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2513.110000] batman_adv: bat0: multicast_mode: Changing from: enabled to: disabled Fri Jun 9 18:08:29 2017 kern.info kernel: [ 2513.170000] batman_adv: bat0: orig_interval: Changing from: 1000 to: 5000 Fri Jun 9 18:08:30 2017 daemon.info fastd[30739]: sending handshake to <mesh_vp n_backbone_peer_default06_11112>[[2a01:4f8:221:1ec4::179]:11112]... Fri Jun 9 18:08:30 2017 daemon.info fastd[30739]: received handshake response f rom <mesh_vpn_backbone_peer_default06_11112>[[2a01:4f8:221:1ec4::179]:11112] usi ng fastd v18 Fri Jun 9 18:08:30 2017 daemon.info fastd[30739]: [2a01:4f8:221:1ec4::179]:1111 2 authorized as <mesh_vpn_backbone_peer_default06_11112> Fri Jun 9 18:08:30 2017 daemon.notice fastd[30739]: connection with <mesh_vpn_b ackbone_peer_default06_11112> established. Fri Jun 9 18:08:30 2017 daemon.info fastd[30739]: new session with <mesh_vpn_ba ckbone_peer_default06_11112> established using method `salsa2012+umac'. Fri Jun 9 18:08:30 2017 kern.info kernel: [ 2514.160000] br-client: port 2(clie nt0) entered forwarding state Fri Jun 9 18:08:30 2017 kern.info kernel: [ 2514.170000] br-client: port 1(eth0 .1) entered forwarding state Fri Jun 9 18:08:31 2017 kern.info kernel: [ 2514.470000] br-client: port 3(bat0 ) entered forwarding state Fri Jun 9 18:08:38 2017 kern.info kernel: [ 2521.790000] device client0 left pr omiscuous mode Fri Jun 9 18:08:38 2017 kern.info kernel: [ 2521.790000] br-client: port 2(client0) entered disabled state Fri Jun 9 18:08:38 2017 daemon.notice netifd: Network device 'ibss0' link is down Fri Jun 9 18:08:38 2017 daemon.notice netifd: Network device 'mesh0' link is down Fri Jun 9 18:08:39 2017 daemon.notice netifd: radio0 (30954): Configuration file: /var/run/hostapd-phy0.conf Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2522.850000] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2522.870000] device client0 entered promiscuous mode Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2522.870000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2522.880000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:39 2017 daemon.notice netifd: radio0 (30954): client0: interface state UNINITIALIZED->COUNTRY_UPDATE Fri Jun 9 18:08:39 2017 daemon.notice netifd: radio0 (30954): Using interface client0 with hwaddr 36:e2:c4:c7:fc:a0 and ssid "nordwest.freifunk.net" Fri Jun 9 18:08:39 2017 daemon.notice netifd: radio0 (30954): client0: interface state COUNTRY_UPDATE->ENABLED Fri Jun 9 18:08:39 2017 daemon.notice netifd: radio0 (30954): client0: AP-ENABLED Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2522.910000] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.070000] IPv6: ADDRCONF(NETDEV_UP): ibss0: link is not ready Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.100000] ibss0: Created IBSS using preconfigured BSSID 02:ca:ff:ee:ba:bf Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.110000] ibss0: Creating new IBSS network, BSSID 02:ca:ff:ee:ba:bf Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.110000] IPv6: ADDRCONF(NETDEV_CHANGE): ibss0: link becomes ready Fri Jun 9 18:08:39 2017 daemon.notice netifd: Network device 'ibss0' link is up Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.190000] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready Fri Jun 9 18:08:39 2017 daemon.notice netifd: Network device 'mesh0' link is up Fri Jun 9 18:08:39 2017 kern.info kernel: [ 2523.200000] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'ibss_radio0' is enabled Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'ibss_radio0' has link connectivity Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'ibss_radio0' is setting up now Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'mesh_radio0' is enabled Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'mesh_radio0' has linkconnectivity Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'mesh_radio0' is setting up now Fri Jun 9 18:08:40 2017 daemon.notice netifd: Network device 'client0' link is up Fri Jun 9 18:08:40 2017 kern.info kernel: [ 2523.620000] batman_adv: bat0: Adding interface: mesh0 Fri Jun 9 18:08:40 2017 kern.info kernel: [ 2523.630000] batman_adv: bat0: Interface activated: mesh0 Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'mesh_radio0' is now up Fri Jun 9 18:08:40 2017 kern.info kernel: [ 2523.710000] batman_adv: bat0: Adding interface: ibss0 Fri Jun 9 18:08:40 2017 kern.info kernel: [ 2523.720000] batman_adv: bat0: Interface activated: ibss0 Fri Jun 9 18:08:40 2017 daemon.notice netifd: Interface 'ibss_radio0' is now up Fri Jun 9 18:08:41 2017 daemon.notice netifd: Interface 'client' is now up Fri Jun 9 18:08:41 2017 kern.info kernel: [ 2524.880000] br-client: port 2(client0) entered forwarding state Fri Jun 9 18:08:42 2017 user.notice firewall: Reloading firewall due to ifup of client (br-client) Fri Jun 9 18:09:04 2017 daemon.info dnsmasq[1592]: reading /tmp/resolv.conf.auto Fri Jun 9 18:09:04 2017 daemon.info dnsmasq[1592]: using local addresses only for domain lan Fri Jun 9 18:09:04 2017 daemon.info dnsmasq[1592]: using nameserver 2a03:b0c0:3:d0::bd6:b001#53 Fri Jun 9 18:09:04 2017 daemon.info dnsmasq[1592]: using nameserver 2001:67c:18e8:0:2::181#53 Fri Jun 9 18:09:04 2017 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)

Gruß Philipp

-----Original-Nachricht----- Betreff: Re: [Nordwest] Knoten kommt nicht mehr online Datum: 2017-06-09T14:53:38+0200 Von: "Malte Modler via Nordwest" nordwest@lists.ffnw.de An: "nordwest@lists.ffnw.de" nordwest@lists.ffnw.de

Hi,

root@WesterstedeGaststr19Indoor:~# hoodselector VPN connection found. Position found. 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 "rastede" Hood set by VPN mode.

Joa das sieht schon mal gut aus...

jetzt wäre die Ausgabe des Befehls "logread" interessant.

Und magst du schreiben was für einen Internetanschluss du verwendest? (Anbieter, uplink, downlink)

LG Malte _______________________________________________ Nordwest mailing list Nordwest@lists.ffnw.de https://lists.ffnw.de/mailman/listinfo/nordwest ?