michaelhagans / paping

Automatically exported from code.google.com/p/paping
MIT License
0 stars 0 forks source link

paping on everyport even though the port is not open in local machine #4

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
paping return success on any port even though nothing is listing on that port 
on local machine.
When I do the same with
#nmap -p 4000 127.0.0.1

output is like this

Starting Nmap 5.00 ( http://nmap.org ) at 2010-10-06 11:33 IST
Interesting ports on DH (127.0.0.1):
PORT     STATE  SERVICE
4000/tcp closed remoteanything

however with paping
#paping 127.0.0.1 -p 400 -c 3

output is like this

paping v1.5.1 - Copyright (c) 2010 Mike Lovell

Connecting to 127.0.0.1 on TCP 400:

Connected to 127.0.0.1: time=0.05ms protocol=TCP port=400
Connected to 127.0.0.1: time=0.09ms protocol=TCP port=400
Connected to 127.0.0.1: time=0.07ms protocol=TCP port=400

Connection statistics:
    Attempted = 3, Connected = 3, Failed = 0 (0.00%)
Approximate connection times:
    Minimum = 0.05ms, Maximum = 0.09ms, Average = 0.07ms

How is it able to connect if nothing is listing on that port

Original issue reported on code.google.com by mrbl...@gmail.com on 6 Oct 2010 at 6:06

GoogleCodeExporter commented 8 years ago

Original comment by pap...@lists.gotinker.com on 21 Apr 2011 at 7:46

GoogleCodeExporter commented 8 years ago

Original comment by pap...@lists.gotinker.com on 21 Apr 2011 at 9:03