BBR Line Monitoring A closer look at one of our site tools Posted on 2005-08-14 08:00:05 Written by lilhurricane
Have you ever wanted to brag about your broadband connection's stability but lacked the proof? What about those days when your connection seems a little sluggish but you are not sure why? Did you ever get the impression that the ISP call center doesn't believe you really have a problem?
Let's take a look at an easy way to compare your DSL, Cable, Satellite or other broadband connection with your neighbor across the street or around the globe. With BroadbandReports Line Monitoring you can have a wonderful diagnostic tool that provides detailed & reliable up-to-the-minute information about your connections.
Continuous easy to read graphing setup for your convenience:
BroadbandReports Line Monitoring provides you with Hourly, Daily, Long & Short Term reports. These diagnostic reports will arrive weekly in your email inbox and are available online anytime and look just like this one.
You'll have an interesting way to instantly see how your line conditions compare with fellow members or neighbors.
Some of our individual forums are already on board with Line Monitoring:
Southeast City Chat - which covers States in the Southeastern US including Kentucky, North Carolina, South Carolina, Georgia, Alabama, Mississippi, Virginia, Tennessee, and Florida here: Southeast Forum Line Monitor
1. A connection that is on 24/7, since that is the most effective way to monitor a connection. Those with Cable/DSL routers can take advantage of this easily, leaving the router on to be monitored. Those without routers will need to leave their PC’s running at all times, staying connected through PPPoE software.
2. A BBR Line Monitoring Service Account . The service costs 1 Tool Point (approximately $1 per week).
The first week is free. After the first week, you'll need to acquire Tool Points to continue participating.
*Note: Your monitor will be terminated after the first week if you do not buy tool points..
Here is a great way to help support the site while enjoying a super way to monitor your connection with the tools that only the pros use!
For more information or assistance - or for inclusion to one of the above forums, please contact either: jazzman916 or lilhurricane .
We'll be happy to get you started!
The BBR Line Monitoring is for informational purposes only and does not in any way replace official status reports or support from your ISP. Thanks to RadioDoc and others who were integral in building the original concept.
*** The information in this article was put together by jazzman916 and lilhurricane .
Basic monitoring is (was) free for signups prior to September 25th 2000. This does not mean accounts prior to that date, it refers to monitoring begun and continuously maintained since before that date. If free monitoring was interrupted and then re-initiated, it is no longer free.
New signups cost 1 Tool Point per week, per module.
To join one of these groups contact the Host/Moderator of the respective group forum e.g. contact jazzman916 , Host/Moderator of the AT&T Southeast Forum to join the AT&T Southeast-NC line monitor group.
The following are the current Line Monitoring groups providing the free monitoring service:
If you are providing any kind of service on your line (web, email or FTP or other), you know how important reliability is. Check up at any time, to ensure that everything has been continuously available while your attention was elsewhere. Get alerts of outages, leaving you free to pay attention to more important things.
Basic Monitoring provides ping time, packet loss & quality metrics, comparisons, graphics and optional weekly report via email for your Residential Line. We require that you reveal your ISP, location (zip code or country) and speed, so we can provide interesting public statistics.
Three tiny ping packets are sent no more than once every 10 minutes. This is considerably less than even the background "noise" a typical DSL or cable line has on it.
The dynamic monitor you setup is allocated a unique number. You can get this unique number from the link Line Monitoring Control Center.. it is the 6 digit number displayed after the text identifying your line monitor.
This six digit number is your "account" number for this line. You must provide the dynamic DNS client this number, it goes into the Host Name or DNS Name field.
Whether it is a DHCP line, or a PPPoE connection where you are allocated a new IP address every time you "log in", we can track this if you are prepared to install one of our supported dynamic DNS clients.
A dynamic DNS client is setup to "call home" (when it starts up or when it sees you have a new IP address) to tell us what the current IP is. When we see the IP address change, we flip to monitoring the new IP!
Warning for PPPoE users: If you are not always-on, then the disconnection of PPPoE when you logout, requires your dynamic DNS client to place your IP into an offline state first by telling us this, otherwise we will not know you have logged out!
The dyndns.com support page has links to a number of clients for various operating systems.
We have only currently tested operation with windows clients: Dynamic DNS 4.0, DeeEnEss and the DynSite client but our Mac/OS X users also recommend dyndns.com and OpenDNS.
If you have a client that supports plugins, just copy and modify whatever dyndns.org config file it comes with, changing the update url to www.dslreports.com/nic, and thats it!
If you prefer to use the free dynamic DNS update software provided by the dynamic DNS host, such as the N0-IP.com's program rather than "shareware" like DynSite that one has to pay extra for, or may not wish to run multiple DNS update clients at the same time.
Check 'Dynamic IP' Enter your dynamic DNS name into 'IP from this DNS' Save the setup.
Wait up to two minutes then check, if the DNS name resolves, the IP will show in the 'STATIC IP' field, but it will change when your DNS name resolves to a new IP.
If a member with DHCP or PPPoE service elects to supply a domain name (such as "rdotson.net" for example) in lieu of a static IP address, he or she has the responsibility to ensure that their DNS listings are kept current.
Please download dyndns.zip <-- extract this zip file into your Dynamic DNS 4.0 directory. This should add a dslreports service to the menu of services. Having done that, setup the screen as per this screenshot.
The dynamic monitor you setup is allocated a unique number. You can get this unique number from the link Line Monitoring Control Center.. it is the 6 digit number displayed after the text identifying your line monitor.
This six digit number is your "account" number for this line. You must provide the dynamic DNS client this number, it goes into the Host Name or DNS Name field.
You must also tell the Dynamic DNS client your dslreports login name and password, as the update procedure is password protected.
Windows client DynSite has just been upgraded to include support for DSLreports monitoring from the start. Or, if you have an older version, simply download dslr.zip and extract the contents (one file) into your DynSite program directory, restart DynSite.
When it is running, use the account assistant (right mouse button from the dynsite icon in your windows system tray) to find "dslreports monitoring" (Dynamic DNS server-type).
Select dslreports monitoring and continue, as with any client we support, you must put in your dslreports site login and password (check the "this account needs a password" option). Then move on to "configure a host", enter your dynamic monitor line account number as the "Host" (leave domain name as dslreports.com), and provide any screen name and account name you wish (these are for DynSite display only).
If you have done everything correctly, have configured DynSite elsewhere to say you are on a fulltime connection, and are online, DynSite will quickly update your line monitor with your public IP, and show "Successfully updated" against entry NNNN.dslreports.com in its main status window.
The status tab of DynSite may say The host does not resolve yet, this message can be ignored, as it relates to dynamic DNS services.
You should also be able to verify this IP is now listed in the Maintain Monitors link above.
The smallest and simplest client is DeeEnEss but that is good for DHCP connections only, it does not handle PPPoE logoff in any way.
For a fully featured client capable of updating many dynamic DNS services, and the DSL reports monitor as well, try DynSite. If you don't like either of these, try Dynamic DNS 4.0 or Dynamic DNS Client .NET Edition - Lite.
Common causes: • Your DSLR account is still unverified. You must have received the temporary password and logged in using it, to fix your account. If you are unsure of the status of your account, visit this page to check. To manually check you can authenticate, please visit this URL to check that it at least accepts your username and password OK. If you get past the username/password prompt ok, then all is well, and you will get a page with the message: Error: Invalid Action. • You have not entered your dslreports login name and password into your dynamic DNS client correctly. Verify carefully you are using the same username and password as you would do to login to the site. • You are not entering the correct line monitoring account number into your dynamic DNS client. It should be a six digit number starting with 1 or 2 or 3.. this number is explained here:
In the accounts section, find dslreports in the Server list, and click ADD. Now edit these entries: Put your Account Number into Host, enter your dslreports username and password into the next two fields.
DeeEnEss needs to figure out your public IP address. It might have trouble with this if you public IP address is not on your actual PC, but on a router or proxy server.. in which case, you probably need to change IP Detection to Web based and Interface to DynDNS.
DDClient, is easily configurable to support BroadbandReports monitoring. Follow the INSTALLATION instructions, edit /etc/ddclient.conf to add an entry that looks like
The machines that (currently) do the monitoring are
ny-monitor.dslreports.com sjc-monitor.dslreports.comno longer available 64.81.79.40 & 64.81.79.41(sfo-monitor.dslreports.com)
These hosts should be be added to your firewall if ICMP ping is being blocked. The IP addresses do change from time to time, so if you must enter IP address and not DNS name, then please do an NSLOOKUP or PING to make sure of the current IP address.
Zone Alarm has two zones. Local Zone and Internet Zone. It is normal to set Local Zone security to medium or lower. You must then place our monitoring stations into the list of "local hosts". Please check this screenshot to see an example of the properties screen of Local Zone setup correctly to except our monitoring systems. Please note that the IP's in that screenshot are not the current IP's.
The machines that (currently) do the monitoring are
ny-monitor.dslreports.com sjc-monitor.dslreports.com dslreports-west2.speakeasy.net (64.81.79.40 AND 64.81.79.41)
These hosts should be be added to your firewall if ICMP ping is being blocked. The IP addresses do change from time to time, so if you must enter IP address and not DNS name, then please do an NSLOOKUP or PING to make sure of the current IP address.
Important: if you PADLOCK your zonealarm, no matter what, you are disconnected from the net. This will break monitoring. If you wish fulltime line monitoring, the PADLOCK function should not be used.
If you have a SonicWALL hardware firewall there are two methods you can use to setup your system to respond to pings:
Method 1: You can pass incoming pings through the SonicWALL to a PC on the LAN and then have the PC respond to the pings.
Method 2: You can have the SonicWALL respond to pings directly. To use Method 1 (your PC responds to pings) follow these steps:
(1a) Open the SonicWALL web admin by entering the SonicWALL's LAN IP address into a web browser on a PC on the LAN side of the SonicWALL.
(1b) Go to Access, Services and make sure Ping shows up in the list of services. If not, add the Ping service.
(1c) Go to Access, Rules, Add New Rule and add two rules Rule 1 - Action=allow - Service=ping - Source=WAN, 216.200.176.6 <= DSLR WC server “sjc-monitor.dslreports.com” - Destination=LAN, 192.x.x.x <= LAN address of PC to respond to pings Rule 2 - Action=allow - Service=ping - Source=WAN, 206.65.191.129 <= DSLR EC server “ny-monitor.dslreports.com” - Destination=LAN, 192.x.x.x <= LAN address of PC to respond to pings
(1d) If you have a software firewall on the LAN PC be sure to allow pings there as well. To use Method 2 (SonicWALL responds to pings) follow these steps:
(2a) Open the SonicWALL web admin by entering the SonicWALL's LAN IP address into a web browser on a PC on the LAN side of the SonicWALL.
(2b) Go to Access, Services and make sure Ping shows up in the list of services. If not, add the Ping service.
(2c) Go to Access, Rules, Add New Rule and add two rules Rule 1 - Action=allow - Service=ping - Source=WAN, 216.200.176.6 <= DSLR WC server “sjc-monitor.dslreports.com” - Destination=LAN, 192.x.x.x <= LAN address of SonicWALL Rule 2 - Action=allow - Service=ping - Source=WAN, 206.65.191.129 <= DSLR EC server “ny-monitor.dslreports.com” - Destination=LAN, 192.x.x.x <= LAN address of SonicWALL General notes:
You can have the SonicWALL “stealth mode” enabled (Access, Services, Stealth Mode) and both methods will still work.
You can use “*” for the WAN address in the SonicWALL rules to allow pings from anyone, but the nice thing about using explicit rules for each DSLR server is that you don't make yourself visible to the general public. I don't think it's a security risk to leave the server-specific rules in place. Of course, if DSLR changes their server IP addresses you need to change your rules.
If your firewall responds to ICMP ping packets, as many do, then we can monitor your connection. Instructions for specific firewalls and network share devices follow.
Recent Linksys, DLink and other routers' firmware allows you to configure the router to be unpingable from outside. "Block WAN Requests" for older devices and "Block Anonymous Internet Requests" for newer 'Cisco' branded devices. DLink uses "Discard PING from WAN side". Enabling these router features will break monitoring.
We recommend if you wish to be monitored, do not select the "Block WAN Requests"/"Block Anonymous Internet Requests"/"Discard PING from WAN side" option on the router configuration screen. Your router can still be password protected, and will be secure.
Also try disabling "SPI" , as this also may block external pings.
Configure to allow incoming icmp request and outgoing icmp reply to/from our two monitoring stations. move these rules to be 1st rules just to be sure that they wont' be blocked by any other rules.