[GH-ISSUE #267] Bug with scanned stations if you re-scan for networks #158

New issue

Closed

opened 2026-02-27 23:23:23 +03:00 by kerem · 2 comments

kerem commented

2026-02-27 23:23:23 +03:00

Owner

Originally created by @samdenty on GitHub (Aug 8, 2017).
Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/267

Latest version affected: yes

How to replicate

Scan for WiFi networks
Select a network that your want to scan for stations
Go to the stations page and scan
Once the scanning is complete, go back to the WiFi networks page
Scan for new networks
If there are different networks (than the previous scan), going back to the stations page will change the network displayed next to the Stations

Originally created by @samdenty on GitHub (Aug 8, 2017). Original GitHub issue: https://github.com/SpacehuhnTech/esp8266_deauther/issues/267 Latest version affected: yes ### How to replicate 1. Scan for WiFi networks 2. Select a network that your want to scan for stations 3. Go to the stations page and scan 4. Once the scanning is complete, go back to the WiFi networks page 5. Scan for new networks 6. If there are different networks (than the previous scan), going back to the stations page will change the network displayed next to the Stations

kerem

2026-02-27 23:23:23 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-27 23:23:24 +03:00

Author

Owner

@spacehuhn commented on GitHub (Aug 8, 2017):

Thanks!
I guess the station-list is not cleared when scanning for new APs. It saves the old ID from the AP, but by scanning fo new APs the IDs may change therefor making a faulty station list.

@spacehuhn commented on GitHub (Aug 8, 2017): Thanks! I guess the station-list is not cleared when scanning for new APs. It saves the old ID from the AP, but by scanning fo new APs the IDs may change therefor making a faulty station list.

kerem commented

2026-02-27 23:23:24 +03:00

Author

Owner

@tobozo commented on GitHub (Mar 24, 2018):

fixed in the next version, closing this

@tobozo commented on GitHub (Mar 24, 2018): fixed in the next version, closing this