-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Kill States for Interface #169
Comments
I’m not sure I’ve ever seen that checkbox. If you don’t mind send over a screenshot of what you’re referring to. You can use the pfsense.kill_states service however to implement what I’m assuming is a similar behavior. |
Sure, it is the 'X' on the far right for the first rule in the list below.
I've tried using kill_states, and it works reasonably well for IPv4
traffic...but I haven't been able to find a way to get it to reliably kill
IPv6 traffic (my workaround at the moment is to _only_ allow IPv4 on these
interfaces).
My pfSense version is 2.7.0-RELEASE (amd64)
[image: image.png]
…On Mon, Aug 7, 2023 at 9:00 PM Travis Glenn Hansen ***@***.***> wrote:
I’m not sure I’ve ever seen that checkbox. If you don’t mind send over a
screenshot of what you’re referring to.
You can use the pfsense.kill_states service however to implement what I’m
assuming is a similar behavior.
—
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB4TM6KMXRGYMZ66PQHGHLXUGTTFANCNFSM6AAAAAA3HVXQAI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Looks like the image didn't come through :( |
Interesting, looks like something new in 2.7. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using firewall rules to restrict traffic to/from a specific vlan. However there is a very noticeable lag between enabling/disabling the rule and traffic being blocked. When I toggle the rule via pfsense, I also use the "Kill all states on this interface created by this rule" button to cause it to immediately take effect.
How can I replicate this behavior from the hass-pfsense plugin?
The text was updated successfully, but these errors were encountered: