https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #5 from Kristof Provost ---
> Kristof, do you know the code well enough to say if it would be possible to
> deny the initial interface rename action if a parent vnet is using the same
> name?
That runs into the same
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #4 from Thomas Steen Rasmussen / Tykling ---
(In reply to Kristof Provost from comment #3)
Thank you for the input. The issue I was hitting is the first one you mention -
also described in #185619 - and I've been able to work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #3 from Kristof Provost ---
With the disclaimer that this is entirely from memory and may be incorrect or
outdated:
I'm aware of several somewhat related issues around interface naming. One is
this, that when an interface is
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #2 from Thomas Steen Rasmussen / Tykling ---
This statement
- Rebooting with four jails plus the above ruleset enabled means never getting
any contact to the server at all (ie. the problem manifests from boot).
is not true,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
--- Comment #1 from Thomas Steen Rasmussen / Tykling ---
Maybe related https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=185619
Also, I forgot to mention, at some point yesterday while trying 100 things I
saw the em0 on the host having
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=260973
Bug ID: 260973
Summary: pf: firewall rules stop matching when vnet jails share
interface names with the host
Product: Base System
Version: 13.0-STABLE
Hardware: Any
