<feed xmlns='http://www.w3.org/2005/Atom'>
<title>wireguard-openbsd/sbin/ping, branch jd/simplify-queueing</title>
<subtitle>WireGuard implementation for the OpenBSD kernel</subtitle>
<id>https://git.zx2c4.com/wireguard-openbsd/atom/sbin/ping?h=jd%2Fsimplify-queueing</id>
<link rel='self' href='https://git.zx2c4.com/wireguard-openbsd/atom/sbin/ping?h=jd%2Fsimplify-queueing'/>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/'/>
<updated>2020-02-11T18:41:39Z</updated>
<entry>
<title>Simplify and unify wording for the -I sourceaddr option in various places.</title>
<updated>2020-02-11T18:41:39Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2020-02-11T18:41:39Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=7081304181fbabfd45e7ed5f2df223bbe61bb1aa'/>
<id>urn:sha1:7081304181fbabfd45e7ed5f2df223bbe61bb1aa</id>
<content type='text'>
This is somewhat related to the "-b bind_addr" option some programs have,
which should get some cleanup also...
input florian claudio jmc
</content>
</entry>
<entry>
<title>ping(8): improve "-i wait" parsing and error-checking code</title>
<updated>2020-01-04T01:00:18Z</updated>
<author>
<name>cheloha</name>
<email>cheloha@openbsd.org</email>
</author>
<published>2020-01-04T01:00:18Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=ee30f25344610b48a00f41b4295304aea963b5dc'/>
<id>urn:sha1:ee30f25344610b48a00f41b4295304aea963b5dc</id>
<content type='text'>
 - 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@
</content>
</entry>
<entry>
<title>At startup, unveil entire filesystem to read-only. If after privdrop, some</title>
<updated>2019-08-28T20:03:51Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-08-28T20:03:51Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=115bfdf815fc2d6ff8ac45f24842ac7a4ee03de4'/>
<id>urn:sha1:115bfdf815fc2d6ff8ac45f24842ac7a4ee03de4</id>
<content type='text'>
implausible bug existed in the socket setup (mostly dns-related and
setsockopt) it would be largely neutered.  of course, a very restrictive
pledge is installed soon after that...
ok mestre brynet florian
</content>
</entry>
<entry>
<title>ping(8): don't round inter-packet delay up to HZ</title>
<updated>2019-07-20T00:49:54Z</updated>
<author>
<name>cheloha</name>
<email>cheloha@openbsd.org</email>
</author>
<published>2019-07-20T00:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=557c6584f16d9dcac62ebf63aeb273c5fd29d737'/>
<id>urn:sha1:557c6584f16d9dcac62ebf63aeb273c5fd29d737</id>
<content type='text'>
ping(8) doesn't know the value of HZ and shouldn't round the user's
packet wait up to whatever it thinks HZ is.  If the period is too small
the interrupt will simply fire less often than instructed.  The kernel
will do the right thing regardless.

Given the rarity of this usage we don't really need to print a warning,
either.

ok millert@
</content>
</entry>
<entry>
<title>When system calls indicate an error they return -1, not some arbitrary</title>
<updated>2019-06-28T13:32:41Z</updated>
<author>
<name>deraadt</name>
<email>deraadt@openbsd.org</email>
</author>
<published>2019-06-28T13:32:41Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=df69c215c7c66baf660f3f65414fd34796c96152'/>
<id>urn:sha1:df69c215c7c66baf660f3f65414fd34796c96152</id>
<content type='text'>
value &lt; 0.  errno is only updated in this case.  Change all (most?)
callers of syscalls to follow this better, and let's see if this strictness
helps us in the future.
</content>
</entry>
<entry>
<title>delay dropping privs a bit when root so that setrtable works.</title>
<updated>2019-03-19T23:27:49Z</updated>
<author>
<name>tedu</name>
<email>tedu@openbsd.org</email>
</author>
<published>2019-03-19T23:27:49Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=c255d9b662e5f108221bc56547af8f68c9212b7e'/>
<id>urn:sha1:c255d9b662e5f108221bc56547af8f68c9212b7e</id>
<content type='text'>
traceroute bits from benno.
ok benno claudio
</content>
</entry>
<entry>
<title>Fix previous, which broke ping -T.</title>
<updated>2018-11-13T14:30:36Z</updated>
<author>
<name>dhill</name>
<email>dhill@openbsd.org</email>
</author>
<published>2018-11-13T14:30:36Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=6669aa477925f34e7ea891bfbc3651d339d8b58c'/>
<id>urn:sha1:6669aa477925f34e7ea891bfbc3651d339d8b58c</id>
<content type='text'>
ok dlg@
</content>
</entry>
<entry>
<title>make all the setsockopt calls consistent.</title>
<updated>2018-11-11T01:40:31Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2018-11-11T01:40:31Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=a77265aeeb35dd4476e022084689245099db2140'/>
<id>urn:sha1:a77265aeeb35dd4476e022084689245099db2140</id>
<content type='text'>
do not cast the arguments unnecessarily, and always err() on failure.

an earlier diff just tweaking the v6 calls was oked by bluhm@ kn@ deraadt@
</content>
</entry>
<entry>
<title>let -D work on ping6 too.</title>
<updated>2018-11-10T23:44:53Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2018-11-10T23:44:53Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=113b2bd5773e3877a5b2ea63ea1f1a545e07c8cd'/>
<id>urn:sha1:113b2bd5773e3877a5b2ea63ea1f1a545e07c8cd</id>
<content type='text'>
the manpage was discussed with many
</content>
</entry>
<entry>
<title>add support for setting the traffic class on ipv6 packets.</title>
<updated>2018-11-10T05:03:23Z</updated>
<author>
<name>dlg</name>
<email>dlg@openbsd.org</email>
</author>
<published>2018-11-10T05:03:23Z</published>
<link rel='alternate' type='text/html' href='https://git.zx2c4.com/wireguard-openbsd/commit/?id=73ce99fb33cdab213019b4b2ada628f6cc0283f0'/>
<id>urn:sha1:73ce99fb33cdab213019b4b2ada628f6cc0283f0</id>
<content type='text'>
it reuses the toskeyword handling that ipv4 uses for setting the
tos field, which is equiavlent to traffic class.

ok florian@ denis@
</content>
</entry>
</feed>
