After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 547598 - gnome-nettools port scan gives different results every time it is run
gnome-nettools port scan gives different results every time it is run
Status: RESOLVED FIXED
Product: gnome-nettool
Classification: Applications
Component: Tools
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: Germán Poo-Caamaño
Rodrigo Moya
Depends on:
Blocks:
 
 
Reported: 2008-08-13 13:18 UTC by Pedro Villavicencio
Modified: 2012-01-03 04:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Pedro Villavicencio 2008-08-13 13:18:28 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-nettool/+bug/257042

"When running the port scan tool I get different results every time I run it on localhost."

"it seems to find random ports that are not open. I just tried it again and ports
40940 and 50530 showed up this time with niether of the ports showing up in netstat"

"tried the same with nmap and get the right results with gnome-nettool the latest ports are random"

screenshot:

http://launchpadlibrarian.net/16710468/Screenshot.png

Thanks,
Comment 1 Germán Poo-Caamaño 2008-12-03 14:45:15 UTC 
Well, sometimes are not the latest port that looks random.  

Anyway, I also can reproduce it.
Comment 2 mfisch@ubuntu.com 2011-12-05 04:13:36 UTC 
Should we just modify this to use nmap?  nmap is much much faster and gives accurate results.  I can scan ports 1-65535 in 0.57 seconds with nmap on my system.  Using gnome-nettools's algorithm takes much much longer, up to 5 seconds, and it's also not correct.   I'd be happy to switch it with a patch depending on how everyone else feels about this.
Comment 3 Germán Poo-Caamaño 2011-12-05 05:26:25 UTC 
Indeed, patches are welcomed.
Comment 4 Germán Poo-Caamaño 2012-01-03 04:25:01 UTC 
This should be fixed now that we switched to nmap instead of using
local sockets.