Date: Fri, 26 Mar 2021 20:17:14 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 254587] net/wireguard: pf fail starting on every boot Message-ID: <bug-254587-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254587 Bug ID: 254587 Summary: net/wireguard: pf fail starting on every boot Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: decke@FreeBSD.org Reporter: victor_volpe@bol.com.br Assignee: decke@FreeBSD.org Flags: maintainer-feedback?(decke@FreeBSD.org) After this update, my NAT rules based on wg0 interface, are no longer goin= g up on boot. I need to manually start the pf after. Even with wireguard-kmod removed, it not behaves as before! It seems that now pf initializes before wireguard, or something else. There is no test routines before releasing an= big updates like this? Jeez! root@home:~ # cat /etc/pf.conf nat on wg0 from 192.168.15.0/24 to { 192.168.111.0/24, 10.0.0.0/24 } -> wg0 root@home:~ # cat /etc/rc.conf wireguard_enable=3D"YES" wireguard_interfaces=3D"wg0" gateway_enable=3D"YES" pf_enable=3D"YES" pf_rules=3D"/etc/pf.conf" pflog_enable=3D"YES" pflog_logfile=3D"/var/log/pflog" --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254587-7788>