Contents > Third party:
I was browsing the IDnetters forum and came across references to a Line Monitoring tool called RouterStats, developed by John Owen. There are two versions: the 'Lite' edition works with 2700 hubs.
To download RouterStats Lite, Click here for link to vwlowen.co.uk
I downloaded the zipped version of 'RouterStats Lite' v4.6. The zip file contained a single executable called RouterStatsLite.exe
Once extracted to my Windows XP computer, I ran the file and followed the simple instructions to enter my router model (2Wire 2700HG-B, -V) and confirm the IP address of my 2700HGV hub (ie. 192.168.1.254). I didn't enter my router login name & password.
Sample screen dump of RouterStats Lite connected to my hub running BT v220.127.116.11 firmware.
Link to RouterStats forum
I've not investigated whether the full RouterStats edition is compatible with 2700 at time of writing.
I usually use netstumbler to view the presence of other wireless networks. However netstumbler isn't compatible with all wireless hardware or all versions of Windows.
I came across this open source utility last week called InSSIDer
Click on here to visit the InSSIDer webpage.
It runs on Windows XP and Vista, including 64 bit editions apparently. Please note: Microsoft .NET framework 2.0 or higher must be installed before you can install and use InSSIDer. I understand Vista includes .Net framework v3.0.
However, if you are using Windows XP, you can perhaps determine which version of .NET framework may already be installed on your Windows XP computer by looking in the following folder (assuming windows is located in c:\windows):
If folder names beginning v2.0, v3.0, v3.5 and/or v4.0 exist, then you have .Net Framework installed.
Note that if you choose to download and install .NET Framework 3.5 from Microsoft website, it is about 250Mb in size! v3.5 includes v2.0 and v3.0.
Alternatively, you could just download and install .NET Framework 2.0. This is about 22Mb in size. Note that Windows Update may attempt to upgrade you to v3.5 ! You can stop this from happening by manually running Windows Update and hiding the .NET Framework v3.5 upgrade.
Use 'Back' button to return to previous page or click here to return to main menu