Commit Graph

100 Commits

Author SHA1 Message Date
sthen
209a2f8568 Lose the fe80::/10 IP restrictions from the sample pf.conf lines for
DHCPv6-PD, it seems some satellite-based internet provider sends PD from
a routable address rather than the usual link-local.

Based on a diff from William Graeber but I tweaked a little (mainly removed
the src addr limit from the outbound rule and use "received-on none" instead,
so that the local machine can send from any address without allowing forwarded
packets).
2023-01-18 19:15:39 +00:00
bket
d94a9ec149 Tweak README
Include information on how to get DHCPv6 working in combination with a
restrictive pf.conf, i.e. when outgoing traffic is filtered.

OK sthen@
2023-01-08 10:01:02 +00:00
ajacoutot
f50fdd748e Stop using the daemon class in @newuser.
If we need to make an exception we can do it and properly document the
reason but by default we should just use the default login class.
rc.d uses daemon or the login class provided in login.conf.d so this has
no impact there.

discussed with sthen@, tb@ and robert@

praying that my grep/sed skills did not break anything and still
believing in portbump :-)
2022-11-08 11:14:43 +00:00
sthen
a98e0e6666 remove rcs IDs in ports that I maintain 2022-03-07 21:36:41 +00:00
sthen
f6538a22d0 update to dhcpcd-9.4.1, test/ok bket@ 2021-10-22 18:28:31 +00:00
stsp
ac067fe6df Fix dhcpcd RB tree route lookup in case overlapping prefixes
with different netmasks exist.
See https://github.com/NetworkConfiguration/dhcpcd/pull/52

ok sthen@
2021-08-30 12:56:05 +00:00
bket
d6ed3cd83e net/dhcpcd - fix rc.d daemon script
OK sthen@
2021-07-11 10:13:24 +00:00
sthen
29aaf49ceb update dhcpcd to a newer git checkout, rolling in the patches, and adding
some improvements for control socket handling with privsep (one specific
thing this fixes is if you run "dhcpcd -U6 badger", i.e. invalid interface
name, previously dhcpcd would not accept any more control connections,
now it works as expected).
2021-07-02 10:33:30 +00:00
sthen
5e8a75c493 dhcpcd port tweaks;
update comments in patches which were committed upstream a while ago
add a note to readme based on a user comment
2021-07-02 10:27:11 +00:00
sthen
97a1af2b79 add portroach marker 2021-03-19 13:27:20 +00:00
sthen
6e16f0a618 remind the user that DHCPv6 (and NDP) require PF rules to pass the traffic
as is not generally the case with v4. pointed out by stsp@
2021-02-21 21:36:30 +00:00
tb
78fa7ab8dc net/dhcpcd: fix a regression introduced in 9.4.0
Once every few minutes dhcpcd prints two lines into /var/log/messages:

dhcpcd[89340]: make_env: Undefined error: 0
dhcpcd[89340]: script_runreason: Undefined error: 0

Apparently OpenBSD allows interfaces with the same priority number whereas
NetBSD doesn't.  This would break the ordering used in the routes tree and
RB-tree insertion would fail.  The upstream fix sets errno to make the log
messages more meaningful and fixes RB-tree insertion. It also plugs a leak
in this error path.

Fix from https://roy.marples.name/archives/dhcpcd-discuss/0003426.html

ok sthen
2021-01-16 23:35:47 +00:00
sthen
ee010c01b7 update to dhcpcd-9.4.0 2020-12-29 15:47:32 +00:00
sthen
01c1578b79 update to dhcpcd-9.3.4 2020-11-28 14:55:29 +00:00
sthen
db9ccee624 dhcpcd: add a couple of upstream patches 2020-11-21 14:33:31 +00:00
sthen
b05eeed48b update to dhcpcd-9.3.3 2020-11-21 14:08:14 +00:00
sthen
4d113a696f update to dhcpcd-9.3.2 2020-11-01 19:35:20 +00:00
sthen
352a6d5977 update to dhcpcd-9.3.1 2020-10-13 10:16:02 +00:00
sthen
9d992ca270 update to dhcpcd-9.3.0 2020-10-05 19:23:10 +00:00
kn
6fa152083e Update to 9.2.0 again with cherry-picked pppoe(4) fix
Reverting to 9.1.4 fixed it for naddy but left it broken for me;  this time
apply the following commit "mak[ing] pppoe(4) interfaces more reliable on
FreeBSD and OpenBSD", fixing dhcpcd in my setup as well.

https://roy.marples.name/cgit/dhcpcd.git/commit/?id=e675d4dde0d865b6ffc7de733623a52852d284ff

Feedback OK sthen
2020-10-02 19:29:32 +00:00
sthen
256640c1fd revert to dhcpcd-9.1.4; 9.2.0 has a problem
https://marc.info/?l=openbsd-ports-cvs&m=159957392321338&w=2
2020-09-08 15:02:32 +00:00
sthen
24ec5370f5 update to dhcpcd-9.2.0 2020-09-07 08:42:55 +00:00
sthen
6cc9779250 switch my maintainer email addresses to my own domain 2020-07-11 22:54:35 +00:00
sthen
449cb8bcb8 update to dhcpcd-9.1.4 2020-07-03 14:28:03 +00:00
sthen
7ff11199ae update to dhcpcd-9.1.2 2020-06-18 10:26:26 +00:00
sthen
9e317abcca update to dhcpcd-9.1.1.
dhcpcd now uses pledge(), there are some articles with findings from the
process that may be of interest to readers:

https://roy.marples.name/blog/capsicum_vs_pledge.html
https://roy.marples.name/blog/capsicum_vs_pledge_part2.html

port change: move the homedir for the @newuser to /var/empty now that
dhcpcd no longer requires files inside the chroot directory.
2020-06-04 13:45:11 +00:00
sthen
dc6d39f88b fix @exec-update warning message in previous. 2020-06-03 20:54:28 +00:00
sthen
c6a2e64155 dhcpcd: warn if the existing _dhcpcd user was created with /var/empty homedir,
this was only the case for 11 days so hopefully not too many people ran into it.
make sure /var/dhcpcd is created for startup.
2020-06-03 12:32:33 +00:00
sthen
5e334b1191 update to dhcpcd-9.0.2 2020-04-21 12:40:59 +00:00
sthen
cf3f822888 update to dhcpcd-9.0.1 2020-04-13 16:12:25 +00:00
sthen
a8beb37c20 dhcpcd: fix plist, spotted by semarie 2020-04-07 17:36:53 +00:00
sthen
31da65a516 Just after dhcpcd started using ND6_PRIV_*_LIFETIME constants(!),
they were moved from a kernel header to src/usr.sbin/rad/rad.h
(ADV_PREFERRED_LIFETIME and ADV_VALID_LIFETIME). Use dhcpcd's own
constants instead. From florian@
2020-04-03 12:20:17 +00:00
sthen
11e62efefa update to dhcpcd-9.0.0, now with privsep 2020-04-02 16:33:19 +00:00
sthen
f82ebac1a6 update to dhcpcd-8.1.6 2020-01-27 20:51:46 +00:00
sthen
140a1eb140 update to dhcpcd-8.1.5 2020-01-03 12:39:25 +00:00
sthen
6ff298ff4a update to dhcpcd-8.1.4 2019-12-21 13:00:49 +00:00
sthen
75bc7c16c1 update to dhcpcd-8.1.3 2019-12-20 12:17:57 +00:00
sthen
e4337acb2f update to dhcpcd-8.1.2 2019-11-13 12:18:09 +00:00
sthen
1896b7ceb2 add upstream commit "Remove 0 sla and 0 prefix means whole prefix" as
benno ran into the problem this fixes. I didn't go for 8.1.0 yet (which
also has this fix), waiting for 8.1.1 before updating.
2019-10-15 21:47:02 +00:00
sthen
59576417b3 update to dhcpcd-8.0.6, including a fix for a potential DoS introduced
in dhcpcd-8.0.3 (post-OpenBSD 6.5)
2019-09-14 21:10:48 +00:00
sthen
4e02828f07 update to dhcpcd-8.0.4 2019-09-04 21:40:54 +00:00
sthen
9a0199959b update to dhcpcd-8.0.3 2019-08-21 21:19:47 +00:00
sthen
b1995c2c4a update to dhcpcd-8.0.2 2019-08-06 18:43:50 +00:00
sthen
c2c03b624a update to dhcpcd-8.0.1 2019-07-25 20:04:17 +00:00
sthen
457680d7da update to dhcpcd-8.0.0 2019-07-24 11:32:01 +00:00
sthen
6eb1c8704c update to dhcpcd-7.2.3 2019-06-26 12:37:58 +00:00
sthen
9c6e9626b9 s/PERMIT_PACKAGE_CDROM/PERMIT_PACKAGE/ and some light whitespace tidying
in ports which I maintain
2019-06-03 16:06:50 +00:00
sthen
7127c699c2 update to dhcpcd-7.2.2, fixes:
DHCP: Ensure dhcp is running on the interface received from
BSD: Link handling has been simplified, however it is expected
that if an interface supports SIOCGIFMEDIA then it reports
the correct link status via route(4) for reliable operations
BPF: ARP filter is more robust
BSD and sun: Validate RTM message lengths
DHCPv6 (security): Fix a potential read overflow with D6_OPTION_PD_EXCLUDE
2019-05-04 21:56:18 +00:00
sthen
482c42f1f2 update to dhcpcd-7.2.1, security fixes:
*  auth: Use consttime_memequal to avoid latency attack
   consttime_memequal is supplied if libc does not support it
   dhcpcd >=6.2 <7.2.1 are vulnerable

*  DHCP: Fix a potential 1 byte read overflow with DHO_OPTSOVERLOADED
   dhcpcd >=4 <7.2.1 are vulnerable

*  DHCPv6: Fix a potential buffer overflow reading NA/TA addresses
   dhcpcd >=7 <7.2.1 are vulnerable
2019-04-26 14:50:06 +00:00
sthen
fac3112f84 update to dhcpcd-7.2.0 2019-04-23 10:52:59 +00:00