I used nmap to scan my router and found this 49152/tcp open upnp Portable SDK for UPnP devices 1.3.1 (Linux 184.108.40.206; UP
The nmap command used was: C:\Users\Admin>nmap -sS -sV -F -n 192.168.1.1
You should go to http://www.grc.com and run their ShieldsUp test on the port. This will tell you if the port is not responding, closed or open. (Green, blue or red status respectively.)
The advantage of using Gibson Research Corporation's test is that it reveals what is happening for unsolicited connections from the Internet. If you make an outgoing connection to a website, typically the destination port of the target website will be port 80 (HTTP), but the source port will be a random high numbered port assigned by the operating system of the originating computer. This might be port 49152. If a packet comes back from the website port 80 to port 49152 on the originating computer, the router will have this port open and mapped to a specific computer and port on the internal network.
To scan for open ports on a router, you cannot do it properly from a computer on the internal network of that router. That is why tests such as the GRC ShieldsUp test or other similar tests coming from the Internet should be used.
I hope this helps.
I believe UPnP allows programs that need it to do dynamic automatic port forwarding, instead or requiring you set port forwarding manually. For example apparently that is required for game consoles, because you often hear people with game consoles trying to figure out how to set "open NAT". Although, I do not know of any PC games that require that. When I run that nmap command on my DSL gateway I get:
PORT STATE SERVICE VERSION
22/tcp open ssh Dropbear sshd 2012.55 (protocol 2.0)
23/tcp open telnet?
53/tcp open domain ISC BIND 9.X
80/tcp open http?
443/tcp open ssl/https?
5000/tcp open upnp MiniUPnP
nmap -O could not determine the actual Linux version of my router, just OS details: Linux 2.6.9 – 2.6.27. I am actually running Linux on my PC, but it is a 64-bit 3.13.0 kernel.
hi so it might be just a history record… as some of these utilities show not only inside use but also invaders… who get no where… so it might not be just the router that is the issue here but what some might call attacks as well…
Hi so it might be just a history record. as some of these utilities show not only inside use but also invaders. who get no where. so it might not be just the router that is the issue here but what some might call attacks as well.
read this, see link