NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
kochin
Jun 24, 2019Apprentice
miniupnpd doesn't update total bytes sent/receive
I tried to get router traffic information from my Orbi RBR50 using it IGD feature. When I ran the upnpc program to retrieve information, I found the total bytes received and sent never get updated and stay at 4294967295 while the total packets sent and received get updated as expected.
d:\Downloads\win32-miniupnpc-2.1>.\upnpc-shared.exe -s -m 192.168.0.1 upnpc : miniupnpc library test client, version 2.1. (c) 2005-2018 Thomas Bernard. Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/ for more information. List of UPNP devices found on the network : desc: http://192.168.0.1:5555/rootDesc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 Found valid IGD : http://192.168.0.1:5555/ctl/IPConn Local LAN ip address : 192.168.0.2 Connection Type : IP_Routed Status : Connected, uptime=5466s, LastConnectionError : ERROR_NONE Time started : Sun Jun 23 20:10:35 2019 MaxBitRateDown : 1000000 bps (1.0 Mbps) MaxBitRateUp 1000000 bps (1.0 Mbps) ExternalIPAddress = xx.xx.xx.xx Bytes: Sent: 4294967295 Recv: 4294967295 Packets: Sent: 25029827 Recv: 71936774
Orbi runs a version of miniupnpd which is supposed to provide those information. It appears the miniupnpd in the firmware is buggy. Netgear, please have your developers take a look. Thanks.
10 Replies
Sort By
Please file a support ticket here and give all details and debut logs to them for review:
https://www.netgear.com/mynetgear/registration/login.aspx
Thank you.
kochin wrote:I tried to get router traffic information from my Orbi RBR50 using it IGD feature. When I ran the upnpc program to retrieve information, I found the total bytes received and sent never get updated and stay at 4294967295 while the total packets sent and received get updated as expected.
d:\Downloads\win32-miniupnpc-2.1>.\upnpc-shared.exe -s -m 192.168.0.1 upnpc : miniupnpc library test client, version 2.1. (c) 2005-2018 Thomas Bernard. Go to http://miniupnp.free.fr/ or https://miniupnp.tuxfamily.org/ for more information. List of UPNP devices found on the network : desc: http://192.168.0.1:5555/rootDesc.xml st: urn:schemas-upnp-org:device:InternetGatewayDevice:1 Found valid IGD : http://192.168.0.1:5555/ctl/IPConn Local LAN ip address : 192.168.0.2 Connection Type : IP_Routed Status : Connected, uptime=5466s, LastConnectionError : ERROR_NONE Time started : Sun Jun 23 20:10:35 2019 MaxBitRateDown : 1000000 bps (1.0 Mbps) MaxBitRateUp 1000000 bps (1.0 Mbps) ExternalIPAddress = xx.xx.xx.xx Bytes: Sent: 4294967295 Recv: 4294967295 Packets: Sent: 25029827 Recv: 71936774
Orbi runs a version of miniupnpd which is supposed to provide those information. It appears the miniupnpd in the firmware is buggy. Netgear, please have your developers take a look. Thanks.
- kochinApprentice
FURRYe38Thank you for responding.
Unfortunately, my 90 days support had expired months ago. I don't see a way to submit bug reports without having a valid support contract with Netgear.
I can only hope someone from Netgear is monitoring its community site and will forward the issue to their development team.
Please send a PM to Blanca_O and Christian_R and see if they can help pass this on to NG engineering. Be aware that even though you report it to NG, it may not get changed, if at all or will take a while for it to appear, even it it does get changed. If miniupnp is working over all and the report function isn't working, maybe something that NG may not look into that much. Just saying. Hope it will get looked at.
Good Luck.
- kochinApprentice
I just realized Orbi IGD does update bytes sent/received. After I rebooted my Orbi, my Home Assistant setup started getting those information from it. However, once the byte received count has reached 4294967295, it stays there.
It seems that Orbi clears out the counters on reboot. Apparently, those counters are recorded in 32-bit variables. When the count reaches 4294967295 = 2^32-1, it stops counting. (But I wonder why it doesn't roll back to 0.)
On second thought, it might be Home Assistant which is using 32-bit counters. I guess it's time to check the source code.
Something to let NG support know about.