Posted: Wed Apr 10, 2019 4:31 Post subject: RouterGraph: A WAN traffic grapher
This is a program for Windows that displays SNMP data. It's main purpose is graphing WAN traffic, and it also shows how much CPU and RAM is being used on the router.
You'll need to enable SNMP on the Services tab in DD-WRT. You can leave the default values alone. The only setting RouterGraph cares about is RO Community. For best results, use build 39137 or older because SNMP only updates every three seconds in newer builds.
If RouterGraph doesn't appear to be doing anything, or if you see red lines, you might need to change one or more settings on the Options window. OIDs can vary depending on which router and DD-WRT build you're using. Paessler SNMP Tester and SolarWinds SNMP Walk are two useful programs for figuring out which OIDs to use.
To figure out which interface the WAN port is on, go to the Setup -> VLANs or Status -> Bandwidth page in DD-WRT. If your WAN is on VLAN2 then that's what you should look for when using the above programs.
The screenshots show a large file that was downloaded. It basically maxed out the internet connection (120Mbps). After the file completed, the first screenshot makes it seem that there was no WAN traffic for awhile, but the second screenshot shows low level traffic.
There's three separate graphs:
1. Top shows 0 to 120mbps
2. Middle shows 0 to 1mpbs
3. Bottom shows 0 to 4kbps
SNMP can be complicated. But you don't really need to know much about it. All you need is your router's IP (usually 192.168.1.1), the SNMP community name (usually "public") and a few OIDs.
Do you have a way to get this working properly with current firmware? It seems like something is broken in DD-WRT's snmpd for almost the last year now. My graphs just show spikes. It might be accurate if it ignores the 0 values, but it seems like an issue with the firmware.
Do you have a way to get this working properly with current firmware? It seems like something is broken in DD-WRT's snmpd for almost the last year now. My graphs just show spikes. It might be accurate if it ignores the 0 values, but it seems like an issue with the firmware.
There's been trouble with SNMP in some of the builds from the past two years. It might have been fixed by now but I've just been using v3.0-r38570 std (02/04/19) since it still works.