How to check if DSLstats will work with a different modem
As stated elsewhere, DSLstats can work with most
Broadcom-based modems which have a fully functional telnet interface
giving access to the Busybox shell. If you have such a modem, but it
isn't on the drop-down list of recognised devices on the login
configuration page, here's what you can do to check it.
First, check if there are any other modems from the same manufacturer with similar model numbers. If so, selecting one of these may be all you have to do, otherwise read on.
Telnet access
Next you need to attempt to log in to the modem by telnet. Linux systems have a telnet client already available, and you just need to open a terminal and enter "telnet <IP address of the modem>". Windows users need to install a telnet client, and Putty is a popular one. If the modem doesn't respond to the telnet access command, then DSLstats will not work with this modem, unless you can find some way of getting past the barrier, which is outside the scope of this document.
If the modem responds with a request for a user name and password then you can enter these if you know them. Almost always these login details will be the same as the details you enter when you access the GUI using a browser. If you don't know the login details you'll need to get them from the manufacturer, or from your ISP if they supplied the modem. Unfortunately, you may encounter resistance to giving out this information.
Checking for Broadcom CLI commands
Assuming that you've logged in successfully, do you see a Busybox welcome message? If you don't, but just see a prompt such as ">" or "$" or "#", the followingmight work, but you may
need to enter a further command in order to reach the shell. This
further command could be "sh" or "shell".
Now try to enter one of the Broadcom CLI commands. Enter "<Command prefix> info --show". <Command prefix> could be one of several possibilities, such as:
If one of these commands produces a stream of data, then you have the necessary information. Logout from the telnet connection. Enter the details which were successful into the DSLstats Login configuration page, including the extra command to reach the shell, if required. DSLstats should now work with this modem.
First, check if there are any other modems from the same manufacturer with similar model numbers. If so, selecting one of these may be all you have to do, otherwise read on.
Next you need to attempt to log in to the modem by telnet. Linux systems have a telnet client already available, and you just need to open a terminal and enter "telnet <IP address of the modem>". Windows users need to install a telnet client, and Putty is a popular one. If the modem doesn't respond to the telnet access command, then DSLstats will not work with this modem, unless you can find some way of getting past the barrier, which is outside the scope of this document.
If the modem responds with a request for a user name and password then you can enter these if you know them. Almost always these login details will be the same as the details you enter when you access the GUI using a browser. If you don't know the login details you'll need to get them from the manufacturer, or from your ISP if they supplied the modem. Unfortunately, you may encounter resistance to giving out this information.
Assuming that you've logged in successfully, do you see a Busybox welcome message? If you don't, but just see a prompt such as ">" or "$" or "#", the following
Now try to enter one of the Broadcom CLI commands. Enter "<Command prefix> info --show". <Command prefix> could be one of several possibilities, such as:
- adsl
- adslcfg
- adslcmd
- xdsl
- xdslcfg
- xdslcmd
- xdslctl
If one of these commands produces a stream of data, then you have the necessary information. Logout from the telnet connection. Enter the details which were successful into the DSLstats Login configuration page, including the extra command to reach the shell, if required. DSLstats should now work with this modem.