Ok so I have a script on my router that sends info about associated stations to a home automation presence setup, which has been working great. However since I’ve updated to the most recent Davidc502 build it keeps showing my wife’s phone as connected ( and therefore an associated station ) when it not. My phone appears to disconnect and reconnect fine.
Any ideas what might be causing it to remain associated?
Is the device getting a static IP?
Is there a lease time configured?
is autorefresh on? how are you viewing the client association?
I had the same problem (see my forum post). Switching to stable removed this problem, but there seems to be a bug somewhere.
1 Like
you think theres a bug in the hostapd?
Yes I've given both devices static IP's and it has a lease time remaining.
I'm using the Luci interface to see associated stations and auto refresh is on.
I had the same problem (see my forum post). Switching to stable removed this problem, but there seems to be a bug somewhere.
Looks like I will have to reboot to the stable build then till this is bug is fixed.
1 Like
Static IP's don't really need a lease.
I have set all my static connections to "infinite".
1 Like
Whoever can reproduce this bug: Which router are you using and which version of lede are you running?
My Router is Linksys wrt1900ACS the build I was trying to use was davidc502 snapshot r5201 build. I've since returned to my last most stable build snapshot r4707 and have no problems with everything working as it should .
@Linuxmarvel, Does it simply never de-authenticate, or does it take longer than before? Because some devices actually send a de-authenticate and are therefor directly disconnected while others do not and take longer to disconnect.
Could you maybe add a "logread" from your AP where you firstly connect your phone --> disconnect your phone --> connect your wives phone --> disconnect your wives phone. This could give some insight in how those 2 devices compare.
@static-ip, why does this even matter? we're talking about associated wireless stations (I suppose?) on layer 2 and not layer 3 ip.
@jwoods, remember that setting the lease time to "infinite" somewhat defeats the purpose of having DHCP, when you want to change for example your gateway/dns or anything else your client will never know this unless they are being unpowered.
As mentioned above, I was referring to setting lease times for my static IP's to "infinite".
I understand, but static leases are a function of DHCP. So that's why I mentioned that.
Correct, and my understanding is that a static IP does not need a lease.
Do you want me to take a logread on the current snapshot I'm on (which is my stable one ) or a logread from the snapshot where I have the problem ? Or should this not matter?
On the snapshot I'm on the clients disconnect as expected as soon as they out of range.
However on the latest build it show the client still as an associated station but with zero signal.
But how are you going to solve this then?
I always say better to much information than 2 little.
The minimum logread is the one where you have a problem. But it would be nice if you provide a stable logread as well. So we can compare if there actually is a difference between the 2.
This is current snapshot.
Tue Nov 7 19:44:16 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED ac:5f:3e:cf:39:e3
Tue Nov 7 19:44:16 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: disassociated
Tue Nov 7 19:44:17 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Nov 7 19:44:29 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: authenticated
Tue Nov 7 19:44:29 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: associated (aid 1)
Tue Nov 7 19:44:29 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED ac:5f:3e:cf:39:e3
Tue Nov 7 19:44:29 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 WPA: pairwise key handshake completed (RSN)
Tue Nov 7 19:44:29 2017 daemon.info dnsmasq-dhcp[3538]: DHCPDISCOVER(br-lan) ac:5f:3e:cf:39:e3
Tue Nov 7 19:44:29 2017 daemon.info dnsmasq-dhcp[3538]: DHCPOFFER(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3
Tue Nov 7 19:44:29 2017 daemon.info dnsmasq-dhcp[3538]: DHCPREQUEST(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3
Tue Nov 7 19:44:29 2017 daemon.info dnsmasq-dhcp[3538]: DHCPACK(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3 SamsungGalaxys7
Tue Nov 7 19:44:40 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 94:65:2d:84:ae:14
Tue Nov 7 19:44:46 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: authenticated
Tue Nov 7 19:44:46 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: associated (aid 2)
Tue Nov 7 19:44:46 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 94:65:2d:84:ae:14
Tue Nov 7 19:44:46 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 WPA: pairwise key handshake completed (RSN)
Tue Nov 7 19:44:46 2017 daemon.info dnsmasq-dhcp[3538]: DHCPDISCOVER(br-lan) 94:65:2d:84:ae:14
Tue Nov 7 19:44:46 2017 daemon.info dnsmasq-dhcp[3538]: DHCPOFFER(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 19:44:46 2017 daemon.info dnsmasq-dhcp[3538]: DHCPREQUEST(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 19:44:46 2017 daemon.info dnsmasq-dhcp[3538]: DHCPACK(br-lan) 192.168.1.130 94:65:2d:84:ae:14 OneplusKatThis is latest snapshot.
Tue Nov 7 19:50:38 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED ac:5f:3e:cf:39:e3
Tue Nov 7 19:50:38 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: disassociated
Tue Nov 7 19:50:39 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Tue Nov 7 19:50:45 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: authenticated
Tue Nov 7 19:50:45 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 IEEE 802.11: associated (aid 2)
Tue Nov 7 19:50:45 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED ac:5f:3e:cf:39:e3
Tue Nov 7 19:50:45 2017 daemon.info hostapd: wlan0: STA ac:5f:3e:cf:39:e3 WPA: pairwise key handshake completed (RSN)
Tue Nov 7 19:50:45 2017 daemon.info dnsmasq-dhcp[2851]: DHCPDISCOVER(br-lan) ac:5f:3e:cf:39:e3
Tue Nov 7 19:50:45 2017 daemon.info dnsmasq-dhcp[2851]: DHCPOFFER(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3
Tue Nov 7 19:50:45 2017 daemon.info dnsmasq-dhcp[2851]: DHCPREQUEST(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3
Tue Nov 7 19:50:45 2017 daemon.info dnsmasq-dhcp[2851]: DHCPACK(br-lan) 192.168.1.179 ac:5f:3e:cf:39:e3 SamsungGalaxys7
Tue Nov 7 19:50:54 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED 94:65:2d:84:ae:14
Tue Nov 7 19:51:00 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: authenticated
Tue Nov 7 19:51:00 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: associated (aid 1)
Tue Nov 7 19:51:00 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 94:65:2d:84:ae:14
Tue Nov 7 19:51:00 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 WPA: pairwise key handshake completed (RSN)
Tue Nov 7 19:51:00 2017 daemon.info dnsmasq-dhcp[2851]: DHCPDISCOVER(br-lan) 94:65:2d:84:ae:14
Tue Nov 7 19:51:00 2017 daemon.info dnsmasq-dhcp[2851]: DHCPOFFER(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 19:51:00 2017 daemon.info dnsmasq-dhcp[2851]: DHCPREQUEST(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 19:51:00 2017 daemon.info dnsmasq-dhcp[2851]: DHCPACK(br-lan) 192.168.1.130 94:65:2d:84:ae:14 OneplusKat
Her phone disconnected,and reconnected with no problems. it only seems to happen when her phone has been connected for some time and then tries to disconnect.
As I say this isn't a problem on my previous snapshot.
I am referring to network devices.
I've configured "static" IP's for printers, STB's, tablets, etc. on the LAN for years, never set lease times, and have not had any issues.
I don't know if this helps but if I disconnect the phone physically by turning Wi-Fi OFF on the phone. it disconnects however if the phone is connected but drops out of range it doesn't disconnect I just took my wife's phone approximately 100m away for 5 minutes and it still was showing connected on the router but zero signal.
log read
Tue Nov 7 20:05:32 2017 daemon.notice hostapd: wlan0: AP-STA-POLL-OK 94:65:2d:84:ae:14
Tue Nov 7 20:06:00 2017 cron.info crond[1594]: USER root pid 9654 cmd /usr/bin/presence_detection
Tue Nov 7 20:07:00 2017 cron.info crond[1594]: USER root pid 10086 cmd /usr/bin/presence_detection
Tue Nov 7 20:07:42 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: authenticated
Tue Nov 7 20:07:42 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 IEEE 802.11: associated (aid 1)
Tue Nov 7 20:07:42 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED 94:65:2d:84:ae:14
Tue Nov 7 20:07:42 2017 daemon.info hostapd: wlan0: STA 94:65:2d:84:ae:14 WPA: pairwise key handshake completed (RSN)
Tue Nov 7 20:07:42 2017 daemon.info dnsmasq-dhcp[2851]: DHCPDISCOVER(br-lan) 94:65:2d:84:ae:14
Tue Nov 7 20:07:42 2017 daemon.info dnsmasq-dhcp[2851]: DHCPOFFER(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 20:07:42 2017 daemon.info dnsmasq-dhcp[2851]: DHCPREQUEST(br-lan) 192.168.1.130 94:65:2d:84:ae:14
Tue Nov 7 20:07:42 2017 daemon.info dnsmasq-dhcp[2851]: DHCPACK(br-lan) 192.168.1.130 94:65:2d:84:ae:14 OneplusKat