Hello,
�
Seeing the reactions, I think did not describe my problem good enough. So here
a better problem description.
�
�
An IPV6-device has many IPV6 addresses. Among them temporary addresses and
autogenerated addresses. This partly because of privacy concerns.
�
So if an IPV6-device
On 10 Jul 2020, at 22:37, Ultima wrote:
Hey Kristof,
(It’s already possible to use pf on top of a bridge in
bump-in-the-wire mode. Given the gotchas in that code I **strongly**
recommend people don’t use that functionality.)
Do you mind going into details on the gotchas or providing links?
Hey Kristof,
> (It’s already possible to use pf on top of a bridge in
> bump-in-the-wire mode. Given the gotchas in that code I **strongly**
> recommend people don’t use that functionality.)
>
>
Do you mind going into details on the gotchas or providing links?
Thanks and best regards,
Richard
Please go in detail about this issue on why you would need to filter layer
2.
I see very little benefit to having the ability to filter on layer 2 except
in some very special cases and IPv6 isn't one of them that I'm aware of.
Best regards,
Richard Gallamore
On Fri, Jul 10, 2020 at 10:57 AM
On 10 Jul 2020, at 19:57, l.m.v.br...@xs4all.nl wrote:
Hello,
I am using pfSense, build on top of pf. And of course pfSense/pf is a
terrific firewall, however the world is changing in the direction of
IPV6 and that leads to new issues and related new requirements.
One of the major issues is
