* Atanas Vladimirov <[email protected]> [2026-04-17 15:57]: > and pf.conf I have `set skip on { lo, em0, em1, em2, em3, em4, em5, tap }`
now that I see skip here - the bug with interfaces popping up and interface groups was exactly with set skip on a group not being applied to the member interface popping up. got that detail wrong on my previous mail. > And when I do a `reboot` on the VM, I have to run `pfctl -f /etc/pf.conf` > once the VM is back up so its network works again. well you must have something in your ruleset that resolves differently with and without the interface being present; my bet is on "to tapX" or similar. comparing pfctl -sr (you may need to do that per anchor if you use 'em) and pfctl -sI before and after reloading should point out what. > Do you think that this issue is PF-related or something else is going on? I think it is related to your ruleset and pf is doing exactly what you tell it to ;) -- Henning Brauer, [email protected], [email protected] BS Web Services GmbH, http://bsws.de, Full-Service ISP Secure Hosting, Mail and DNS. Virtual & Dedicated Servers, Root to Fully Managed Henning Brauer Consulting, http://henningbrauer.com/
