Date: Mon, 01 Aug 2022 08:33:50 +0000 From: bugzilla-noreply@freebsd.org To: net@FreeBSD.org Subject: [Bug 237973] pf: implement egress keyword to simplify rules across different hardware Message-ID: <bug-237973-7501-q9kNEcMmX4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-237973-7501@https.bugs.freebsd.org/bugzilla/> References: <bug-237973-7501@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D237973 --- Comment #14 from Alexander V. Chernikov <melifaro@FreeBSD.org> --- (In reply to Goran Meki=C4=87 from comment #13) Depends on the implementation. The code in the mentioned repository ( https://github.com/mekanix/freebsd-src/commit/afeff25d15b5d16b6402b36de8d61= ee44d229c5b ) sets IFG_EGRESS based on the default route presence. I'm not familiar wit= h PF internals to say what is a clear way here - to maintain an additional inter= nal data structure with the list of interfaces with default route, or leverage = an already existing? machinery for interface groups. What I'm saying is that PF can instantiate subscription to any fib it desir= es and handle default default route changes from that hook. --=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-237973-7501-q9kNEcMmX4>