gary109 / paping Goto Github PK

paping is awsome, thanks!

Using it on Windows7 64 bit and I notice that after the last ping result is 
displayed there is a delay of 1 second? before the stats are displayed.

Whilst this isn't the end of the world I want to use paping in a script that 
scans 400 plus devices to make sure a port is still open and 400 x 1 second 
extra delays all adds up :)

Keep up the good work!

Thanks,
Andy.

Hi there,

It would be nice to include my localization I've posted on 
https://code.google.com/p/paping/wiki/Translation#Ukrainian_translation

What steps will reproduce the problem?
1. ./paping -p 3306 -c 12 -t 5000 192.168.20.188

What is the expected output? What do you see instead?
I would spect 12 invocations separated 5 sec each
I see the fist invocation at 5 sec, then 1 invocation each second

What version of the product are you using? On what operating system?
1.55 linux

Please provide any additional information below.

Maybe I am doing something wrong.  If so I'd love to know.  Didn't have time to 
investigate further but I'd be happy to run it on my machine for you with some 
debug flags.


What steps will reproduce the problem?
1. Compiled on OS X (10.7.3) using the 64-bit line in the makefile (commented 
the other one out)
2. Ran following command:

{{{
$ ./x86-64-paping www.google.com -p 80 -c 5
}}}

3. Got the following result:
{{{
paping v1.5.5 - Copyright (c) 2013 Mike Lovell

Connecting to www.google.com on TCP 80:

Connection timed out
Connection timed out
Connection timed out
Connection timed out
Connection timed out

Connection statistics:
    Attempted = 5, Connected = 0, Failed = 5 (100.00%)
Approximate connection times:
    Minimum = 0.00ms, Maximum = 0.00ms, Average = 0.00ms
}}}

Please provide any additional information below.

{{{
$ uname -a
Darwin basillamus.local 11.3.0 Darwin Kernel Version 11.3.0: Thu Jan 12 
18:47:41 PST 2012; root:xnu-1699.24.23~1/RELEASE_X86_64 x86_64
}}}

What steps will reproduce the problem?
1. Downloaded paping_1.5.5_x86-64_windows.zip from the Downloads page.
2. Extracted.
3. Ran paping.exe
4. Received paping.exe - System Error: The program can't start because 
MSVCP100D.dll is missing from your computer. Try reinstalling the program to 
fix the problem.

What is the expected output? What do you see instead?

Expected output: Usage/command-line arguments help for paping.exe
Actual output: Windows error specified above.

What version of the product are you using? On what operating system?

Product version: Windows 7 64-bit binary.
OS: Windows 7 64-bit

Please provide any additional information below.

It would appear that the 64-bit Windows binary currently available from the 
Downloads page has been compiled in Debug instead of Release mode.

Apologies if this isn't the right place for a feature request.

It would be extra helpful if there could be a switch to prepend each line of 
output with a time / date stamp. 

Example usage:I have an erratic connection with an as yet unreproducible fault 
- I want to leave paping running overnight, with the output piped to a file - 
that I can inspect the next day and check when the connectivity fault arose / 
went away..

thanks

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.

[Enhance request]

Would it be lovely for me if:

#paping IP/name

just tried to standard PING.

Maybe you can consider this in the future.

Thanks for a great software, it is really useful!
Rgds, Konrad

Can an option be provided so that size of packet can be specified (to test for 
MTU size constraints)?

What steps will reproduce the problem?
1. Download paping_1.5.1_x86-64_windows.zip
2. Unzip it
3. Run paping.exe

What is the expected output? What do you see instead?
System error: The program can't start becasue MSVCP100D.dll is missing ... 

What version of the product are you using? On what operating system?
1.5.1 x86-64  on Windows 7 Enterprise - 64 bit

Please provide any additional information below.

N/A - as above

i am using paping_1.5.5_x86_windows in windows xp sp3.

How to set this command?

-c N (option ping delay time from 1 second to 30 second)

and

time stamps....

and also

output log file

What steps will reproduce the problem?
1. Query a port on localhost that is closed but not filtered.
2. Use tcpdump or similar to observe returning RST messages
3. Note that the output of the tool does not reflect that a packet was 
returned, but instead reports a timeout.

What is the expected output? What do you see instead?

When a port is closed and the remote system responds to the connection request 
with an RST packet, the output should indicate the fact that a response was 
received despite the port being closed. "Connection timed out" implies that no 
response was generated and that the host may be down/firewalled.

$ ./x86-64-paping -p 65000 -c 4 localhost
paping v1.5.5 - Copyright (c) 2015 Mike Lovell

Connecting to localhost on TCP 65000:

Connection timed out
Connection timed out
Connection timed out
Connection timed out

Connection statistics:
    Attempted = 4, Connected = 0, Failed = 4 (100.00%)
Approximate connection times:
    Minimum = 0.00ms, Maximum = 0.00ms, Average = 0.00ms


tcpdump output -----------------

09:44:44.860355 IP 127.0.0.1.54156 > 127.0.0.1.65000: Flags [S], seq 
3122841057, win 43690, options [mss 65495,sackOK,TS val 945914219 ecr 0,nop,0
09:44:44.860369 IP 127.0.0.1.65000 > 127.0.0.1.54156: Flags [R.], seq 0, ack 
3122841058, win 0, length 0
09:44:45.860618 IP 127.0.0.1.54158 > 127.0.0.1.65000: Flags [S], seq 
1915727314, win 43690, options [mss 65495,sackOK,TS val 945914469 ecr 0,nop,0
09:44:45.860644 IP 127.0.0.1.65000 > 127.0.0.1.54158: Flags [R.], seq 0, ack 
1915727315, win 0, length 0
09:44:46.860954 IP 127.0.0.1.54159 > 127.0.0.1.65000: Flags [S], seq 
4105729788, win 43690, options [mss 65495,sackOK,TS val 945914719 ecr 0,nop,0
09:44:46.860981 IP 127.0.0.1.65000 > 127.0.0.1.54159: Flags [R.], seq 0, ack 
4105729789, win 0, length 0
09:44:47.861281 IP 127.0.0.1.54160 > 127.0.0.1.65000: Flags [S], seq 
4161817225, win 43690, options [mss 65495,sackOK,TS val 945914969 ecr 0,nop,0
09:44:47.861311 IP 127.0.0.1.65000 > 127.0.0.1.54160: Flags [R.], seq 0, ack 
4161817226, win 0, length 0



What version of the product are you using? On what operating system?
v1.5.5 x64 linux

Please provide any additional information below.

What steps will reproduce the problem?
1. downloaded 1.5.1 x86 windows
2. unzipped
3. ran install

What is the expected output? What do you see instead?
cmd window opens, then new window opens: Failed to start because MSVCP100D.dll 
could not be found.

What version of the product are you using? On what operating system?
1.5.1 on XP SP2
I'm on a corporate image, so SP level is not up to me.

Please add source IP or interface binding

What steps will reproduce the problem?
1. cmd
2. paping
3. See how paping doesn't work

What is the expected output? What do you see instead?
Paping can't initiate properly. Error 0xc000007b. Accept to close.

What version of the product are you using? On what operating system?
Paping 1.5.1 on Windows 7 Ultimate.

Please provide any additional information below.

I have copied paping.exe and the 3 dlls needed on c:\windows\system32 but it 
continues not working.

A case was seen where paping reported 0.00ms on a 'problem' connection where it 
would sometimes connect and sometimes not.  I cannot give reproduction details 
because (a) this was performed by a 3rd party and (b) we don't know what is 
wrong the connection.

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
a non-zero time period

What version of the product are you using? On what operating system?
v1.5.5 on Win XP


Please provide any additional information below.

Hi,

Just want to say I was able to build the Linux source for armv71 without issues.

You need to have "build-essential" installed.

After downloading the source you can do:

g++ ./src/print.cpp ./src/stats.cpp ./src/timer.cpp ./src/arguments.cpp 
./src/i18n.cpp ./src/host.cpp ./src/socket.cpp ./src/main.cpp -o ./bin/paping

this will build a working "paping" executable.

What steps will reproduce the problem?
1. paping 0.0.0.0 -p 80
2. paping 0.0.0.0 -p 8080
3.

What is the expected output? What do you see instead?
Expected it to fail as address doesn't exist
Instead the ping was successful for both 80 and 8080. Other ports fail as 
expected

What version of the product are you using? On what operating system?
Windows XP

Please provide any additional information below.
Seems to do it for port 81 as well

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

C:\>paping.exe" www.google.com -p 1234 --udp -c 4

Connecting to www.l.google.com [72.14.204.103] on 1234/udp:
Connected to 72.14.204.103: time=0ms protocol=udp port=1234
Connected to 72.14.204.103: time=0ms protocol=udp port=1234
Connected to 72.14.204.103: time=0ms protocol=udp port=1234
Connected to 72.14.204.103: time=0ms protocol=udp port=1234

Connection statistics for 72.14.204.103 1234/udp:
        Connections: Total = 4, Succeeded = 4, Failed = 0 (0% failure)
Approximate connection times in milli-seconds:
        Minimum = 0ms, Maximum = 0ms, Average = 0ms

What steps will reproduce the problem?
1. Download paping.
2. Create a batch file that runs paping and checks %ERRORLEVEL% environnment 
variable.
3. Run the batch file and see that %ERRORLEVEL% is always 0, no matter if the 
ping wast successful or not.

What is the expected output? What do you see instead?
I expected paping to set %ERRORLEVEL% in the same manner ping.exe does (0 if 
ping successful, 1 if "request timed out or other error).

What version of the product are you using? On what operating system?
paping 1.5.1 x86, Windows 7 Professional

Please provide any additional information below.

Batch file example:

paping google.com -p 80 -c 4
goto %ERRORLEVEL%
:0
@echo Ping successful!
goto:eof
:1
@echo Ping error!
goto:eof

What steps will reproduce the problem?
1. ping a server with connection drops (socket timeouts)
2. take a look at the averages
3.

What is the expected output? What do you see instead?

$ paping news.php.net -p 119 -c 10
paping v1.5.5 - Copyright (c) 2011 Mike Lovell

Connecting to pair1.php.net [76.75.200.58] on TCP 119:

Connected to 76.75.200.58: time=114.25ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.37ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.92ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=113.53ms protocol=TCP port=119
Connection timed out
Connected to 76.75.200.58: time=115.17ms protocol=TCP port=119
Connection timed out

Connection statistics:
    Attempted = 10, Connected = 5, Failed = 5 (50.00%)
Approximate connection times:
    Minimum = 113.37ms, Maximum = 115.17ms, Average = 57.02ms

The average is below the minimum. That should not happen in my universe ;)

What version of the product are you using? On what operating system?
Fedora Linux 20, x86_64

Please provide any additional information below.
Lots of TCP retransmission (seems to be a level3 problem).

What steps will reproduce the problem?
1. download the zip file
2. extract it
3. execute the exe file (paping.exe)

What is the expected output? What do you see instead?
Expected options or some help screen, but got an error says "The application 
was unable to start correctly(0xc000007b). Click OK to close the application."

What version of the product are you using? On what operating system?
paping_1.5.5_x86-64_windows on Windows 7 Pro SP1 x64

Please provide any additional information below.