Jump to content


Photo

Ubuntu Network Lock Deactivated when Eddie Closed

eddie network-lock ubuntu

  • Please log in to reply
5 replies to this topic

#1 ms1SDR4ppBabRSjrP18H

ms1SDR4ppBabRSjrP18H

    Newbie

  • New Members
  • Pip
  • 1 posts

Posted 12 January 2018 - 10:41 AM

Hi AirVPN forums.

 

I'm using 2.13.6 of Eddie on Ubuntu 16.04 and noticed today that when I close the client (or as happened overnight it crashed) the IPTables firewall rules were reset, and all traffic was allowed!!

 

I definitely only want to allow network traffic when AirVPN is connected.

 

I believe this worked in the past - any suggestions?!

 

Kind regards,

randomusername 



#2 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7022 posts

Posted 12 January 2018 - 05:15 PM

I'm using 2.13.6 of Eddie on Ubuntu 16.04 and noticed today that when I close the client (or as happened overnight it crashed) the IPTables firewall rules were reset, and all traffic was allowed!!

 

 

Hello!

 

iptables rules restored when you close Eddie: intended and expected.

 

When Eddie crashes, we can't see how it can modify iptables rules or do anything else. Network Lock is a set of iptables and ip6tables rules, please feel free to clarify.

 

Kind regards



#3 go558a83nk

go558a83nk

    Advanced Member

  • Members
  • PipPipPip
  • 1351 posts

Posted 12 January 2018 - 07:04 PM

I'm using 2.13.6 of Eddie on Ubuntu 16.04 and noticed today that when I close the client (or as happened overnight it crashed) the IPTables firewall rules were reset, and all traffic was allowed!!

 

 

Hello!

 

iptables rules restored when you close Eddie: intended and expected.

 

When Eddie crashes, we can't see how it can modify iptables rules or do anything else. Network Lock is a set of iptables and ip6tables rules, please feel free to clarify.

 

Kind regards

 

 

I'm running Mint 18.3 (or 18.2 and 18.1 and so on in the past) in a VM and as happens sometimes the Eddie GUI crashes, but openvpn is still running.  I'll just reboot at this point.

 

When I rebooted in the past the network lock rules were still running because Eddie wasn't shut down properly.

 

But, I've noticed lately that network lock rules are not in place upon reboot.

 

Sounds like I'm seeing the same thing as the OP.



#4 Staff

Staff

    Advanced Member

  • Staff
  • PipPipPip
  • 7022 posts

Posted 13 January 2018 - 11:06 AM

But, I've noticed lately that network lock rules are not in place upon reboot.

 

Hello!

 

That's expected and intentional. Eddie does not set "permanent" iptables rules, they will not survive a system reboot.

 

Kind regards



#5 LZ1

LZ1

    It's nice to be nice to nice people

  • Members
  • PipPipPip
  • 1476 posts

Posted 13 January 2018 - 01:10 PM

 

I'm using 2.13.6 of Eddie on Ubuntu 16.04 and noticed today that when I close the client (or as happened overnight it crashed) the IPTables firewall rules were reset, and all traffic was allowed!!

 

 

Hello!

 

iptables rules restored when you close Eddie: intended and expected.

 

When Eddie crashes, we can't see how it can modify iptables rules or do anything else. Network Lock is a set of iptables and ip6tables rules, please feel free to clarify.

 

Kind regards

 

 

I'm running Mint 18.3 (or 18.2 and 18.1 and so on in the past) in a VM and as happens sometimes the Eddie GUI crashes, but openvpn is still running.  I'll just reboot at this point.

 

When I rebooted in the past the network lock rules were still running because Eddie wasn't shut down properly.

 

But, I've noticed lately that network lock rules are not in place upon reboot.

 

Sounds like I'm seeing the same thing as the OP.

 

Hello!

 

In case it's of any interest and you don't want to reboot for some reason, you can open the System Monitor go to Processes and search for "Mono" and then "openvpn". Killing both, will enable you to restart Eddie without a hitch. I can't speak to the security of it :).


Open This Spoiler If: A Website Is Blocked, You Want To Help AirVPN, Find The Beta/Experimental Client Or You're A New User Wanting Help/Information

Spoiler

Did you make a guide or how-to for something? Then contact me if you want me to index it in my new user guide, so that the community can find it more easily.

Tired of Windows? Why Linux Is Better.


#6 iwih2gk

iwih2gk

    Advanced Member

  • Members
  • PipPipPip
  • 257 posts

Posted 16 January 2018 - 07:24 PM

 

But, I've noticed lately that network lock rules are not in place upon reboot.

 

Hello!

 

That's expected and intentional. Eddie does not set "permanent" iptables rules, they will not survive a system reboot.

 

Kind regards

 

I would just like to mention that the users can proactively protect themselves by closing down via UFW accordingly:  I set UFW (frontend for IP tables) to permanently deny all outgoing and incoming and disable routed and logging.  Now when I initiate Eddie and use network lock the client handles the new tables temporarily leaving only tun0 access to the internet.  When I reboot the next day I have no internet access UNTIL Eddie because again UFW has everything blocked.  This would handle any circumstance where a non-Eddie connection is attempted.  Works without fail on my family machines.  I don't use Eddie's network lock on my other machines because I want to manually control any and all connections.  Part of why I like this configuration is that "family" cannot connect to the internet without going through Air.  Slick and sure fire!







Similar Topics Collapse


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

Servers online. Online Sessions: 14113 - BW: 45099 Mbit/sYour IP: 54.226.41.91Guest Access.