Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
SPIKE kill switch #354
We will probably fail with our openvpn approach. Problem is that client clears out routes if it reaches ping-restart timeout. That is we loose tun device even if openvpn client stays alive:
0/1 10.8.0.1 UGSc 95 0 utun1
Client receives ping-restart timeout from the server. We could ignore it, but that would solve problem only for UDP connections. We could also manage routes ourselves , but this will not work for Darwin. Also it will keep alive sessions on server.
Route management might be an options, but in certain cases (computer restarted) routes might be reapplied and you could loose your kill switch. Also, this will not work for Darwin as our own route management will be clashing with openvpn routes. We cannot have persist tun on darwin.
To track inactivity timeout you should get such clear out report:
Some fw based approach: