Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- $ ssh FF-WKP-Privat-01
- BusyBox v1.25.1 () built-in shell (ash)
- _______ __ ___ __
- | ___|.----.-----.|__|.' _|.--.--.-----.| |--.
- | ___|| _| -__|| || _|| | | || <
- |___| |__| |_____||__||__| |_____|__|__||__|__|
- _______ __ Freie Netze fuer alle! __
- | | |.-----.----.--| |.--.--.--.-----.-----.| |_
- | || _ | _| _ || | | | -__|__ --|| _|
- |__|____||_____|__| |_____||________|_____|_____||____|
- ##############################################################################
- _________
- / /\ _ ___ ___ ___
- / LE / \ | | | __| \| __|
- / DE / \ | |__| _|| |) | _|
- /________/ LE \ |____|___|___/|___| lede-project.org
- \ \ DE /
- \ LE \ /
- \ DE \ /
- \________\/
- ------------------------------------------------------------------------------
- LEDE Version: LEDE Reboot 17.01-SNAPSHOT r3881+51-999bb66b20 (r3881+51-999bb66b20)
- Gluon Version: v2017.1.8-7-g8e371e86 Gluon Release: 20180709
- Selected Hood: landkreis-steinfurt
- ------------------------------------------------------------------------------
- root@FF-WKP-Privat-01:~# uptime
- 09:36:48 up 2 days, 23:27, load average: 11.75, 10.85, 10.43
- root@FF-WKP-Privat-01:~# logread
- Tue Sep 4 16:53:47 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 16:53:48 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 16:54:09 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 16:54:29 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 16:54:48 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 16:54:49 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 16:54:58 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 16:54:58 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 16:56:27 2018 user.notice root: hoodselector[23459]: The hoodselector is still running.
- Tue Sep 4 17:04:44 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:05:26 2018 daemon.notice hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 17:07:48 2018 user.notice root: hoodselector[23640]: The hoodselector is still running.
- Tue Sep 4 17:09:21 2018 daemon.info hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: disassociated due to inactivity
- Tue Sep 4 17:09:33 2018 daemon.info hostapd: client0: STA ec:1f:72:d4:c2:36 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
- Tue Sep 4 17:15:20 2018 user.notice root: hoodselector[23747]: The hoodselector is still running.
- Tue Sep 4 17:17:55 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
- Tue Sep 4 17:17:58 2018 daemon.notice hostapd: client0: AP-DISABLED
- Tue Sep 4 17:18:03 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
- Tue Sep 4 17:18:13 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
- Tue Sep 4 17:18:13 2018 daemon.notice netifd: radio0 (23799): Command failed: Request timed out
- Tue Sep 4 17:18:14 2018 kern.info kernel: [198510.050757] device client0 left promiscuous mode
- Tue Sep 4 17:18:14 2018 kern.info kernel: [198510.055861] br-client: port 4(client0) entered disabled state
- Tue Sep 4 17:18:32 2018 daemon.notice netifd: Network device 'client0' link is down
- Tue Sep 4 17:19:13 2018 kern.info kernel: [198566.213845] batman_adv: bat0: Interface deactivated: mesh0
- Tue Sep 4 17:19:27 2018 daemon.notice netifd: Network device 'mesh0' link is down
- Tue Sep 4 17:19:27 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Tue Sep 4 17:19:35 2018 kern.info kernel: [198589.108253] batman_adv: bat0: Removing interface: mesh0
- Tue Sep 4 17:19:36 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Tue Sep 4 17:21:03 2018 user.notice root: hoodselector[23926]: The hoodselector is still running.
- Tue Sep 4 17:25:37 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Tue Sep 4 17:25:39 2018 kern.info kernel: [198954.103925] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Tue Sep 4 17:25:52 2018 kern.info kernel: [198965.617202] device client0 entered promiscuous mode
- Tue Sep 4 17:26:12 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Tue Sep 4 17:26:29 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Tue Sep 4 17:26:29 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Tue Sep 4 17:26:29 2018 daemon.notice hostapd: client0: AP-ENABLED
- Tue Sep 4 17:26:29 2018 kern.info kernel: [199004.246878] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Tue Sep 4 17:26:29 2018 kern.info kernel: [199004.253955] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 17:26:29 2018 kern.info kernel: [199004.260331] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 17:26:36 2018 kern.info kernel: [199006.256489] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 17:26:36 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 17:27:26 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 17:28:55 2018 kern.info kernel: [199135.402263] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
- Tue Sep 4 17:29:41 2018 kern.info kernel: [199193.608579] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
- Tue Sep 4 17:29:42 2018 daemon.notice netifd: Network device 'mesh0' link is up
- Tue Sep 4 17:31:27 2018 user.notice root: hoodselector[24298]: The hoodselector is still running.
- Tue Sep 4 17:32:57 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
- Tue Sep 4 17:32:58 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
- Tue Sep 4 17:32:58 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
- Tue Sep 4 17:32:58 2018 daemon.notice netifd: Network device 'client0' link is up
- Tue Sep 4 17:33:22 2018 daemon.notice netifd: radio0 (23956): Command failed: Request timed out
- Tue Sep 4 17:34:25 2018 daemon.notice netifd: mesh_radio0 (24385): ip: SIOCSIFMTU: No such device
- Tue Sep 4 17:35:14 2018 daemon.notice netifd: Interface 'mesh_radio0' is now up
- Tue Sep 4 17:37:54 2018 daemon.info respondd[24512]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 17:38:49 2018 kern.info kernel: [199733.708630] batman_adv: bat0: Adding interface: mesh0
- Tue Sep 4 17:38:49 2018 kern.info kernel: [199733.713966] batman_adv: bat0: Interface activated: mesh0
- Tue Sep 4 17:45:28 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 17:45:37 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 17:45:37 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 17:45:50 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 17:45:50 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 17:48:34 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 17:56:04 2018 user.notice root: hoodselector[24854]: The hoodselector is still running.
- Tue Sep 4 17:56:04 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 17:59:44 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:00:14 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:00:28 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:00:38 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 18:00:44 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:03 2018 user.notice root: hoodselector[24930]: The hoodselector is still running.
- Tue Sep 4 18:01:17 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:22 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:01:27 2018 daemon.notice hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: did not acknowledge authentication response
- Tue Sep 4 18:04:24 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 18:04:46 2018 daemon.info hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: disassociated due to inactivity
- Tue Sep 4 18:04:46 2018 daemon.info hostapd: client0: STA 24:18:1d:44:bc:c1 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
- Tue Sep 4 18:05:05 2018 daemon.info respondd[25042]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 18:06:13 2018 user.notice root: hoodselector[25031]: The hoodselector is still running.
- Tue Sep 4 18:09:08 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 18:20:24 2018 user.notice root: hoodselector[25295]: The hoodselector is still running.
- Tue Sep 4 18:37:48 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 18:37:55 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 18:38:01 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 18:38:12 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 18:38:12 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 18:41:42 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 18:47:39 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 18:50:11 2018 user.notice root: hoodselector[25918]: The hoodselector is still running.
- Tue Sep 4 18:53:38 2018 user.notice root: hoodselector[25975]: The hoodselector is still running.
- Tue Sep 4 19:01:34 2018 user.notice root: hoodselector[26117]: The hoodselector is still running.
- Tue Sep 4 19:16:49 2018 daemon.err hostapd: eloop: could not process SIGINT or SIGTERM in two seconds. Looks like there
- is a bug that ends up in a busy loop that prevents clean shutdown.
- Killing program forcefully.
- Tue Sep 4 19:17:10 2018 kern.info kernel: [205640.282137] br-client: port 4(client0) entered disabled state
- Tue Sep 4 19:17:10 2018 kern.info kernel: [205641.223198] device client0 left promiscuous mode
- Tue Sep 4 19:17:10 2018 kern.info kernel: [205641.228144] br-client: port 4(client0) entered disabled state
- Tue Sep 4 19:17:10 2018 daemon.notice netifd: Network device 'client0' link is down
- Tue Sep 4 19:17:20 2018 kern.info kernel: [205648.124474] batman_adv: bat0: Interface deactivated: mesh0
- Tue Sep 4 19:17:38 2018 daemon.notice netifd: Network device 'mesh0' link is down
- Tue Sep 4 19:17:38 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Tue Sep 4 19:17:52 2018 kern.info kernel: [205677.443115] batman_adv: bat0: Removing interface: mesh0
- Tue Sep 4 19:17:52 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Tue Sep 4 19:20:35 2018 daemon.notice netifd: wan6 (1485): Command failed: Request timed out
- Tue Sep 4 19:21:18 2018 user.notice root: hoodselector[26540]: The hoodselector is still running.
- Tue Sep 4 19:21:22 2018 daemon.info procd: Instance gluon-respondd::instance1 pid 25042 not stopped on SIGTERM, sending SIGKILL instead
- Tue Sep 4 19:21:27 2018 daemon.info respondd[26569]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 19:25:33 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Tue Sep 4 19:25:45 2018 kern.info kernel: [206156.236180] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Tue Sep 4 19:25:45 2018 kern.info kernel: [206156.424349] device client0 entered promiscuous mode
- Tue Sep 4 19:25:45 2018 kern.info kernel: [206156.429652] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 19:25:45 2018 kern.info kernel: [206156.435996] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 19:25:45 2018 kern.info kernel: [206156.926116] br-client: port 4(client0) entered disabled state
- Tue Sep 4 19:26:05 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Tue Sep 4 19:26:26 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Tue Sep 4 19:26:29 2018 kern.info kernel: [206190.774934] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Tue Sep 4 19:26:29 2018 kern.info kernel: [206190.782114] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 19:26:29 2018 kern.info kernel: [206190.788474] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 19:26:29 2018 kern.info kernel: [206192.826189] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 19:26:30 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Tue Sep 4 19:26:30 2018 daemon.notice hostapd: client0: AP-ENABLED
- Tue Sep 4 19:26:36 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 19:27:52 2018 kern.info kernel: [206284.222910] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
- Tue Sep 4 19:28:04 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 19:28:11 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 19:28:29 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 19:28:29 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 19:28:38 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 19:28:39 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 19:29:12 2018 kern.info kernel: [206365.497765] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
- Tue Sep 4 19:29:12 2018 daemon.notice netifd: Network device 'mesh0' link is up
- Tue Sep 4 19:30:51 2018 user.notice root: hoodselector[26894]: The hoodselector is still running.
- Tue Sep 4 19:31:41 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 19:32:36 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
- Tue Sep 4 19:32:36 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
- Tue Sep 4 19:32:36 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
- Tue Sep 4 19:32:36 2018 daemon.notice netifd: Network device 'client0' link is up
- Tue Sep 4 19:33:35 2018 daemon.notice netifd: mesh_radio0 (26966): ip: SIOCSIFMTU: No such device
- Tue Sep 4 19:34:43 2018 daemon.notice netifd: Interface 'mesh_radio0' is now up
- Tue Sep 4 19:37:29 2018 kern.info kernel: [206862.681019] batman_adv: bat0: Adding interface: mesh0
- Tue Sep 4 19:37:29 2018 kern.info kernel: [206862.686446] batman_adv: bat0: Interface activated: mesh0
- Tue Sep 4 19:38:09 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 19:39:31 2018 daemon.info procd: Instance gluon-respondd::instance1 pid 26569 not stopped on SIGTERM, sending SIGKILL instead
- Tue Sep 4 19:40:05 2018 daemon.info respondd[27162]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 19:40:42 2018 user.notice root: hoodselector[27136]: The hoodselector is still running.
- Tue Sep 4 19:41:59 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 19:44:37 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 19:56:34 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 20:00:04 2018 user.notice root: hoodselector[27537]: The hoodselector is still running.
- Tue Sep 4 20:19:25 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 20:19:30 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 20:19:31 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 20:19:38 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 20:19:39 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 20:21:42 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 20:31:56 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 20:37:28 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 20:44:22 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 20:50:56 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
- Tue Sep 4 20:51:01 2018 daemon.notice hostapd: client0: AP-DISABLED
- Tue Sep 4 20:51:01 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
- Tue Sep 4 20:51:23 2018 daemon.notice netifd: radio0 (28443): Command failed: Request timed out
- Tue Sep 4 20:51:23 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
- Tue Sep 4 20:51:23 2018 kern.info kernel: [211297.886192] device client0 left promiscuous mode
- Tue Sep 4 20:51:23 2018 kern.info kernel: [211297.891282] br-client: port 4(client0) entered disabled state
- Tue Sep 4 20:51:40 2018 daemon.notice netifd: Network device 'client0' link is down
- Tue Sep 4 20:52:46 2018 kern.info kernel: [211378.548876] batman_adv: bat0: Interface deactivated: mesh0
- Tue Sep 4 20:52:50 2018 daemon.notice netifd: Network device 'mesh0' link is down
- Tue Sep 4 20:52:50 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Tue Sep 4 20:52:55 2018 kern.info kernel: [211388.654044] batman_adv: bat0: Removing interface: mesh0
- Tue Sep 4 20:53:05 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Tue Sep 4 20:55:10 2018 daemon.info respondd[28630]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 21:00:21 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Tue Sep 4 21:00:45 2018 kern.info kernel: [211859.409873] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Tue Sep 4 21:00:45 2018 kern.info kernel: [211859.503164] device client0 entered promiscuous mode
- Tue Sep 4 21:00:45 2018 kern.info kernel: [211859.508546] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 21:00:45 2018 kern.info kernel: [211859.514800] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 21:00:45 2018 kern.info kernel: [211859.792979] br-client: port 4(client0) entered disabled state
- Tue Sep 4 21:00:52 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Tue Sep 4 21:01:38 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Tue Sep 4 21:01:39 2018 kern.info kernel: [211915.812254] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Tue Sep 4 21:01:39 2018 kern.info kernel: [211915.819429] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 21:01:39 2018 kern.info kernel: [211915.825758] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 21:01:43 2018 kern.info kernel: [211917.817684] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 21:01:48 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Tue Sep 4 21:01:56 2018 daemon.notice hostapd: client0: AP-ENABLED
- Tue Sep 4 21:02:14 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 21:03:13 2018 kern.info kernel: [212009.008835] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
- Tue Sep 4 21:04:12 2018 kern.info kernel: [212066.753289] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
- Tue Sep 4 21:04:23 2018 daemon.notice netifd: Network device 'mesh0' link is up
- Tue Sep 4 21:07:04 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
- Tue Sep 4 21:07:04 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
- Tue Sep 4 21:07:04 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
- Tue Sep 4 21:07:04 2018 daemon.notice netifd: Network device 'client0' link is up
- Tue Sep 4 21:08:23 2018 daemon.notice netifd: mesh_radio0 (28966): ip: SIOCSIFMTU: No such device
- Tue Sep 4 21:09:10 2018 daemon.notice netifd: Interface 'mesh_radio0' is now up
- Tue Sep 4 21:11:10 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 21:11:11 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 21:11:12 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 21:11:20 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 21:11:20 2018 kern.info kernel: [212494.574267] batman_adv: bat0: Adding interface: mesh0
- Tue Sep 4 21:11:20 2018 kern.info kernel: [212494.579605] batman_adv: bat0: Interface activated: mesh0
- Tue Sep 4 21:11:33 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 21:11:33 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 21:13:37 2018 daemon.info respondd[29174]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 21:16:06 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 21:21:21 2018 user.notice root: hoodselector[29294]: The hoodselector is still running.
- Tue Sep 4 21:31:31 2018 user.notice root: hoodselector[29508]: The hoodselector is still running.
- Tue Sep 4 21:35:36 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 21:36:04 2018 user.notice root: hoodselector[29586]: The hoodselector is still running.
- Tue Sep 4 21:45:26 2018 user.notice root: hoodselector[29784]: The hoodselector is still running.
- Tue Sep 4 22:01:16 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 22:01:18 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 22:01:22 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 22:01:29 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 22:01:29 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 22:06:13 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 22:07:20 2018 user.notice root: hoodselector[30197]: The hoodselector is still running.
- Tue Sep 4 22:29:40 2018 user.notice root: hoodselector[30576]: The hoodselector is still running.
- Tue Sep 4 22:34:35 2018 daemon.notice netifd: wan6 (1485): cat: write error: Broken pipe
- Tue Sep 4 22:35:01 2018 daemon.notice fastd[1886]: connection with <mesh_vpn_backbone_peer__10001> disestablished.
- Tue Sep 4 22:35:01 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Tue Sep 4 22:35:09 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Tue Sep 4 22:35:16 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 22:35:17 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 22:35:18 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 22:35:18 2018 daemon.notice fastd[1886]: connection with <mesh_vpn_backbone_peer__10001> established.
- Tue Sep 4 22:35:18 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 22:36:43 2018 user.notice firewall: Reloading firewall due to ifupdate of wan6 (br-wan)
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:53 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:57 2018 daemon.err respondd[29174]: sendto failed: Operation not permitted
- Tue Sep 4 22:39:57 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:57 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:39:57 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:40:13 2018 daemon.warn fastd[1886]: sendmsg: Operation not permitted
- Tue Sep 4 22:41:29 2018 user.notice root: hoodselector[30899]: The hoodselector is still running.
- Tue Sep 4 22:49:50 2018 user.notice root: hoodselector[31078]: The hoodselector is still running.
- Tue Sep 4 22:53:58 2018 daemon.err hostapd: eloop: could not process SIGINT or SIGTERM in two seconds. Looks like there
- is a bug that ends up in a busy loop that prevents clean shutdown.
- Killing program forcefully.
- Tue Sep 4 22:54:21 2018 kern.info kernel: [218674.440689] br-client: port 4(client0) entered disabled state
- Tue Sep 4 22:54:30 2018 daemon.notice netifd: Network device 'client0' link is down
- Tue Sep 4 22:54:35 2018 kern.info kernel: [218689.112512] device client0 left promiscuous mode
- Tue Sep 4 22:54:35 2018 kern.info kernel: [218689.117500] br-client: port 4(client0) entered disabled state
- Tue Sep 4 22:54:41 2018 kern.info kernel: [218695.754241] batman_adv: bat0: Interface deactivated: mesh0
- Tue Sep 4 22:54:54 2018 daemon.notice netifd: Network device 'mesh0' link is down
- Tue Sep 4 22:54:54 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Tue Sep 4 22:54:54 2018 kern.info kernel: [218708.395583] batman_adv: bat0: Removing interface: mesh0
- Tue Sep 4 22:54:55 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Tue Sep 4 22:59:50 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Tue Sep 4 23:00:03 2018 kern.info kernel: [219015.628797] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Tue Sep 4 23:00:12 2018 kern.info kernel: [219023.844360] device client0 entered promiscuous mode
- Tue Sep 4 23:00:12 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Tue Sep 4 23:00:18 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Tue Sep 4 23:00:18 2018 kern.info kernel: [219033.535451] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Tue Sep 4 23:00:18 2018 kern.info kernel: [219033.542546] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 23:00:18 2018 kern.info kernel: [219033.548940] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 23:00:20 2018 kern.info kernel: [219035.670238] br-client: port 4(client0) entered forwarding state
- Tue Sep 4 23:00:20 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Tue Sep 4 23:00:20 2018 daemon.notice hostapd: client0: AP-ENABLED
- Tue Sep 4 23:01:34 2018 kern.info kernel: [219103.674510] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
- Tue Sep 4 23:02:07 2018 kern.info kernel: [219139.694202] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
- Tue Sep 4 23:02:13 2018 daemon.notice netifd: Network device 'mesh0' link is up
- Tue Sep 4 23:05:38 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
- Tue Sep 4 23:05:44 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
- Tue Sep 4 23:05:44 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
- Tue Sep 4 23:05:51 2018 daemon.notice netifd: Network device 'client0' link is up
- Tue Sep 4 23:05:53 2018 user.notice root: hoodselector[31656]: The hoodselector is still running.
- Tue Sep 4 23:06:32 2018 daemon.notice netifd: client (1481): Command failed: Request timed out
- Tue Sep 4 23:06:32 2018 daemon.notice netifd: client (1481): Command failed: Request timed out
- Tue Sep 4 23:06:32 2018 daemon.notice netifd: wan6 (1485): Command failed: Request timed out
- Tue Sep 4 23:07:34 2018 daemon.notice netifd: mesh_radio0 (31691): ip: SIOCSIFMTU: No such device
- Tue Sep 4 23:07:40 2018 daemon.info respondd[31750]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 23:08:03 2018 daemon.notice netifd: Interface 'mesh_radio0' is now up
- Tue Sep 4 23:10:48 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 23:11:15 2018 kern.info kernel: [219690.658904] batman_adv: bat0: Adding interface: mesh0
- Tue Sep 4 23:11:15 2018 kern.info kernel: [219690.664349] batman_adv: bat0: Interface activated: mesh0
- Tue Sep 4 23:23:58 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 23:28:10 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 23:28:12 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Tue Sep 4 23:28:12 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Tue Sep 4 23:28:24 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Tue Sep 4 23:28:28 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Tue Sep 4 23:28:42 2018 local0.info autoupdater-wifi-fallback: connectivity check failed
- Tue Sep 4 23:29:01 2018 daemon.info respondd[32253]: unable to read providers from '/usr/lib/respondd', ignoring
- Tue Sep 4 23:30:56 2018 user.notice root: hoodselector[32275]: The hoodselector is still running.
- Tue Sep 4 23:35:38 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Tue Sep 4 23:46:19 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Wed Sep 5 00:01:09 2018 daemon.notice netifd: client (1481): Command failed: Request timed out
- Wed Sep 5 00:01:09 2018 daemon.notice netifd: client (1481): Command failed: Request timed out
- Wed Sep 5 00:23:19 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 00:23:19 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 00:23:24 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 00:23:27 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 00:23:27 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 01:15:13 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 01:15:14 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 01:15:15 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 01:15:19 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 01:15:19 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 02:07:42 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 02:07:43 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 02:07:43 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 02:07:43 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 02:07:43 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 02:59:16 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 02:59:16 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 02:59:17 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 02:59:17 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 02:59:18 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 03:51:10 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 03:51:10 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 03:51:10 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 03:51:10 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 03:51:10 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 04:42:32 2018 daemon.info fastd[1886]: refreshing session with <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 04:42:32 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 04:42:32 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 04:42:33 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 04:42:33 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 05:15:06 2018 kern.info kernel: [241521.253787] IPv6: ADDRCONF(NETDEV_UP): tmp.mesh0: link is not ready
- Wed Sep 5 05:28:07 2018 user.notice firewall: Reloading firewall due to ifupdate of wan6 (br-wan)
- Wed Sep 5 05:29:15 2018 daemon.notice fastd[1886]: connection with <mesh_vpn_backbone_peer__10001> disestablished.
- Wed Sep 5 05:29:15 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 05:29:15 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 05:29:16 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 05:29:16 2018 daemon.info fastd[1886]: received handshake response from <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001] using fastd v18
- Wed Sep 5 05:29:16 2018 daemon.info fastd[1886]: [2a01:4f8:110:1473::54]:10001 authorized as <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 05:29:16 2018 daemon.notice fastd[1886]: connection with <mesh_vpn_backbone_peer__10001> established.
- Wed Sep 5 05:29:16 2018 daemon.info fastd[1886]: new session with <mesh_vpn_backbone_peer__10001> established using method `salsa2012+umac'.
- Wed Sep 5 05:38:13 2018 daemon.notice netifd: client (1481): cat: write error: Broken pipe
- Wed Sep 5 06:06:32 2018 daemon.notice fastd[1886]: connection with <mesh_vpn_backbone_peer__10001> disestablished.
- Wed Sep 5 06:06:32 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:06:32 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:06:34 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:06:46 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:06:46 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:06:54 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[78.46.49.54:10001]...
- Wed Sep 5 06:06:54 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:06:54 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:07:04 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:07:14 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:07:25 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[78.46.49.54:10000]...
- Wed Sep 5 06:07:25 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:07:25 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:07:36 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[78.46.49.54:10001]...
- Wed Sep 5 06:07:36 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:07:36 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:07:42 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:07:59 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:08:03 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[78.46.49.54:10000]...
- Wed Sep 5 06:08:03 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:08:04 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:08:20 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[78.46.49.54:10001]...
- Wed Sep 5 06:08:20 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:08:20 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:08:25 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:08:39 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:08:44 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[78.46.49.54:10000]...
- Wed Sep 5 06:08:44 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:08:44 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:09:00 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[78.46.49.54:10001]...
- Wed Sep 5 06:09:00 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:09:00 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:09:07 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:09:17 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:09:28 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[78.46.49.54:10000]...
- Wed Sep 5 06:09:28 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:09:28 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:09:39 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[78.46.49.54:10001]...
- Wed Sep 5 06:09:39 2018 daemon.info fastd[1886]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:09:39 2018 daemon.info fastd[1886]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:09:47 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:10:03 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10001>[[2a01:4f8:110:1473::54]:10001]...
- Wed Sep 5 06:10:06 2018 daemon.info fastd[1886]: sending handshake to <mesh_vpn_backbone_peer__10000>[78.46.49.54:10000]...
- Wed Sep 5 06:10:06 2018 daemon.info fastd[1886]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:10:06 2018 daemon.info fastd[1886]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:10:08 2018 daemon.notice fastd[1886]: terminating fastd
- Wed Sep 5 06:10:08 2018 daemon.info fastd[1886]: deleting peer <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 06:10:08 2018 daemon.info fastd[1886]: deleting peer <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 06:10:08 2018 daemon.notice netifd: Network device 'mesh-vpn' link is down
- Wed Sep 5 06:10:08 2018 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity loss
- Wed Sep 5 06:10:08 2018 kern.info kernel: [244824.573541] batman_adv: bat0: Interface deactivated: mesh-vpn
- Wed Sep 5 06:10:09 2018 kern.info kernel: [244824.861253] batman_adv: bat0: Removing interface: mesh-vpn
- Wed Sep 5 06:10:09 2018 daemon.notice netifd: Interface 'mesh_vpn' is disabled
- Wed Sep 5 06:10:11 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Wed Sep 5 06:10:11 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Wed Sep 5 06:10:15 2018 kern.info kernel: [244830.399951] batman_adv: bat0: Interface deactivated: mesh0
- Wed Sep 5 06:10:15 2018 kern.info kernel: [244830.405778] batman_adv: bat0: Removing interface: mesh0
- Wed Sep 5 06:10:15 2018 daemon.notice netifd: Interface 'mesh_radio0' is now down
- Wed Sep 5 06:10:15 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
- Wed Sep 5 06:10:15 2018 daemon.notice hostapd: client0: AP-DISABLED
- Wed Sep 5 06:10:15 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
- Wed Sep 5 06:10:15 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
- Wed Sep 5 06:10:16 2018 kern.info kernel: [244831.662383] device client0 left promiscuous mode
- Wed Sep 5 06:10:16 2018 kern.info kernel: [244831.667524] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:10:16 2018 daemon.notice netifd: Network device 'client0' link is down
- Wed Sep 5 06:10:17 2018 daemon.info respondd[15758]: unable to read providers from '/usr/lib/respondd', ignoring
- Wed Sep 5 06:10:21 2018 daemon.notice fastd[15890]: fastd v18 starting
- Wed Sep 5 06:10:21 2018 daemon.notice fastd[15890]: changed to UID 0, GID 800
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.310566] br-client: port 3(bat0) entered disabled state
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.316570] br-client: port 2(local-port) entered disabled state
- Wed Sep 5 06:10:21 2018 daemon.info fastd[15890]: adding peer <mesh_vpn_backbone_peer__11112>
- Wed Sep 5 06:10:21 2018 daemon.err odhcp6c[1481]: Failed to send DHCPV6 message to ff02::1:2 (Permission denied)
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.652402] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.658561] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.664543] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:10:21 2018 kern.info kernel: [244837.671094] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:10:22 2018 daemon.info fastd[15890]: adding peer <mesh_vpn_backbone_peer__11111>
- Wed Sep 5 06:10:22 2018 daemon.info fastd[15890]: resolving host `default06.ffnw.de' for peer <mesh_vpn_backbone_peer__11111>...
- Wed Sep 5 06:10:22 2018 daemon.info fastd[15890]: resolving host `default06.ffnw.de' for peer <mesh_vpn_backbone_peer__11112>...
- Wed Sep 5 06:10:22 2018 daemon.err odhcp6c[1481]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
- Wed Sep 5 06:10:22 2018 daemon.notice netifd: Interface 'mesh_vpn' is enabled
- Wed Sep 5 06:10:22 2018 daemon.notice netifd: Network device 'mesh-vpn' link is up
- Wed Sep 5 06:10:22 2018 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity
- Wed Sep 5 06:10:22 2018 daemon.notice netifd: Interface 'mesh_vpn' is setting up now
- Wed Sep 5 06:10:22 2018 daemon.info fastd[15890]: resolved host `default06.ffnw.de' successfully
- Wed Sep 5 06:10:22 2018 daemon.info fastd[15890]: resolved host `default06.ffnw.de' successfully
- Wed Sep 5 06:10:23 2018 daemon.err odhcp6c[1481]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
- Wed Sep 5 06:10:24 2018 kern.info kernel: [244839.655998] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:10:24 2018 kern.info kernel: [244839.666011] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:10:24 2018 daemon.info fastd[15890]: sending handshake to <mesh_vpn_backbone_peer__11112>[[2a06:e881:2000:12::13]:11112]...
- Wed Sep 5 06:10:24 2018 daemon.info fastd[15890]: received handshake response from <mesh_vpn_backbone_peer__11112>[[2a06:e881:2000:12::13]:11112] using fastd v18
- Wed Sep 5 06:10:25 2018 daemon.err respondd[15758]: join_mcast: no valid interface given
- Wed Sep 5 06:10:26 2018 daemon.info fastd[15890]: [2a06:e881:2000:12::13]:11112 authorized as <mesh_vpn_backbone_peer__11112>
- Wed Sep 5 06:10:26 2018 daemon.notice fastd[15890]: connection with <mesh_vpn_backbone_peer__11112> established.
- Wed Sep 5 06:10:26 2018 daemon.info fastd[15890]: new session with <mesh_vpn_backbone_peer__11112> established using method `salsa2012+umac'.
- Wed Sep 5 06:10:27 2018 daemon.notice netifd: Interface 'mesh_vpn' is now up
- Wed Sep 5 06:11:05 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Wed Sep 5 06:11:20 2018 kern.info kernel: [244894.955575] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Wed Sep 5 06:11:24 2018 kern.info kernel: [244899.260337] batman_adv: bat0: Adding interface: mesh-vpn
- Wed Sep 5 06:11:24 2018 kern.info kernel: [244899.266127] 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.
- Wed Sep 5 06:11:24 2018 kern.info kernel: [244899.291326] batman_adv: bat0: Interface activated: mesh-vpn
- Wed Sep 5 06:11:24 2018 kern.info kernel: [244900.473463] device client0 entered promiscuous mode
- Wed Sep 5 06:11:32 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Wed Sep 5 06:11:54 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Wed Sep 5 06:11:57 2018 kern.info kernel: [244926.484420] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Wed Sep 5 06:11:57 2018 kern.info kernel: [244926.491595] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:11:57 2018 kern.info kernel: [244926.497955] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:11:57 2018 kern.info kernel: [244928.496543] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:12:01 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Wed Sep 5 06:12:05 2018 daemon.notice hostapd: client0: AP-ENABLED
- Wed Sep 5 06:12:16 2018 daemon.notice hostapd: nl80211: nl80211_recv_beacons->nl_recvmsgs failed: -5
- Wed Sep 5 06:12:58 2018 kern.info kernel: [244983.103600] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
- Wed Sep 5 06:13:54 2018 kern.info kernel: [245047.488674] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
- Wed Sep 5 06:15:28 2018 kern.info kernel: [245139.562140] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:15:28 2018 kern.info kernel: [245139.568421] br-client: port 3(bat0) entered disabled state
- Wed Sep 5 06:15:28 2018 kern.info kernel: [245139.575101] br-client: port 2(local-port) entered disabled state
- Wed Sep 5 06:15:42 2018 daemon.notice netifd: bridge 'br-client' link is down
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.476109] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.482546] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.488832] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.494810] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.500827] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245156.507338] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:15:42 2018 daemon.notice netifd: Interface 'client' has link connectivity loss
- Wed Sep 5 06:15:42 2018 daemon.err odhcp6c[1481]: Failed to send DHCPV6 message to ff02::1:2 (Permission denied)
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245158.515792] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245158.522176] br-client: port 3(bat0) entered forwarding state
- Wed Sep 5 06:15:42 2018 kern.info kernel: [245158.528177] br-client: port 2(local-port) entered forwarding state
- Wed Sep 5 06:15:44 2018 daemon.notice netifd: bridge 'br-client' link is up
- Wed Sep 5 06:15:44 2018 daemon.notice netifd: Interface 'client' has link connectivity
- Wed Sep 5 06:15:44 2018 daemon.notice netifd: Interface 'client' is setting up now
- Wed Sep 5 06:15:55 2018 daemon.notice netifd: Interface 'client' is now down
- Wed Sep 5 06:15:56 2018 kern.info kernel: [245171.696680] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:15:56 2018 kern.info kernel: [245171.702945] br-client: port 3(bat0) entered disabled state
- Wed Sep 5 06:15:56 2018 kern.info kernel: [245171.708849] br-client: port 2(local-port) entered disabled state
- Wed Sep 5 06:15:56 2018 kern.info kernel: [245171.721135] device bat0 left promiscuous mode
- Wed Sep 5 06:15:56 2018 kern.info kernel: [245171.726143] br-client: port 3(bat0) entered disabled state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245180.914383] device eth0 left promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245180.919275] br-client: port 1(eth0) entered disabled state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245180.930683] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245181.866588] device local-port left promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245181.872001] br-client: port 2(local-port) entered disabled state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245181.884565] IPv6: ADDRCONF(NETDEV_UP): local-port: link is not ready
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245181.893073] device client0 left promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245181.898174] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245185.767965] device bat0 entered promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245186.398978] device eth0 entered promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245186.560504] batman_adv: bat0: Interface deactivated: mesh-vpn
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245186.617689] batman_adv: bat0: Removing interface: mesh-vpn
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245187.382771] device local-port entered promiscuous mode
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245187.401942] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245187.408626] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245187.415142] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:12 2018 kern.info kernel: [245187.421162] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:12 2018 daemon.notice fastd[15890]: terminating fastd
- Wed Sep 5 06:16:12 2018 daemon.info fastd[15890]: deleting peer <mesh_vpn_backbone_peer__11111>
- Wed Sep 5 06:16:12 2018 daemon.notice netifd: Interface 'client' is disabled
- Wed Sep 5 06:16:12 2018 daemon.notice fastd[15890]: connection with <mesh_vpn_backbone_peer__11112> disestablished.
- Wed Sep 5 06:16:12 2018 daemon.info fastd[15890]: deleting peer <mesh_vpn_backbone_peer__11112>
- Wed Sep 5 06:16:12 2018 user.notice root: hoodselector[16121]: The hoodselector is still running.
- Wed Sep 5 06:16:13 2018 kern.info kernel: [245189.438078] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:13 2018 kern.info kernel: [245189.444660] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:14 2018 daemon.notice netifd: Interface 'client' is enabled
- Wed Sep 5 06:16:15 2018 daemon.notice netifd: Interface 'client' is setting up now
- Wed Sep 5 06:16:16 2018 user.notice firewall: Reloading firewall due to ifupdate of client (br-client)
- Wed Sep 5 06:16:29 2018 kern.info kernel: [245201.870854] br-client: port 3(local-port) entered disabled state
- Wed Sep 5 06:16:29 2018 kern.info kernel: [245201.877358] br-client: port 1(bat0) entered disabled state
- Wed Sep 5 06:16:29 2018 daemon.err respondd[15758]: Could not join multicast group on mesh0: sendto failed: Permission denied
- Wed Sep 5 06:16:30 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:16:31 2018 daemon.notice netifd: Interface 'client' is now up
- Wed Sep 5 06:16:31 2018 daemon.notice netifd: bridge 'br-client' link is down
- Wed Sep 5 06:16:31 2018 daemon.notice netifd: Interface 'client' has link connectivity loss
- Wed Sep 5 06:16:31 2018 daemon.notice netifd: Network device 'mesh-vpn' link is down
- Wed Sep 5 06:16:31 2018 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity loss
- Wed Sep 5 06:16:41 2018 daemon.notice netifd: Interface 'mesh_vpn' is now down
- Wed Sep 5 06:16:42 2018 kern.info kernel: [245218.269507] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:42 2018 kern.info kernel: [245218.276105] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:42 2018 kern.info kernel: [245218.282730] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:42 2018 kern.info kernel: [245218.288732] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:44 2018 kern.info kernel: [245220.268245] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:16:44 2018 kern.info kernel: [245220.494393] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:16:45 2018 daemon.notice netifd: Interface 'mesh_vpn' is disabled
- Wed Sep 5 06:16:46 2018 daemon.notice netifd: bridge 'br-client' link is up
- Wed Sep 5 06:16:46 2018 daemon.notice netifd: Interface 'client' has link connectivity
- Wed Sep 5 06:16:46 2018 daemon.notice netifd: Interface 'client' is setting up now
- Wed Sep 5 06:16:52 2018 user.notice root: hoodselector[16194]: The hoodselector is still running.
- Wed Sep 5 06:17:06 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:17:25 2018 daemon.notice netifd: Network device 'mesh0' link is up
- Wed Sep 5 06:17:25 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
- Wed Sep 5 06:17:25 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
- Wed Sep 5 06:17:25 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
- Wed Sep 5 06:17:25 2018 daemon.notice netifd: Network device 'client0' link is up
- Wed Sep 5 06:17:25 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:17:26 2018 kern.info kernel: [245261.693861] device client0 entered promiscuous mode
- Wed Sep 5 06:17:26 2018 kern.info kernel: [245261.699205] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:17:26 2018 kern.info kernel: [245261.705457] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:17:28 2018 kern.info kernel: [245263.782557] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:17:43 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
- Wed Sep 5 06:17:43 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
- Wed Sep 5 06:17:51 2018 daemon.notice netifd: Interface 'mesh_radio0' is now down
- Wed Sep 5 06:17:51 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:17:58 2018 kern.info kernel: [245291.814377] device client0 left promiscuous mode
- Wed Sep 5 06:17:58 2018 kern.info kernel: [245291.819465] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:18:06 2018 daemon.err hostapd: eloop: could not process SIGINT or SIGTERM in two seconds. Looks like there
- is a bug that ends up in a busy loop that prevents clean shutdown.
- Killing program forcefully.
- Wed Sep 5 06:18:08 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:18:21 2018 user.notice sysctl: net.ipv6.conf.br-client.forwarding = 0
- Wed Sep 5 06:18:28 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:18:38 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:18:43 2018 daemon.notice fastd[16455]: fastd v18 starting
- Wed Sep 5 06:18:43 2018 daemon.notice fastd[16455]: changed to UID 0, GID 800
- Wed Sep 5 06:18:43 2018 daemon.info fastd[16455]: adding peer <mesh_vpn_backbone_peer__10001>
- Wed Sep 5 06:18:43 2018 daemon.info fastd[16455]: adding peer <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 06:18:43 2018 daemon.info fastd[16455]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:18:43 2018 daemon.info fastd[16455]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:18:44 2018 daemon.notice netifd: Interface 'mesh_vpn' is enabled
- Wed Sep 5 06:18:45 2018 daemon.notice netifd: Network device 'mesh-vpn' link is up
- Wed Sep 5 06:18:45 2018 daemon.notice netifd: Interface 'mesh_vpn' has link connectivity
- Wed Sep 5 06:18:45 2018 daemon.notice netifd: Interface 'mesh_vpn' is setting up now
- Wed Sep 5 06:18:48 2018 daemon.notice netifd: Interface 'client' is now up
- Wed Sep 5 06:18:48 2018 user.notice root: hoodselector[16330]: The hoodselector is still running.
- Wed Sep 5 06:18:53 2018 daemon.info fastd[16455]: resolving host `lk-st02.sn.ffnw.de' failed: Try again
- Wed Sep 5 06:18:53 2018 daemon.info fastd[16455]: resolving host `lk-st01.sn.ffnw.de' failed: Try again
- Wed Sep 5 06:18:53 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:18:53 2018 kern.info kernel: [245349.295478] br-client: port 3(local-port) entered disabled state
- Wed Sep 5 06:18:53 2018 kern.info kernel: [245349.302052] br-client: port 1(bat0) entered disabled state
- Wed Sep 5 06:18:54 2018 daemon.notice netifd: bridge 'br-client' link is down
- Wed Sep 5 06:18:54 2018 daemon.notice netifd: Interface 'client' has link connectivity loss
- Wed Sep 5 06:18:54 2018 kern.info kernel: [245350.212227] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:18:54 2018 kern.info kernel: [245350.218847] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:18:54 2018 kern.info kernel: [245350.225475] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:18:54 2018 kern.info kernel: [245350.231495] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:18:55 2018 daemon.err odhcp6c[16316]: Failed to send DHCPV6 message to ff02::1:2 (Permission denied)
- Wed Sep 5 06:18:56 2018 kern.info kernel: [245352.259187] br-client: port 3(local-port) entered forwarding state
- Wed Sep 5 06:18:56 2018 kern.info kernel: [245352.265772] br-client: port 1(bat0) entered forwarding state
- Wed Sep 5 06:18:57 2018 daemon.err odhcp6c[16316]: Failed to send DHCPV6 message to ff02::1:2 (Address not available)
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.notice netifd: bridge 'br-client' link is up
- Wed Sep 5 06:19:07 2018 daemon.notice netifd: Interface 'client' has link connectivity
- Wed Sep 5 06:19:07 2018 daemon.notice netifd: Interface 'client' is setting up now
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:07 2018 daemon.err respondd[15758]: sendto failed: Permission denied
- Wed Sep 5 06:19:10 2018 daemon.info respondd[16553]: unable to read providers from '/usr/lib/respondd', ignoring
- Wed Sep 5 06:19:11 2018 daemon.info fastd[16455]: resolving host `lk-st01.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10000>...
- Wed Sep 5 06:19:14 2018 daemon.notice netifd: Interface 'mesh_vpn' is now up
- Wed Sep 5 06:19:14 2018 daemon.notice netifd: Interface 'client' is now up
- Wed Sep 5 06:19:14 2018 daemon.info fastd[16455]: resolved host `lk-st01.sn.ffnw.de' successfully
- Wed Sep 5 06:19:16 2018 daemon.info fastd[16455]: resolving host `lk-st02.sn.ffnw.de' for peer <mesh_vpn_backbone_peer__10001>...
- Wed Sep 5 06:19:17 2018 user.notice firewall: Reloading firewall due to ifup of client (br-client)
- Wed Sep 5 06:19:18 2018 daemon.err dnsmasq[1705]: failed to send packet: Operation not permitted
- Wed Sep 5 06:19:18 2018 daemon.err dnsmasq[1705]: failed to send packet: Operation not permitted
- Wed Sep 5 06:19:19 2018 daemon.info fastd[16455]: resolved host `lk-st02.sn.ffnw.de' successfully
- Wed Sep 5 06:19:20 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Wed Sep 5 06:19:20 2018 kern.info kernel: [245376.636778] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Wed Sep 5 06:19:21 2018 kern.info kernel: [245376.837977] batman_adv: bat0: Adding interface: mesh-vpn
- Wed Sep 5 06:19:21 2018 kern.info kernel: [245376.843670] 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.
- Wed Sep 5 06:19:21 2018 kern.info kernel: [245376.868806] batman_adv: bat0: Interface activated: mesh-vpn
- Wed Sep 5 06:19:21 2018 kern.info kernel: [245376.893755] device client0 entered promiscuous mode
- Wed Sep 5 06:19:21 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
- Wed Sep 5 06:19:29 2018 daemon.err hostapd: Using interface client0 with hwaddr f6:05:35:b4:23:f8 and ssid "nordwest.freifunk.net"
- Wed Sep 5 06:19:29 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
- Wed Sep 5 06:19:29 2018 daemon.notice hostapd: client0: AP-ENABLED
- Wed Sep 5 06:19:30 2018 kern.info kernel: [245385.839331] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
- Wed Sep 5 06:19:30 2018 kern.info kernel: [245385.846459] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:19:30 2018 kern.info kernel: [245385.852818] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:19:32 2018 kern.info kernel: [245387.849203] br-client: port 4(client0) entered forwarding state
- Wed Sep 5 06:19:38 2018 daemon.info fastd[16455]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 06:19:38 2018 daemon.info fastd[16455]: received handshake response from <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000] using fastd v18
- Wed Sep 5 06:19:38 2018 user.notice firewall: Reloading firewall due to ifup of client (br-client)
- Wed Sep 5 06:19:45 2018 daemon.info fastd[16455]: [2a01:4f8:110:1473::54]:10000 authorized as <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 06:19:45 2018 daemon.notice fastd[16455]: connection with <mesh_vpn_backbone_peer__10000> established.
- Wed Sep 5 06:19:45 2018 daemon.info fastd[16455]: new session with <mesh_vpn_backbone_peer__10000> established using method `salsa2012+umac'.
- Wed Sep 5 06:21:53 2018 kern.info kernel: [245527.098190] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:21:55 2018 daemon.notice hostapd: client0: INTERFACE-DISABLED
- Wed Sep 5 06:22:08 2018 kern.info kernel: [245543.748616] device client0 left promiscuous mode
- Wed Sep 5 06:22:08 2018 kern.info kernel: [245543.753592] br-client: port 4(client0) entered disabled state
- Wed Sep 5 06:22:41 2018 daemon.err hostapd: Failed to set beacon parameters
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:54 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:55 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:22:55 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:23:03 2018 daemon.err respondd[16553]: sendto failed: Operation not permitted
- Wed Sep 5 06:23:03 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:23:03 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:23:03 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:23:03 2018 daemon.warn fastd[16455]: sendmsg: Operation not permitted
- Wed Sep 5 06:25:25 2018 kern.info kernel: [245739.147473] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
- Wed Sep 5 06:25:39 2018 daemon.notice netifd: client (16594): Command failed: Request timed out
- Wed Sep 5 06:25:40 2018 daemon.notice hostapd: client0: INTERFACE-ENABLED
- Wed Sep 5 06:25:40 2018 daemon.err hostapd: Failed to set beacon parameters
- Wed Sep 5 06:25:59 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
- Wed Sep 5 06:26:09 2018 daemon.notice hostapd: client0: INTERFACE-DISABLED
- Wed Sep 5 06:26:09 2018 daemon.err hostapd: nl80211: Could not configure driver mode
- Wed Sep 5 06:26:09 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
- Wed Sep 5 06:26:09 2018 daemon.err hostapd: nl80211 driver initialization failed.
- Wed Sep 5 06:26:14 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->DISABLED
- Wed Sep 5 06:26:20 2018 daemon.notice hostapd: client0: AP-DISABLED
- Wed Sep 5 06:26:20 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
- Wed Sep 5 06:26:20 2018 daemon.err hostapd: hostapd_free_hapd_data: Interface client0 wasn't started
- Wed Sep 5 06:27:47 2018 daemon.notice netifd: radio0 (16740): Device setup failed: HOSTAPD_START_FAILED
- Wed Sep 5 06:29:08 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
- Wed Sep 5 06:29:08 2018 daemon.notice hostapd: client0: AP-DISABLED
- Wed Sep 5 06:29:08 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
- Wed Sep 5 06:29:08 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 06:29:08 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
- Wed Sep 5 06:29:08 2018 daemon.notice hostapd: nl80211: Failed to remove interface client0 from bridge br-client: Invalid argument
- Wed Sep 5 06:35:53 2018 daemon.info respondd[17578]: unable to read providers from '/usr/lib/respondd', ignoring
- Wed Sep 5 06:38:55 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 06:53:53 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 07:03:03 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 07:12:52 2018 daemon.info fastd[16455]: refreshing session with <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 07:12:58 2018 daemon.info fastd[16455]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 07:12:58 2018 daemon.info fastd[16455]: received handshake response from <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000] using fastd v18
- Wed Sep 5 07:13:02 2018 daemon.info fastd[16455]: [2a01:4f8:110:1473::54]:10000 authorized as <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 07:13:02 2018 daemon.info fastd[16455]: new session with <mesh_vpn_backbone_peer__10000> established using method `salsa2012+umac'.
- Wed Sep 5 07:23:15 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 07:46:15 2018 daemon.notice netifd: client (16594): cat: write error: Broken pipe
- Wed Sep 5 08:03:28 2018 daemon.info fastd[16455]: refreshing session with <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 08:03:29 2018 daemon.info fastd[16455]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 08:03:29 2018 daemon.info fastd[16455]: received handshake response from <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000] using fastd v18
- Wed Sep 5 08:03:33 2018 daemon.info fastd[16455]: [2a01:4f8:110:1473::54]:10000 authorized as <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 08:03:33 2018 daemon.info fastd[16455]: new session with <mesh_vpn_backbone_peer__10000> established using method `salsa2012+umac'.
- Wed Sep 5 08:14:25 2018 daemon.notice netifd: wan6 (1485): Command failed: Request timed out
- Wed Sep 5 08:20:55 2018 daemon.notice netifd: client (16594): Command failed: Request timed out
- Wed Sep 5 08:29:09 2018 daemon.notice netifd: wan6 (1485): Command failed: Request timed out
- Wed Sep 5 08:29:09 2018 daemon.notice netifd: client (16594): Command failed: Request timed out
- Wed Sep 5 08:30:25 2018 user.notice root: hoodselector[21675]: The hoodselector is still running.
- Wed Sep 5 08:37:05 2018 daemon.notice netifd: client (16594): Command failed: Request timed out
- Wed Sep 5 08:38:48 2018 daemon.notice netifd: client (16594): Command failed: Request timed out
- Wed Sep 5 08:55:32 2018 daemon.info fastd[16455]: refreshing session with <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 08:55:33 2018 daemon.info fastd[16455]: sending handshake to <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000]...
- Wed Sep 5 08:55:34 2018 daemon.info fastd[16455]: received handshake response from <mesh_vpn_backbone_peer__10000>[[2a01:4f8:110:1473::54]:10000] using fastd v18
- Wed Sep 5 08:55:35 2018 daemon.info fastd[16455]: [2a01:4f8:110:1473::54]:10000 authorized as <mesh_vpn_backbone_peer__10000>
- Wed Sep 5 08:55:36 2018 daemon.info fastd[16455]: new session with <mesh_vpn_backbone_peer__10000> established using method `salsa2012+umac'.
- Wed Sep 5 09:34:11 2018 authpriv.info dropbear[23545]: Child connection from 2a02:8109:1a40:1d1b:1259:d7ad:7c11:3914:45708
- Wed Sep 5 09:34:21 2018 authpriv.notice dropbear[23545]: Pubkey auth succeeded for 'root' with key md5 59:9b:b8:68:27:43:4e:54:23:8a:87:e5:68:3e:42:9d from 2a02:8109:1a40:1d1b:1259:d7ad:7c11:3914:45708
- root@FF-WKP-Privat-01:~# reboot;exit
- Connection to 2a06:e881:2000:4200:32b5:c2ff:fed9:e416 closed.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement