Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
GoogleCodeExporter opened this issue Apr 20, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

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
Copy link
Author

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

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

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

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant