Date: Mon, 01 Aug 2022 10:26:56 +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-xzyi5hIIhR@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 #16 from Alexander V. Chernikov <melifaro@FreeBSD.org> --- (In reply to Goran Meki=C4=87 from comment #15) IIRC ipfw doesn't do anything with the groups. It does have interface track= er, which is used to maintain efficient lookup for interface-name tables. Speaking of the grouping - there are many variants of grouping that may take different options into account. For some (bridge, epair) FIB isn't relevant= at all. I'd really prefer to have as little business logic in the kernel as possible and leave it to the applications. For example, nothing stops someone from writing a small rtsock monitor scri= pt that tracks per-fib default route and assigns "egress_fibX" groups to the relevant interfaces. --=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-xzyi5hIIhR>