Search the Community
Showing results for tags 'network-lock'.
Found 5 results
-
I'm setting up AirVPN's OpenVPN3 Suite on my home headless Arch server over SSH. I've never had a problem with it in prior years (when the server was Debian, which makes a lot of sense considering it probably had some installed program that blocked AirVPN network locking functionality), but recently it's been kicking my ssh session when every activation due to network lock setting up on a different subnet than my LAN (10.x.x.x vs 192.168.x.x). I was further surprised to find that there does not seem to be any native functionality built into goldcrest or bluetit to allow for exceptions to the network lock iptables rules (i.e. allowing a certain IP or subnet in through the filter); all I can seem to find is the ability to toggle the lock between iptables and nftables. My question, then, is just that: is there any way for me to allow certain addresses through my network lock, while keeping it activate for 99% of external traffic? Or, more preferably, allowing my entire 192.168.x.x subnet?
-
I'm encountering a strange issue for the past few days where I'm unable to connect to the internet when eddie isn't running. Info about my system/software: Mac OSX 10.12.6 Eddie v 2.15.2 Eddie is setup to run with the network lock enabled by default. I have, in the past, faced these issues where the machine would refuse to connect to the internet when eddie wasn't running, and restarting the machine would restore connectivity [sic] Restarting the machine doesn't seem to be doing the trick for me anymore, and I'm stuck with the need to use the machine without the airVPN connectivity (because I need to use my employer's VPN instead) Attaching logs, and screenshots of my Eddie settings. Please let me know if there's more info I can provide. Eddie_20180809_114535.txt
-
Hi. Written my own network lock implementation for macOS in rust. It's based on Eddie's code rules with some modifications. Maybe useful, for example, for Viscosity lovers or those who need some extra futures. My github mirror: netlock
-
Since yesterday I cant connect to any address without using Eddie. I deactivated network lock but I'm still not able to connect. IPtables state: sudo iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination sudo ip6tables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Content of /etc/resolv.conf: # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 Also ping to any address isnt working: ping: google.com: Name or service not known The connection through Eddie in any server of airVPN works without any troubles. Any ideas what is wrong?
-
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