morgan-greywolf/paping

Issues

• Wrong average time calculation on connection timeouts

  #19 opened 9 years ago by GoogleCodeExporter
  1

• Delay after last ping

  #8 opened 9 years ago by GoogleCodeExporter
  0

• Packet size option

  #13 opened 9 years ago by GoogleCodeExporter
  0

• Time Stamps

  #7 opened 9 years ago by GoogleCodeExporter
  2

• Ukrainian localization

  #15 opened 9 years ago by GoogleCodeExporter
  0

• Option ping time and time stamps

  #16 opened 9 years ago by GoogleCodeExporter
  0

• The application was unable to start correctly

  #14 opened 9 years ago by GoogleCodeExporter
  2

• port 80 and 8080 always successful

  #9 opened 9 years ago by GoogleCodeExporter
  1

• Fature Request: Bind source IP or interface

  #21 opened 9 years ago by GoogleCodeExporter
  0

• Build system sucks.

  #23 opened 9 years ago by morgan-greywolf
  1

• Does not work on OS X

  #17 opened 9 years ago by GoogleCodeExporter
  4

• Run without any options - just the ip/name

  #20 opened 9 years ago by GoogleCodeExporter
  0

• Incorrectly reports "Connection timed out" when querying a closed port

  #22 opened 9 years ago by GoogleCodeExporter
  0

• Build for arm from source files

  #18 opened 9 years ago by GoogleCodeExporter
  1

• Windows 7 64-bit Binary Probably Miscompiled in Debug Mode

  #11 opened 9 years ago by GoogleCodeExporter
  3

• Option -t works only first time

  #12 opened 9 years ago by GoogleCodeExporter
  1

• 0.00ms time reported

  #10 opened 9 years ago by GoogleCodeExporter
  2

• paping does not set %ERRORLEVEL%

  #5 opened 9 years ago by GoogleCodeExporter
  3

• Paping can't initiate properly

  #6 opened 9 years ago by GoogleCodeExporter
  1

• paping.exe does not start on Window 7 Enterprise - 64 bit

  #3 opened 9 years ago by GoogleCodeExporter
  1

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

  #4 opened 9 years ago by GoogleCodeExporter
  2

• Missing DLL: MSVCP100D.dll

  #2 opened 9 years ago by GoogleCodeExporter
  39

• UDP port check does not function, it immediately reports a successful connection even if the port is not open

  #1 opened 9 years ago by GoogleCodeExporter
  4