On Tue, Jul 17, 2018 at 3:59 PM, Corinna Vinschen wrote: > On Jul 17 19:41, Takashi Yano wrote: >> On Mon, 16 Jul 2018 16:14:46 +0900 >> Takashi Yano wrote: >> > ping/ping6 in inetutils also require administrator right as well. >> >> I have noticed that current ping package, as well as ping/ping6 in >> inetutils, works without administrator privilege in Windows 10. >> >> It seems that the policy of raw socket access has been changed in >> Windows 10. > > Indeed! Wow. I just checked and apparently this has been implemented > mainly for WSL, already since build 14926. > > The remaining problem is that we still have non-W10 users. > > So I think the right thing to do is to keep ping in a separate package. > > Marco, the ping you're maintaining isn't IPv6 capable, as far as I can > see.
surely not. it is the ancient 1983 version https://en.wikipedia.org/wiki/Ping_(networking_utility) that is lacking a lot of features compared to most recent ones > Marco and Takashi, what about using ping/ping6 from inetutils but > providing them in a ping package on their own? Would you mind to > discuss this between the two of you? Whatever you two come up with is > fine with me. I think it is a good idea Regards Marco