RF Detector?

Take a computer that is not connected to the internet and plug the NVR into the ethernet port of the computer. Make sure the computer and NVR are on the same IP subnet. Then open a web browser and type in the IP address of the NVR or open SmartPSSLite.
 
You shouldn't need to be proficient in networking to run some of these steps, especially this part:
In terms of router security:

If you are struggling to interpret the results, just post them here. What AV are you running on your PC (and what OS)?
 
Honestly, I am not well versed when it comes to networking.
OK, but here is a simple non-technical thing that you can do that may provide potentially useful information.
One of the many services that will do an inbound scan from the internet to see if there are any holes in your inbound firewall protection.

This just needs you to 'connect the NVR to the internet' as you've described you normally do for reviewing recordings, and use the browser on your PC to visit this site that can check inbound access -
Use the first 'Proceed' button, then select the 'All Service Ports' option.
Wait for the scan result, hopefully all green.
 
Now if we could probe my gf's ports to see how to make her silent that would be nice.
Yes, one port in particular you would not want exposed......:facepalm:
 
How do you guys get the neat stealth readings? Attached is what I got
 

Attachments

  • Testresult1.jpg
    Testresult1.jpg
    240.3 KB · Views: 9
Take a computer that is not connected to the internet and plug the NVR into the ethernet port of the computer. Make sure the computer and NVR are on the same IP subnet. Then open a web browser and type in the IP address of the NVR or open SmartPSSLite.
I had to wrestle with the web plugins but finally managed to get it to work. Did I mention I hate the damn plugins? And they usually are ok for a while and then need to be reinstalled
 
You have run a UPnP scan. That's good, but the other half of the test is a port scan. Instead of pressing the big yellow instant UPnP button, press the All Service Ports button, and post that result.
Took me a bit to find that selection. Looks ok
 

Attachments

  • TestScan2.jpg
    TestScan2.jpg
    280 KB · Views: 7
Looking good. Are all the blocks green, screenshot has cut of the ports lower than about 160 which are some of the most important to check.
 
Took me a bit to find that selection. Looks ok
Well done!
Yes, that's a perfect scan result, there are no listening ports found on the inbound scan.
A full stealth result, as it should be.

However - a question - did you have the NVR powered on and 'connected to the internet' as you normally used to for reviewing recordings? Not just directly connected to the laptop?
Even with an inbound hole in a firewall configuration, there has to be an active, listening, port in order for that inbound hole to be discovered.
Turn off, or disconnect, the target device and there will be nothing to respond to the inbound probe, which would give a misleading result even with a firewall hole.
 
  • Like
Reactions: Flintstone61
Well done!
Yes, that's a perfect scan result, there are no listening ports found on the inbound scan.
A full stealth result, as it should be.

However - a question - did you have the NVR powered on and 'connected to the internet' as you normally used to for reviewing recordings? Not just directly connected to the laptop?
Even with an inbound hole in a firewall configuration, there has to be an active, listening, port in order for that inbound hole to be discovered.
Turn off, or disconnect, the target device and there will be nothing to respond to the inbound probe, which would give a misleading result even with a firewall hole.
No, the NVR was not connected to the network/internet
 
It might be interesting if you repeat the test with the NVR connected as it normally used to be.
Certainly do this. Just to make 100% sure.

Something I don't understand... I have a working L2TP VPN listening on UDP port 1701, but nothing shows up when I do a "User Specified Custom Port Probe" on that port? ...
Very likely because your L2TP server listens on UDP, but the scanner is only scanning TCP. Scanning UDP is hard, actually.

Side note, is your VPN plain L2TP or L2TP + IPsec?