bassoonsun
New Around Here
Question regarding the Killswitch with the most recent 3004 versions trying to get a proper understanding of how it functions.
With 3004 on the old Jun-2024 release, the killswitch rules were created before WAN goes up, “to reduce the risks of leaks between WAN going up and VPN connecting” The update in Nov-2024 changed so that the “VPN killswitch will now only be active if the VPN client itself is enabled.”
By doing this change hasn't it increased the risks of leaks between WAN going up and VPN connecting? If so, are their any recommendations to stop this leak risk? Is it at all possible for me as a user to revert to the old function for the killswitch or am I misunderstanding the change?
Would the below script function similarly to a killswitch for all router traffic if the VPN goes down? And would using that script as well as the killswitch at the same time cause a conflict?
A lot of questions appreciate any input.
With 3004 on the old Jun-2024 release, the killswitch rules were created before WAN goes up, “to reduce the risks of leaks between WAN going up and VPN connecting” The update in Nov-2024 changed so that the “VPN killswitch will now only be active if the VPN client itself is enabled.”
By doing this change hasn't it increased the risks of leaks between WAN going up and VPN connecting? If so, are their any recommendations to stop this leak risk? Is it at all possible for me as a user to revert to the old function for the killswitch or am I misunderstanding the change?
Would the below script function similarly to a killswitch for all router traffic if the VPN goes down? And would using that script as well as the killswitch at the same time cause a conflict?
Code:#!/bin/sh WAN_IF="$1" iptables -I FORWARD -o $WAN_IF -j REJECT
A lot of questions appreciate any input.
Last edited: