Note to all:

Please create a fork of the repo https://github.com/gnotaras/python-ping so as to be able to tell what changes you have applied using the above code as a starting point. And then feel free to work on your fork.

This is becoming really confusing for me and I do not have the time to browse through the commits to understand the modifications. This post is about reporting issues and modifications to the _published_ code.

Thank you all for your understanding.

Unfortunately, this post is becoming more and more confusing for readers, since it is cumbersome to diff the code snippets provided in the comments or in any repositories linked from the comments.

So, this is how it will be resolved once and for all.

The code that has been posted above has been uploaded to the following repositories:

1) https://bitbucket.org/gnotaras/python-ping
2) https://github.com/gnotaras/python-ping
3) https://source.codetrax.org/hgroot/python-ping/

Also, a zip archive can be found in the files section of the following development website:

http://www.codetrax.org/projects/python-ping/files

If you have worked on the code that has been published above, it is highly recommended that you fork the repositories at bitbucket/github, commit your changes and then create a pull request. Also, feel free to start working on a specific fork of yours without expecting me to actually pull your changes.

The idea is to have a clear view of what changes have been made to the published code in this post. This way we will all save our free time and things will be generally better.

I found the existing fork [link removed. see note] and merged everything together. Would be great if everyone worked on the same repository.

A idea is to implement a subprocess call ping with a parser of the output, so that no admin right is needed: [link removed. see note]

[MODERATED: Please provide some explanation about where this code derives and what it has to do with the code that has been posted in this post. This is becoming really confusing and I cannot follow. Sorry.]

Currently, I am out of free time and, also, I’m not sure I have the required qualifications for such a task. But it would be an interesting task for the future. Also, there is another python library I’d like to check out at some point, impacket, and also scapy. I am quite certain the latter has support for ICMPV6, but I’ve never checked it out.

PS: Note to self: It is about time I get python 3 installed in my system :)

Yes, there are certainly changes to the code, as well as a more rigorous analysis of the checksum routine. My changes were not Cygwin-specific, it was just a handy version I could readily test against. Other than adding in the “average” ping time what I turned this into is pretty much the same as what the original public domain ping.c does.

Note that @Jens backport *is* the Python 2 version, for those using that (yes, I realize mine may have a more niche audience, though I think it’s always valuable to have a Python 3 version out there as people move forward… which is why I focused on the Python 3 port).

1) it seems you have focused on Python 3, which has not yet been adopted by the majority of users.

2) several changes to the original code have been introduced by your published snippets.

To be honest, despite the fact that Martin has built upon the source code of the ping utility that ships with cygwin, I’d rather stick with the old version for now (published in this post), which has been around for over a decade, until the new changes are reviewed by other users. Unfortunately, I do not have the time or the required expertise to evaluate them. Thanks for your understanding.