lucky13

Group: Members
Posts: 1478
Joined: Feb. 2007 |
 |
Posted: June 04 2008,14:55 |
 |
As already described, it's not a vulnerability. One thing you can do to check on any port to see what's happening is: netstat -anp | grep N where N is the port number. So if N=68, you would get back a line that looks like this: tcp 0 0 0.0.0.0:68 0.0.0.0:* LISTEN (with portnumber and process after LISTEN if you're root)
...and you'll also get back any other network information with "68" in it (which could be a lot if you're connected to a LAN like you are - 192.168.x.x since grep will catch every line with 68).
edited
-------------- "It felt kind of like having a pitbull terrier on my rear end." -- meo (copyright(c)2008, all rights reserved)
|