Export to GitHub

paping - issue #4

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


Posted on Oct 6, 2010 by Helpful Cat

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

Comment #1

Posted on Apr 21, 2011 by Helpful Bear

(No comment was entered for this change.)

Comment #2

Posted on Apr 21, 2011 by Helpful Bear

(No comment was entered for this change.)

Status: Fixed

Labels:
Type-Defect Priority-Medium