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
Perhaps someone can find an event on the UDMP that is triggered when iptables are refreshed so that he-ipv6 chains can be restored / regenerated (or perhaps there's a way to inject that interface to be addressed for changes as well as eth8/eth9 when the changes happen, so it's much better integrated and no 'trigger' / artificial update is needed at all)
The text was updated successfully, but these errors were encountered:
Doing some research, it's possible something like the following could monitor the interface(s):
monitor:
ip monitor all all-nsid | xargs -L 1 ./change.sh
change.sh:
#!/bin/bashif [[ $@==*"UP"* ]];thenecho$@echo"Looks like an interface came up!"echo""elif [[ $@==*"DOWN"* ]];thenecho$@echo"Looks like an interface went down!"echo""fi
...but some research would have to be done on what type of events would trigger a re-evaluation and potential re-setup of the ipv6 connection
I may spend more time on this to see if [RULE] events come from the change in firewall when things are modified in the UI, but this is pretty low on my priority list...
Perhaps someone can find an event on the UDMP that is triggered when iptables are refreshed so that he-ipv6 chains can be restored / regenerated (or perhaps there's a way to inject that interface to be addressed for changes as well as eth8/eth9 when the changes happen, so it's much better integrated and no 'trigger' / artificial update is needed at all)
The text was updated successfully, but these errors were encountered: