Inssider interface suggestions
Submitted by mysticvirgo on Fri, 11/21/2008 - 10:11.
inSSIDer is great! but there are a few small improvements that can be made:
A more in depth sorting of the data , IE sot by signal strength then sub sort by security then by SSID.
A connect feature and maybe even an auto connect feature
A scrollable graph
Save Data & Save Image instead of copy data and copy image
Hide Options; Hide Secured/Unsecured networks, HideRSSI strength above/ below value, ect
shorter inactive network deletion intervals under one minute
I think that these ?upgrades? will help users better digest the often overwhelming amount of signal information that occurs in urban enviroments and likewise increase inSSIDers utility for Wardrivers
I tried out your inSSIDer program... Everything seemed nice, lots of networks discovered, lots of information about them...
But the shock came immedeately after: Your program fouled up the connection in the server of our wireless provider.
I am still angry about that!
Why should a blody network scanning and monitoring program wreck the connection to our server.
Don't release such programs, if you can't get them right!
The access point had to be reset to make our WiFi connection work again. This is lousy!!!
The network icon in Windows said: "Excellent signal strength, limited or no connectivity"
Stephan
Thank you very much for these suggestions! Some of these have already been suggested, but I will add the others on to our to-do list for inSSIDer!
inSSIDer is open source, so if any of you add these changes by chance, let us know and we'll implement them!
We've been busy working on Chanalyzer 3.2, Wi-Spy DBx, and a few other cool things you should look forward to in the future!
This would be trivial to add but could you please bold the currently connected to BSSID (I would imagine this would only work on Windows Vista).
I have 2 APs, same channel, same SSID to permit "roaming" and I can see which SSID I am connected to by doing netsh wlan show interface. It'd be great if I could "watch myself roam" or just to diagnose how aggressively the Intel network card is roaming.
As far as I can recall NetStumbler used to put a "*" next to the currently connected to access point/ router.
It'd add a lot to the program in so few lines of code.