Knoten ist online, akzeptiert aber keine Clients

postapo · 27. April 2018 um 14:34

Hallo zusammen,

seit Kurzem ist unser Knoten zwar laut Karte online, allerdings akzeptiert er keine Verbindungen von den Clients. Nach einem Neustart des Knotens läuft es kurze Zeit wieder normal, irgendwann werden die Verbindungen zu den Clients dann gekappt und es geht nichts mehr. Ich habe schon versucht das DHCP durch statische IP-Adressen zu ersetzen, was aber nur bedingt geholfen hat. Habt ihr noch eine Idee wie ich auf die Ursache des Problems kommen kann? SSH auf den Knoten aus dem lokalen Netz geht. Hardware ist ein TL-WR1043ND mit Firmware 1.1.4-20180313 / gluon-v2017.1.5+

Herzlichen Dank

Thomas

rgr · 27. April 2018 um 15:21

Da ssh vom lokalen Netz aus geht würde ich mich auf den Knoten verbinden und mit logread bzw logread -f beobachten, ob es auffällige Fehlermeldungen gibt. Normalerweise sieht man dort An- und Abmeldungen der einzelnen Geräte.

postapo · 27. April 2018 um 16:57

Ich habe eben das WLAN mal per Knopfdruck am Router aus- und wieder eingeschaltet. Danach war eine Anmeldung wieder möglich. Und so wie es aussieht, läuft der Knoten jetzt wieder stabil. Das Log erscheint unauffällig:

root@Post-Apotheke:~# logread -f
Fri Apr 27 17:28:01 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
Fri Apr 27 17:28:01 2018 daemon.notice hostapd: client0: AP-DISABLED
Fri Apr 27 17:28:01 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
Fri Apr 27 17:28:01 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
Fri Apr 27 17:28:01 2018 kern.info kernel: [88350.343493] device client0 left promiscuous mode
Fri Apr 27 17:28:01 2018 kern.info kernel: [88350.348326] br-client: port 4(client0) entered disabled state
Fri Apr 27 17:28:01 2018 daemon.notice netifd: Network device 'client0' link is down
Fri Apr 27 17:28:01 2018 kern.info kernel: [88350.426995] batman_adv: bat0: Interface deactivated: mesh0
Fri Apr 27 17:28:01 2018 daemon.notice netifd: Network device 'mesh0' link is down
Fri Apr 27 17:28:01 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity loss
Fri Apr 27 17:28:02 2018 kern.info kernel: [88350.604003] batman_adv: bat0: Removing interface: mesh0
Fri Apr 27 17:28:02 2018 daemon.notice netifd: Interface 'mesh_radio0' is disabled
Fri Apr 27 17:28:02 2018 daemon.info respondd[6272]: unable to read providers from '/usr/lib/respondd', ignoring
Fri Apr 27 17:28:10 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Fri Apr 27 17:28:10 2018 kern.info kernel: [88358.815477] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
Fri Apr 27 17:28:10 2018 kern.info kernel: [88358.877389] device client0 entered promiscuous mode
Fri Apr 27 17:28:10 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Apr 27 17:28:10 2018 daemon.err hostapd: Using interface client0 with hwaddr c6:7f:b3:95:e4:80 and ssid "freifunk-rhein-neckar.de"
Fri Apr 27 17:28:10 2018 kern.info kernel: [88358.934100] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Fri Apr 27 17:28:10 2018 kern.info kernel: [88358.940885] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:10 2018 kern.info kernel: [88358.947003] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:10 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
Fri Apr 27 17:28:10 2018 daemon.notice hostapd: client0: AP-ENABLED
Fri Apr 27 17:28:10 2018 kern.info kernel: [88359.076265] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Fri Apr 27 17:28:10 2018 daemon.notice netifd: Network device 'mesh0' link is up
Fri Apr 27 17:28:10 2018 kern.info kernel: [88359.118302] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Fri Apr 27 17:28:12 2018 kern.info kernel: [88360.941975] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:20 2018 daemon.notice hostapd: client0: interface state ENABLED->DISABLED
Fri Apr 27 17:28:20 2018 daemon.notice hostapd: client0: AP-DISABLED
Fri Apr 27 17:28:20 2018 daemon.notice hostapd: client0: CTRL-EVENT-TERMINATING
Fri Apr 27 17:28:20 2018 daemon.notice hostapd: nl80211: deinit ifname=client0 disabled_11b_rates=0
Fri Apr 27 17:28:20 2018 kern.info kernel: [88369.253588] device client0 left promiscuous mode
Fri Apr 27 17:28:20 2018 kern.info kernel: [88369.258551] br-client: port 4(client0) entered disabled state
Fri Apr 27 17:28:20 2018 daemon.notice netifd: Network device 'mesh0' link is down
Fri Apr 27 17:28:21 2018 daemon.err hostapd: Configuration file: /var/run/hostapd-phy0.conf
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.075877] IPv6: ADDRCONF(NETDEV_UP): client0: link is not ready
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.158537] device client0 entered promiscuous mode
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.163805] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.169847] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:21 2018 daemon.notice hostapd: client0: interface state UNINITIALIZED->COUNTRY_UPDATE
Fri Apr 27 17:28:21 2018 daemon.err hostapd: Using interface client0 with hwaddr c6:7f:b3:95:e4:80 and ssid "freifunk-rhein-neckar.de"
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.230508] IPv6: ADDRCONF(NETDEV_CHANGE): client0: link becomes ready
Fri Apr 27 17:28:21 2018 daemon.notice hostapd: client0: interface state COUNTRY_UPDATE->ENABLED
Fri Apr 27 17:28:21 2018 daemon.notice hostapd: client0: AP-ENABLED
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.331721] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Fri Apr 27 17:28:21 2018 daemon.notice netifd: Network device 'mesh0' link is up
Fri Apr 27 17:28:21 2018 kern.info kernel: [88370.375717] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready
Fri Apr 27 17:28:21 2018 daemon.notice netifd: Interface 'mesh_radio0' is enabled
Fri Apr 27 17:28:21 2018 daemon.notice netifd: Interface 'mesh_radio0' has link connectivity
Fri Apr 27 17:28:21 2018 daemon.notice netifd: Interface 'mesh_radio0' is setting up now
Fri Apr 27 17:28:21 2018 daemon.notice netifd: Network device 'client0' link is up
Fri Apr 27 17:28:22 2018 daemon.notice netifd: mesh_radio0 (6620): ip: SIOCSIFMTU: No such device
Fri Apr 27 17:28:22 2018 daemon.notice netifd: Interface 'mesh_radio0' is now up
Fri Apr 27 17:28:22 2018 kern.info kernel: [88370.919995] batman_adv: bat0: Adding interface: mesh0
Fri Apr 27 17:28:22 2018 kern.info kernel: [88370.925210] batman_adv: bat0: Interface activated: mesh0
Fri Apr 27 17:28:22 2018 daemon.info respondd[6690]: unable to read providers from '/usr/lib/respondd', ignoring
Fri Apr 27 17:28:23 2018 kern.info kernel: [88372.162016] br-client: port 4(client0) entered forwarding state
Fri Apr 27 17:28:24 2018 daemon.notice hostapd: client0: STA 58:40:4e:69:3d:7b IEEE 802.11: did not acknowledge authentication response
Fri Apr 27 17:28:24 2018 daemon.info hostapd: client0: STA 58:40:4e:69:3d:7b IEEE 802.11: associated (aid 1)
Fri Apr 27 17:28:24 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED 58:40:4e:69:3d:7b
Fri Apr 27 17:30:12 2018 authpriv.info dropbear[6115]: Exit (root): Exited normally
Fri Apr 27 17:30:20 2018 authpriv.info dropbear[6816]: Child connection from 10.xx.xx.xx:52289
Fri Apr 27 17:30:29 2018 authpriv.notice dropbear[6816]: Password auth succeeded for 'root' from 10.xx.xx.xx:52289
Fri Apr 27 17:32:07 2018 daemon.info hostapd: client0: STA 24:18:1d:c5:6d:56 IEEE 802.11: authenticated
Fri Apr 27 17:32:07 2018 daemon.info hostapd: client0: STA 24:18:1d:c5:6d:56 IEEE 802.11: associated (aid 2)
Fri Apr 27 17:32:07 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED 24:18:1d:c5:6d:56
Fri Apr 27 17:34:02 2018 authpriv.info dropbear[6919]: Child connection from 10.xx.xx.xx:52347
Fri Apr 27 17:34:11 2018 authpriv.notice dropbear[6919]: Password auth succeeded for 'root' from 10.xx.xx.xx:52347
Fri Apr 27 17:35:57 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 17:35:57 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 17:35:57 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 17:37:46 2018 daemon.info hostapd: client0: STA 8c:f5:a3:04:5d:b7 IEEE 802.11: authenticated
Fri Apr 27 17:37:46 2018 daemon.info hostapd: client0: STA 8c:f5:a3:04:5d:b7 IEEE 802.11: associated (aid 4)
Fri Apr 27 17:37:46 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED 8c:f5:a3:04:5d:b7
Fri Apr 27 17:38:54 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 17:38:54 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:38:54 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:38:54 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:38:54 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:38:55 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 17:52:00 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 17:52:00 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 17:52:00 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 17:52:03 2018 daemon.info hostapd: client0: STA bc:44:34:2b:e2:bb IEEE 802.11: authenticated
Fri Apr 27 17:52:03 2018 daemon.info hostapd: client0: STA bc:44:34:2b:e2:bb IEEE 802.11: associated (aid 5)
Fri Apr 27 17:52:03 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED bc:44:34:2b:e2:bb
Fri Apr 27 17:54:27 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 17:54:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:54:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:54:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:54:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 17:54:28 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 17:56:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 17:56:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 17:56:03 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 17:58:40 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED bc:44:34:2b:e2:bb
Fri Apr 27 17:58:40 2018 daemon.info hostapd: client0: STA bc:44:34:2b:e2:bb IEEE 802.11: disassociated due to inactivity
Fri Apr 27 17:58:41 2018 daemon.info hostapd: client0: STA bc:44:34:2b:e2:bb IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:09:22 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:09:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated due to inactivity
Fri Apr 27 18:09:23 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:10:08 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:10:08 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 18:10:08 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:17:02 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:17:03 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:19:21 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:19:21 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 18:19:21 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:21:36 2018 daemon.info hostapd: client0: STA cc:c3:ea:13:9e:8e IEEE 802.11: authenticated
Fri Apr 27 18:21:36 2018 daemon.info hostapd: client0: STA cc:c3:ea:13:9e:8e IEEE 802.11: associated (aid 5)
Fri Apr 27 18:21:36 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED cc:c3:ea:13:9e:8e
Fri Apr 27 18:26:22 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:22 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:26:23 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:35:42 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:35:43 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 18:35:43 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:35:49 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:35:49 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:35:49 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:35:49 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:35:49 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:35:50 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:36:07 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:36:07 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 18:36:07 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:36:13 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:36:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:36:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:36:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:36:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:36:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:36:14 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:36:24 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:36:24 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 3)
Fri Apr 27 18:36:24 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:37:24 2018 daemon.info hostapd: client0: STA 24:18:1d:c5:6d:56 IEEE 802.11: disconnected due to excessive missing ACKs
Fri Apr 27 18:37:24 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 24:18:1d:c5:6d:56
Fri Apr 27 18:37:54 2018 daemon.info hostapd: client0: STA 24:18:1d:c5:6d:56 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:38:13 2018 daemon.info hostapd: client0: STA 58:40:4e:69:3d:7b IEEE 802.11: disconnected due to excessive missing ACKs
Fri Apr 27 18:38:13 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 58:40:4e:69:3d:7b
Fri Apr 27 18:38:43 2018 daemon.info hostapd: client0: STA 58:40:4e:69:3d:7b IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:39:55 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED 8c:f5:a3:04:5d:b7
Fri Apr 27 18:39:55 2018 daemon.info hostapd: client0: STA 8c:f5:a3:04:5d:b7 IEEE 802.11: disassociated due to inactivity
Fri Apr 27 18:39:56 2018 daemon.info hostapd: client0: STA 8c:f5:a3:04:5d:b7 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:40:23 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:40:23 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:23 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:24 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:40:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:40:27 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 1)
Fri Apr 27 18:40:27 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:40:35 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:35 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:40:36 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Fri Apr 27 18:42:58 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: authenticated
Fri Apr 27 18:42:58 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: associated (aid 1)
Fri Apr 27 18:42:58 2018 daemon.notice hostapd: client0: AP-STA-CONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:44:13 2018 daemon.notice hostapd: client0: AP-STA-DISCONNECTED e4:e4:ab:80:3f:d6
Fri Apr 27 18:44:13 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: disassociated
Fri Apr 27 18:44:14 2018 daemon.info hostapd: client0: STA e4:e4:ab:80:3f:d6 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)

rgr · 27. April 2018 um 18:47

Spannend wird es wenn er keinen mehr drauf lässt, ob es dann Fehlermeldungen gibt und die Clients überhaupt noch im Log erwähnt werden.

postapo · 29. April 2018 um 19:30

Ich habe des Rätsels Lösung gefunden: ich Dummerchen habe -weil ein weiteres Netzwerkgerät an einem Arbeitsplatz anschließen wollten und nicht genügend freie Dosen lagen- einen unmodifizierten TL-WR842N an die vorhandene Netzwerkdose gehängt. Da war dann natürlich DHCP aktiv und hat die Client-IP vom FF-Router falsch eingestellt…

rgr · 30. April 2018 um 12:15

Ok, dann sei für die die mal beim Suchen auf diesen Artikel stoßen die Liste mit den Punkten erwähnt, die man durchgehen kann, wenn es mal nicht tut: https://wiki.freifunk.net/Mein_Freifunk_funktioniert_nicht_mehr

Und ganz allgemein sei nochmal die FAQ erwähnt: https://forum.ffrn.de/c/FAQ - dort finde ich das Problem aus diesem Thread so nicht direkt beschrieben - ist aber dennoch allgemein nützlich :-)