el_pedr0
Occasional Visitor
It seems to me that the kill switch behaviour in the 386.14_2 version is still of the type described in the changelog:
- Manually stopping a client will remove the kill
switch. It will now only be applied at boot time
(if client was set to start at boot), or if the
tunnel is disconnected through a non-user event
But it sounds like the kill switch for those of you on 388 acts in a much more conservative/cautious manner - ensuring that clients can access the internet *only* via the VPN tunnel, regardless of whether it was a manual user intervention or otherwise.
Have I understood things correctly?
Please, please could you bring across the 388 killswitch behaviour to the 386 stream as one last parting gift before we're left north of the wall?
- Manually stopping a client will remove the kill
switch. It will now only be applied at boot time
(if client was set to start at boot), or if the
tunnel is disconnected through a non-user event
But it sounds like the kill switch for those of you on 388 acts in a much more conservative/cautious manner - ensuring that clients can access the internet *only* via the VPN tunnel, regardless of whether it was a manual user intervention or otherwise.
Have I understood things correctly?
Please, please could you bring across the 388 killswitch behaviour to the 386 stream as one last parting gift before we're left north of the wall?
Last edited:
