What's new

Strange things with UPnP

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

TheLyppardMan

Very Senior Member
I have used Networx network traffic monitor for a number of years and had no problems with it until I started using my RT-AC86U. Networx can either be set to monitor traffic to/from your own computer or to monitor the whole network. For the latter, it gives you the option of either using SNMP, which I have always used before changing my router or UPnP (my only choice with my RT-AC86U as it doesn't have SNMP capability).

Now here's the strange bit - Networx will only run correctly for a short time after a reboot of the router, after which, either the download monitoring or the upload monitoring stops working.

A second strange thing is that one of my security cameras recognises UPnP but the other does not and they are both made by the same manufacturer.

I am uploading some screenshots to show you what I am seeing. On the traffic graph, you can see the situation before rebooting the router and then immediately afterwards. Any ideas about how to diagnose the problem? Oh and yes, I had tried diabling my internet security firewall (ESET).
 

Attachments

  • 001.jpg
    001.jpg
    14.6 KB · Views: 220
  • 002.jpg
    002.jpg
    13.6 KB · Views: 372
  • 003.jpg
    003.jpg
    34.3 KB · Views: 380
  • 004.jpg
    004.jpg
    28 KB · Views: 352
I have used Networx network traffic monitor for a number of years and had no problems with it until I started using my RT-AC86U. Networx can either be set to monitor traffic to/from your own computer or to monitor the whole network. For the latter, it gives you the option of either using SNMP, which I have always used before changing my router or UPnP (my only choice with my RT-AC86U as it doesn't have SNMP capability).

Now here's the strange bit - Networx will only run correctly for a short time after a reboot of the router, after which, either the download monitoring or the upload monitoring stops working.

A second strange thing is that one of my security cameras recognises UPnP but the other does not and they are both made by the same manufacturer.

I am uploading some screenshots to show you what I am seeing. On the traffic graph, you can see the situation before rebooting the router and then immediately afterwards. Any ideas about how to diagnose the problem? Oh and yes, I had tried diabling my internet security firewall (ESET).
provide a screen shot of the port forwarding from syslog/portforwarding tab and your upnp settings from wan internet connection tab
 
provide a screen shot of the port forwarding from syslog/portforwarding tab and your upnp settings from wan internet connection tab
Here you go...
 

Attachments

  • 005.jpg
    005.jpg
    54.2 KB · Views: 353
  • 006.jpg
    006.jpg
    13.5 KB · Views: 353
Networx has been working OK for most of the day, after I rebooted the router this morning, but download data has stopped showing again now.
 
Here you go...

Regardless of what the camera shows, the upnp looks like its working based on the screen shot. It could be that both cameras are trying for the same exact ports externally. But both ip addresses are listening externally on the ports that show in your screenshot via udp. Your two cameras are listening on different ports internally which is different than what i would expect. Usually apps (IOT hardware) don't change listening ports dynamically. It's like i want to call you , but you keep changing the number. UPNP security may be preventing one device overwritting the others upnp registration.

For example, with my samsung cameras the internal listening port is always 40000 - the external upnp ports are different because externally there is only one ip and the port forwarding with the PAT can only be done through tcp/udp port mapping (you can't have one port 40000 open externally and mapped to 5 cameras using a single ip). This way the cameras never conflict with each other externally. Traffic coming in externally to port 41000 is then destined for 40000 on the ip address 192.168.1.233

TCP 41000 192.168.1.233 40000 17049h 0m 45s NAT-PMP 41000 tcp
TCP 41002 192.168.1.159 40000 17049h 0m 47s NAT-PMP 41002 tcp
TCP 41004 192.168.1.253 40000 17049h 0m 52s NAT-PMP 41004 tcp
TCP 41001 192.168.1.225 40000 17077h 4m 31s NAT-PMP 41001 tcp
TCP 41003 192.168.1.166 40000 17084h 20m 41s NAT-PMP 41003 tcp

Even though the extenal ports numbers are different here, the cameras then register themselves with the samsung service that knows camera 1 is at my public ip on port 41000 and cameras 2 is on my public ip on port 41002.

Also, i don't know if your cameras support tcp. It may give you better results.

I don't have a ac86...but from ac88
http://192.168.1.1/Advanced_SNMP_Content.asp
 
Last edited:
Regardless of what the camera shows, the upnp looks like its working based on the screen shot. It could be that both cameras are trying for the same exact ports externally. But both ip addresses are listening externally on the ports that show in your screenshot via udp. Your two cameras are listening on different ports internally which is different than what i would expect. Usually apps (IOT hardware) don't change listening ports dynamically. It's like i want to call you , but you keep changing the number. UPNP security may be preventing one device overwritting the others upnp registration.

For example, with my samsung cameras the internal listening port is always 40000 - the external upnp ports are different because externally there is only one ip and the port forwarding with the PAT can only be done through tcp/udp port mapping (you can't have one port 40000 open externally and mapped to 5 cameras using a single ip). This way the cameras never conflict with each other externally. Traffic coming in externally to port 41000 is then destined for 40000 on the ip address 192.168.1.233

TCP 41000 192.168.1.233 40000 17049h 0m 45s NAT-PMP 41000 tcp
TCP 41002 192.168.1.159 40000 17049h 0m 47s NAT-PMP 41002 tcp
TCP 41004 192.168.1.253 40000 17049h 0m 52s NAT-PMP 41004 tcp
TCP 41001 192.168.1.225 40000 17077h 4m 31s NAT-PMP 41001 tcp
TCP 41003 192.168.1.166 40000 17084h 20m 41s NAT-PMP 41003 tcp

Even though the extenal ports numbers are different here, the cameras then register themselves with the samsung service that knows camera 1 is at my public ip on port 41000 and cameras 2 is on my public ip on port 41002.

Also, i don't know if your cameras support tcp. It may give you better results.

I don't have a ac86...but from ac88
http://192.168.1.1/Advanced_SNMP_Content.asp
Thanks for the analysis. The cameras aren't really a problem as I can use a dedicated app to view them and they seem to work either using UPnP or Port Forwarding. Networx was the main thing I wanted to diagnose, but I can manage without it if it isn't going to work properly on the network option. The RT-AC86U doesn't have SNMP unfortunately, so I can't use that option with this router.
 
Yes, I have looked at that a few times, just to check on historic data, but the great thing about Networx, when it works that is, is that it provides real-time graphical data on download and upload speeds. It works fine with an SNMP-enabled router, but only intermittently using UPnP (at least, with my particular router).
 

Attachments

  • 001.jpg
    001.jpg
    14.5 KB · Views: 316
  • 002.jpg
    002.jpg
    25.5 KB · Views: 366
  • 003.jpg
    003.jpg
    13.3 KB · Views: 313

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top