SNMP monitoring issue after upgrading to 384.4_2 on RT-AC5300

[orion44]

I've always used SNMP to monitor my WAN traffic (among others) and after upgrading to 384.4_2 the data returned no longer includes WAN traffic and instead is the LAN traffic.

Prior setup under 380.xx
Monitoring interface 005 (eth0) via SNMP
Shows only WAN traffic

Current setup under 384
Monitoring interface 005 (eth0) via SNMP
Shows all LAN traffic combined

I'm assuming the interface number wouldn't have changed as the result of a firmware update. Is there any hope to regain collecting WAN only traffic again?

 

[orion44]

To note, I've tried downgrading back to 380 and the monitoring of eth0 is still LAN traffic (combined). I re-upgraded to 384, did a factory default restore, new manual config, and still no dice. Is this something that transcends firmware? It seems odd it can't be remedied with the old FW version or a factory default restore. Losing out on WAN traffic data is pretty crappy as well.

 

[orion44]

Tools - System Information leads me to believe WAN traffic is now under vlan2 -- however the link state is down and no traffic is logged. Is this the root cause of the issue?

 

[orion44]

I'm not able to reproduce the issue with my RT-N66U since I can't run the new firmware. Is anyone else using the SNMP feature for monitoring and noticing a change in eth0 after updating to 384.x?

The only thing I haven't tried is going back to 380.x and then doing a factory reset. When I previously downgraded, it was a dirty downgrade. I'd rather not go backwards, but it might be my only option.

 

[orion44]

Success!

Steps to correct the SNMP issue:

1. Flash 380.x firmware
2. Perform factory reset
3. Power cycle router (optional)
4. Manually configure settings
5. Confirm SNMP working as expected
6. Restore prior config (optional)

I also noticed the average CPU usage dropped as well after reverting to 380.x

The increase was observed when I upgraded to 384.x last month

 

[orion44]

You can test with ASUS Stock Firmware v3.0.0.4.384.20648

Stock ASUS firmware doesn't offer SNMP.

 

[orion44]

Any idea if the SNMP issue can be corrected in a future 384 release? I'd rather not stay on 380 long term.

 

[RMerlin]

If the Ethernet driver doesn't play nice with SNMP then there's nothing I can do about it.

Try monitoring the vlan instead, see if you get better results.

Sent from my P027 using Tapatalk

 

[orion44]

I already tried monitoring every port, vlan or otherwise. None of the them provided WAN traffic data. Guess I'll stay on 380 until the next botnet targeting ASUS devices bricks it. By then the hardware should need replacing anyway.

 

[kfp]

Have you tried 384.5? I think ASUS added some code to address this issue, but they've f*cked up their programming causing 4GB spikes.
https://www.snbforums.com/threads/r...4-5-is-now-available.46575/page-9#post-405485

 

[unsynaps]

What are you using to generate the graphs?

 

[kfp]

What are you using to generate the graphs?

Looks like netdata.

 

[orion44]

What are you using to generate the graphs?

It's PRTG.

 

[orion44]

Have you tried 384.5? I think ASUS added some code to address this issue, but they've fcked up their programming causing 4GB spikes.
https://www.snbforums.com/threads/r...4-5-is-now-available.46575/page-9#post-405485

Interesting read, saw that post while searching if the SNMP issues might have been resolved. Will try a dirty upgrade and see.

 

[develox]

Just as an added option, I use collectd to collect various data from the router, including WAN and LAN traffic.

 

[orion44]

Interesting, thanks for sharing. I've never used collectd previously and it looks way more accurate than SNMP under the current firmware.

 

[cburkins]

Bit of an older thread, but wondering if it's still impossible to use SNMP to track WAN-only traffic ?

 

[orion44]

Yes, SNMP is dead. Long live SNMP!

 

[develox]

Bit of an older thread, but wondering if it's still impossible to use SNMP to track WAN-only traffic ?

Sorry for being late, but curious to find what would the advantage be in using SNMP rather than some regular data collector like netdata collectd, telegraf (though this might not be an option in our case), etc. Well, perhaps netdata would imply an heavier load (but it's also an all-in-one solution providing plenty of metrics and also a ready-made, very nice-looking GUI to visualize it, without the need of a monitoring chain like a storage (influx ?) and visualiser (grafana ?) to be held on another piece of hw).