wireguard-openbsd/sbin/pfctl, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sbin/pfctl?h=jd%2Fqueueboosts2020-05-15T00:56:03Zpf(4): use CLOCK_BOOTTIME to get time_uptime(9) in userspace2020-05-15T00:56:03Zchelohacheloha@openbsd.org2020-05-15T00:56:03Zurn:sha1:e45b97acc68240287380c19ce0d763926c796dbd
In pf(4), the pf_status.since timestamp is set with time_uptime(9).
This is a low-res snapshot of nanouptime(9). nanouptime(9) is used to
implement CLOCK_BOOTTIME for clock_gettime(2). It is not used to
implement CLOCK_UPTIME, though. The names are misleading.
Switch to CLOCK_BOOTTIME in places in userspace where we use
pf_status.since so we are working with the right clock.
Technically CLOCK_MONOTONIC is equivalent, but we shouldn't use that
here. CLOCK_MONOTONIC is not necessarily the "time since boot": the
standard says its absolute value is meaningless.
ok patrick@ bluhm@
sbin/pfctl: replace TAILQ concatenation loop with TAILQ_CONCAT2020-01-28T15:40:35Zbketbket@openbsd.org2020-01-28T15:40:35Zurn:sha1:c8d5c2349e3f227bad1d2f5dc86738410c5de33e
OK kn@, sashan@, florian@
Fail on missing anchor2020-01-16T01:02:20Zknkn@openbsd.org2020-01-16T01:02:20Zurn:sha1:ad846651a1e57f4044de08e014c62f6c17306af2
There is no reason to continue on anchor specific paths if the given
anchor does not exist.
OK sashan
Do the actual pfr_strerror() to pf_strerror() rename2020-01-15T22:38:30Zknkn@openbsd.org2020-01-15T22:38:30Zurn:sha1:c802a0d9d6a6510e658984688f179f6777ccfce2
Missed in previous
Unify error message for nonexisting anchors2020-01-15T22:31:51Zknkn@openbsd.org2020-01-15T22:31:51Zurn:sha1:e5c920154c2024677fa8b335bbe529eaa6a4e705
pf(4) returns EINVAL for DIOCGETRULE, DIOCGETRULES and DIOCGETRULESET if
the specified anchor does not exist.
Extend and rename {pfr -> pf}_strerror() to make error message more
consistent.
There are other occasions as well but those need additional tweaks;
that's stuff for another diff.
OK and rename from sashan
Refine error message2020-01-15T16:15:08Zknkn@openbsd.org2020-01-15T16:15:08Zurn:sha1:910e8feeb52b5a134ad07406c9ff19ac9dbff7df
While code in pf/pfctl confusingly uses either anchor or ruleset
depending on the context, pfctl(8) (both manual and user interface)
should be consistent.
For users there are basically anchors only, so do not imply any
difference between the two terminologies.
OK sashan
Merge radix_perror() into simpler warnx()/errx() usage2020-01-15T15:45:49Zknkn@openbsd.org2020-01-15T15:45:49Zurn:sha1:e13f0105288f304d66f03ce19d6424ba30482f36
Less nesting for clearer code.
OK sashan
Further document recursive flush behaviour2020-01-15T14:39:41Zknkn@openbsd.org2020-01-15T14:39:41Zurn:sha1:5bd1c2906f9ebf166bab4aced5322a2716895dc2
OK sashan
Print the main ruleset/anchor as "/" not "<root>" for consistency2020-01-15T13:42:39Zknkn@openbsd.org2020-01-15T13:42:39Zurn:sha1:baa66dbe09e9b06485965f736a81919fb26ad31d
OK sashan
Recent change to pfctl(8) prompts for a minor update of manpage.2020-01-15T13:42:38Zsashansashan@openbsd.org2020-01-15T13:42:38Zurn:sha1:7abd52e24aa543084f527e1a8cd127a1a51bbd82
OK kn@