Okay, say I have some public IP address 64.0.0.1 or something like that. And that address is basically to a router on my home network. (no my actual IP mind you)
Is there anyway for The Dude to scan my private network if I enter my public IP into the scan field? I have one Set up with 192.168.0.0/24.
There is no way for Dude to understand what devices are behind a NAT by scanning the public IP address of the NAT. But you can scan the private IP subnet of your local LAN if you setup a VPN between your home network and your work network. Or if you are using Cisco routers (Linksys doesn’t count) you could setup ‘tunnels’ between the networks and then you could monitor all your devices on your home network. I use tunnels all over my network to enable remote monitoring.
There is no way for Dude to understand what devices are behind a NAT…
This is not completely true if the device preforming the NAT is a RouterOS device.
You can run dude the server on it. The router would then act much like a proxy to the NATed area of the visible network.
If in this case the Dude source IP was say 64.0.0.2, then it could be done by a simple routing statement without runing Dude on the router.
Many people who use the MT products are making IPSs and as such could have multiple public subnets as well.
It is possible to route (not just NAT) between public and private IPs. You do need to use care however.
Are you:
A) trying to connect over the “entire” internet,
or
b) are you on the other side of a NAT in a network that you control?
If A then use the Dude server if you can.
If B then use routing to handle the issue.