Wireless LAN : How to prove that it sucks
by oBelIX
We all know that WLAN is sucking. There may be reasons (valid / invalid) but I somehow feel that the concerned authorities still feel that it is not “their” problem, or it isn’t slow enough to be a “major” problem yet. (Logically that could be the only explanation that accounts for the inaction – assuming that the “concerned” people are rational hbs). .NB -> hb = human being
How to benchmark WLAN’s performance
Lets make a utility. That sits in the system tray. It monitors the AP you are connected to, your signal strength, your ping time to 200 and your packet loss. Let this utility upload the data to some server. Or a webservice running on a server. We can make the methods of this web-service public.
Then, we would have some data to show that wireless actually sucks and sucks enough for the “concerned” people to do something about it.
Technically, since we all feel that it sucks, the “concerened” authorities should write this. Anyhoo, if for some reason they are reluctant then let my gre finish. I will write this utility. Or if someone wants to write it please do go ahead.
I suggest we should record whatever problems we face regarding LAN and Internet and other sysadmin issues with ourselves and show this to faculty sometime along with proofs if possible.
For example the utility u mention could be used as a proof for the speed that we got at various times during a day.
We could also record 204 was down at what all times. Also other problems like communication lab’s LAN keeps going down and the sysadmin has no idea why it got down.
We can create a list of probs and show to faculty(in some future meeting or by mail with authorization of all labcoms) that “There is really some problem”.
As u said we need to prove that things are going wrong in front of the faculty. The reason I want ppl to record things is to go to faculty all prepared instead of just blabbering whatever problem comes to our mind.
my response ??
go shout at faculty’s face. tell them that they have done enough to make students life hell.
then take a bedsheet and some sticks … put the bed sheet on sysadmin, bash him with the sticks ..
if he comes back to IIIT .. do the same again. do it till he quits