wireguard-openbsd/sbin/ping/ping.8, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sbin/ping/ping.8?h=jd%2Fqueueboosts2020-02-11T18:41:39ZSimplify and unify wording for the -I sourceaddr option in various places.2020-02-11T18:41:39Zderaadtderaadt@openbsd.org2020-02-11T18:41:39Zurn:sha1:7081304181fbabfd45e7ed5f2df223bbe61bb1aa
This is somewhat related to the "-b bind_addr" option some programs have,
which should get some cleanup also...
input florian claudio jmc
ping(8): improve "-i wait" parsing and error-checking code2020-01-04T01:00:18Zchelohacheloha@openbsd.org2020-01-04T01:00:18Zurn:sha1:ee30f25344610b48a00f41b4295304aea963b5dc
- Never accept negative values.
- Cap the interval at UINT_MAX seconds to avoid strange rounding
behavior at the end of the input range.
- Use error messages that resemble other parts of the tree where we
are able to use strtonum(3).
- Leverage modf(3) for cleaner code.
- Call it "-i interval" to avoid accidental visual similarity to
"-w maxwait".
With input from cjeker@, kettenis@, kn@.
ok kn@
let -D work on ping6 too.2018-11-10T23:44:53Zdlgdlg@openbsd.org2018-11-10T23:44:53Zurn:sha1:113b2bd5773e3877a5b2ea63ea1f1a545e07c8cd
the manpage was discussed with many
add support for setting the traffic class on ipv6 packets.2018-11-10T05:03:23Zdlgdlg@openbsd.org2018-11-10T05:03:23Zurn:sha1:73ce99fb33cdab213019b4b2ada628f6cc0283f0
it reuses the toskeyword handling that ipv4 uses for setting the
tos field, which is equiavlent to traffic class.
ok florian@ denis@
in florian;s last commit i urged him to change "twenty-four" to2016-10-26T16:18:45Zjmcjmc@openbsd.org2016-10-26T16:18:45Zurn:sha1:fe5882cf0967af9221f09488609ca0bf79161053
"twenty four", arguing, i think, that the internet is wrong; well
seemingly i'm wrong, and you should hyphenate numbers when spelled out
- who'd have thought it. apologies to florian and the diff submitter
(and the internet);
still, what i should have advised, and what i've done here, is use "24",
which is much simpler, fits the surrounding text, and agrees with oed
style advice;
Due to 64 bit seconds + 64 bit nano seconds resolution and the2016-10-26T14:06:05Zflorianflorian@openbsd.org2016-10-26T14:06:05Zurn:sha1:1fef22de7849cbda2f6139184893838f6042aabd
addition of a MAC we need at least 24 bytes packet size these days to
show timing information.
Pointed out by Tamas Horvath, thanks!
OK jmc
various cleanup; ok florian2016-09-20T12:32:35Zjmcjmc@openbsd.org2016-09-20T12:32:35Zurn:sha1:ed96f4df755f6ecd6fa6519c8b220abeb5747c1cminor tweaks;2016-09-18T10:20:21Zjmcjmc@openbsd.org2016-09-18T10:20:21Zurn:sha1:94c37e73b986cec62c7c90d20f0a13ff59e3cd64Merge ping6(8) manual into ping(8).2016-09-17T18:36:15Zflorianflorian@openbsd.org2016-09-17T18:36:15Zurn:sha1:83f4a66a1bac9e606ee7f0bfcf223600e8d53704
Tweak & OK jmc@
Mention the maximum value for the -s option.2016-09-03T13:56:17Zakfaewakfaew@openbsd.org2016-09-03T13:56:17Zurn:sha1:40507cd53a5e41d5d8c639b5dc1fd907b1effeae
OK tedu@ jmc@