Linux with Eddie: startup leak

[kelonigma 1]

Eddie 2.10 on Linux (Debian): I configured Eddie in the settings menu to connect at startup and activate network lock at startup. Unfortunately, I still had to manually add Eddie to my startup applications (maybe this is what's causing my problem).

 

It does start when I turn on my PC, but during the time in between the PC finalizing the booting process and Eddie starting up, network lock does not appear to be active, as my PC already manages to get various internet-dependent info, like the current weather for a widget, before the Eddie client is even open.

 

Is there any way to prevent this short period of startup leak?

[LZ1 662]

Hello!

 

You shouldn't be using 2.10 on Linux. Use 2.11.x. Check my guide if you don't know where it is .

[Staff 9751]

It does start when I turn on my PC, but during the time in between the PC finalizing the booting process and Eddie starting up, network lock does not appear to be active, as my PC already manages to get various internet-dependent info, like the current weather for a widget, before the Eddie client is even open.

 

That's correct and expected: Network Lock is a set of iptables and ip6tables rules enforced when Eddie starts. Such rules are not permanent and on top of that Eddie will explicitly restore previous ip*tables rules when you shut it down.

 

Is there any way to prevent this short period of startup leak?

 

The easiest way is to set proper iptables rules at the very beginning of your init. See also https://airvpn.org/topic/12175-network-lock/

 

Kind regards

[kelonigma 1]

Thanks, this actually seems to work perfectly. I've installed iptables-persistent to load the rules from that thread at boot, and then as soon as the AirVPN client autostarts and applies its own network lock, it overwrites those iptable rules with its own thing and it all works without any leaks (that I could notice).