It is a core module, and the latest version (bundled w/perl) is 2.38, although CPAN shows 2.36. Perhaps it is no longer maintained individually and change requests should go to P5P?

Let see, the Net::Ping docs still says report bugs to RT, but the module isn't in http://perl5.git.perl.org/perl.git/tree/HEAD:/cpan/Net-Ping but it is in http://perl5.git.perl.org/perl.git/tree/HEAD:/dist/Net-Ping

perlsource#Core modules only says that modules in /cpan/ should use individual RT bugtrackers, it kinda looks like it implies reports for /dist/Net-Ping should go to perlbug/p5p

I must admit I'm a casual Perl user despite having a few CPAN modules and writing a (perhaps questionable) patch. I'm not familiar with the bug reporting other than CPAN RT. I do appreciate your advice and I did get a BitCard account and report the "wishlist" with 'perlbug'. We'll see what comes from that.

Thanks again for the direction!

Sorry to see no progress. Perhaps this will help (I added it to the CPAN bug report):

With respect to the questions about the patch:

A quick search turns up the source for ping6 at http://cvsweb.netbsd.org/bsdweb.cgi/src/sbin/ping6/ping6.c?rev=1.81&content-type=text/x-cvsweb-markup&only_with_tag=MAIN

Checksum:

The header checksum field is initialized to zero, but not computed - I assume (but haven't dug in) that sendmsg computes.

Source address:

When no explicit interface is bound, the source address is determined by indirectly consulting the routing tables - a UDP socket is connect()ed and getsockname() called. Look for the code under if (!(options & F_SRCADDR))

Hope this helps.

This communication may not represent my employer's views, if any, on the matters discussed.