You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While blocking IPv6 in this case is a good start, loopback traffic
from internal to internal should never be blocked as some deamons
like squid use it to probe and/or communicate.
`block quick' creates a chain-reaction that requires `pass quick' for
loopback traffic, even though we have non-quick loopback pass rules
below. If `quick' ought to be used, non-quick should be removed
completely, but that is beyond the scope of this fix.
For now, rather pass all IPv6 traffic on the looback device as opposed
to passing all IPv6 traffic with an IPv6 loopback address.
`block quick' creates a chain-reaction that requires `pass quick' for
loopback traffic, even though we have non-quick loopback pass rules
below. If `quick' ought to be used, non-quick should be removed
completely, but that is beyond the scope of this fix.
For now, rather pass all IPv6 traffic on the looback device as opposed
to passing all IPv6 traffic with an IPv6 loopback address.
via: https://forum.opnsense.org/index.php?topic=879.0
The text was updated successfully, but these errors were encountered: