![]() What Does Scanning for Wireless Network Devices Do? You can also use Wi-Fi scanning software to discover areas in your facility with a weak Wi-Fi signal. Using a Wi-Fi network analyzer for consistent Wi-Fi scanning helps you collect data and identify problems and indicate potential solutions, such as switching to another channel to reduce congestion. Wi-Fi signals are constantly changing, and small changes in the network can have massive effects on the overall connection uptime. A wireless network analyzer can help you maintain connection quality, which can be vital for numerous business needs and performance metrics. In simple terms, a Wi-Fi analyzer or scanner gathers information about access points and channels on your network and displays it in an easy-to-understand, visually accessible way. ![]() The Wi-Fi analyzer then examines the spectrum to view networks, their channels, and signal strength. Admittedly, I'm torn between posting this in SuperUser or ServerFault, so opinions of where this should go are welcome.Most Wi-Fi network analyzers work in a similar way, in which you can choose a wireless spectrum to examine, such as 2.4GHz or 5GHz. I have a hotspot set up on my Raspberry Pi 4, running Raspian. I used hostapd to set it up, following the guide from the Pi Foundation's website as I hadn't done anything like that before. The network technically works, and if I get another device to connect fast enough, it accepts the Passphrase and connects, however every few minutes the connected devices all disconnect, and if I try to reconnect with the saved passphrase on them, I get a "Incorrect Passphrase" error. If I delete the saved network record on any given device, it connects with the same passphrase, and then disconnects a short while later again. I thought it could be signal strength, but running NetSpot on a Notebook even further away from the Pi shows great signal strength. The network was suddenly listed a second time, and the first listing showed as no longer being in range. The only difference I could find: the second network had a different BSSID. The longer I left Netspot scanning, the more copies of the network turn up with new BSSIDs, and the previous networks show as out of range. I tried setting the BSSID explicitly in my hostapd config, which makes it take longer the change BSSID the first time, but after that first change, it goes back to the 2-3 minute frequency. I am honestly out of my depth here at this point, I typically just work on Ethernet networks (I have a well wired home so beyond my router's network for my phone, why wouldn't I go wired?).Īny pointers to find the cause would be amazing. (Why a wifi hotspot I hear you ask, since there is a working router here anyway? The Pi is running my HomeAssistant instance, and I want to pop smart home devices I don't trust to be connected to the internet on the Pi's hotspot and have HomeAssistant control them, such as my aircon, that does not use TLS for it's commands and sends the login username and password in plaintext back and forward on every command, and my TV, which allows app remote control that is better than the physical remote, but is unlikely ever to get a security update because, well, smart TVs)Īccept_mac_file=/etc/hostapd/hostapd.accept I'm generally pretty comfortable with the Bash terminal. My hostapd.accept file just has the MAC addresses of all the devices I intend to connect to it, each on it's own line, with no spaces or commas. Turning off the MAC ACL option and removing the accept file line does not change the network behaviour.
0 Comments
Leave a Reply. |