[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2025-01-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Mark Linimon changed: What|Removed |Added Assignee|n...@freebsd.org |bugmeis...@freebsd.org

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2024-10-02 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Mark Linimon changed: What|Removed |Added Flags|mfc-stable12?, | |mfc-stable11?

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-12 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #25 from Goran Mekić --- I created a port for egress-monitor in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=267731 so please take any discussion about that port to that PR. -- You are receiving this mail because: You are

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #24 from Goran Mekić --- I was missing one USES=uidfix, so that's sorted out, and I did create service file for it, but before I submit the port I want the "initial scan" implemented and that is: get the current default route an

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #23 from d...@rabson.org --- For the root account problem, it looks like bsd.prog.mk always specifies root user. I guess you could workaround by overriding do-install in the port? -- You are receiving this mail because: You are

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #22 from Goran Mekić --- I created a port in https://github.com/mekanix/freebsd-ports/tree/port/egress-monitor but it compiles only if you use root account. If anyone knows how to fix that I would be grateful. For now you can tr

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-11-11 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 d...@rabson.org changed: What|Removed |Added CC||d...@rabson.org --- Comment #21 f

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #20 from Goran Mekić --- Initial version: https://github.com/mekanix/egress-monitor I found in ifconfig (https://github.com/freebsd/freebsd-src/blob/main/sbin/ifconfig/ifgroup.c#L60) that group name should not end in a digit, s

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #19 from Alexander V. Chernikov --- (In reply to Goran Mekić from comment #18) The rest is the prefix information, in sockaddr form. Basically, rtm_addrs contains a bitmask of sockaddrs available, and these remaining bytes are

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Goran Mekić changed: What|Removed |Added Attachment #235606|text/x-csrc |text/plain mime type|

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #17 from Goran Mekić --- (In reply to Alexander V. Chernikov from comment #16) I didn't know you can subscribe from userspace, too. In that case, yes, my patch is completely wrong. I have to do some research now before I write n

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #16 from Alexander V. Chernikov --- (In reply to Goran Mekić from comment #15) IIRC ipfw doesn't do anything with the groups. It does have interface tracker, which is used to maintain efficient lookup for interface-name tables.

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #15 from Goran Mekić --- (In reply to Alexander V. Chernikov from comment #14) Continuing on what you wrote, I can see PF implementing something internal, then IPFW doing similar and we end up with a need for common implementati

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #14 from Alexander V. Chernikov --- (In reply to Goran Mekić from comment #13) Depends on the implementation. The code in the mentioned repository ( https://github.com/mekanix/freebsd-src/commit/afeff25d15b5d16b6402b36de8d61ee44

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #13 from Goran Mekić --- (In reply to Alexander V. Chernikov from comment #12) I'm curious about 1. Does that mean if_addgroup() would be removed altogether and PF would handle egress internally? -- You are receiving this mail

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Alexander V. Chernikov changed: What|Removed |Added CC||melif...@freebsd.org ---

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-08-01 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 --- Comment #11 from Goran Mekić --- (In reply to Zhenlei Huang from comment #10) It is complex and I just started learning about routing implementation in kernel, so this patch is far from perfect, but let me give some of the answers: 1.

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-07-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Zhenlei Huang changed: What|Removed |Added CC||zlei.hu...@gmail.com --- Comment #

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-07-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Goran Mekić changed: What|Removed |Added CC||meka@tilda.center --- Comment #9 fro

[Bug 237973] pf: implement egress keyword to simplify rules across different hardware

2022-05-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237973 Kristof Provost changed: What|Removed |Added Assignee|p...@freebsd.org |n...@freebsd.org --- Comment #