Staff 10014 Posted ... Hello!We're very glad to inform you that a new Eddie Air client version has been released: 2.5. Please read the changelogs: https://airvpn.org/services/changelog.php?software=client&format=html2.5 version is compatible with several Linux distributions. For very important notes about environments, please read here: https://airvpn.org/forum/35-client-software-platforms-environmentsNetwork Lock feature has been implemented in version 2.5 as EXPERIMENTAL for all systems. By default it is turned off, feel free to activate and test it by clicking "AirVPN" -> "Preferences" -> "Advanced" -> "Network Lock" -> "Mode: Automatic". Important information on how it works: https://airvpn.org/topic/12175-network-lockEddie 2.5 for Linux can be downloaded here: https://airvpn.org/linuxEddie 2.5 for Windows can be downloaded here: https://airvpn.org/windowsEddie 2.5 for OS X Mavericks can be downloaded here: https://airvpn.org/macosxPLEASE NOTE: Eddie 2.5 package, just like Eddie 2.4beta package, includes an OpenVPN version re-compiled by us with OpenSSL 1.0.1i for security reasons and to fix this bug: https://community.openvpn.net/openvpn/ticket/328 Eddie 2.5 is free and open source software released under GPLv3Kind regards & dataloveAirVPN Staff Quote Share this post Link to post
iwih2gk 94 Posted ... Seems to be working fine on 14.04. I have Eddie 2.5 on my 14.04 host and I am using 14.04 with TOR on VM's connected via bridge to the host. All seems fine. In candor, I am still using UFW with tunnel only allowed, while also using Eddie's 2.5 network lock feature. Once I run this a few more days I may drop UFW. Your term EXPERIMENTAL left me with ufw still being engaged on my end. Frankly my UFW firewall plays well with 2.5. Probably no extra protection at all but I am watching during the 2.5 experimental phase. Great job on the client. It connects well!!!!!! Quote Share this post Link to post
Corsair28 8 Posted ... So far I am loving this client, but it does not work well with the Windows Firewall Control software when I apply the network lock. I may drop WFC all together after testing the network lock feature since it is working wonderfully by itself. Great job!!!! Quote Share this post Link to post
stupidcats 14 Posted ... Awesome! I'll be using the Network Lock feature quite extensively I think. I'm having a problem though, something that never happened in the old client. I got disconnected from the VPN server I was connected to and then "checking authorization" took a while. Logs here: I 2014.09.15 08:06:52 - AirVPN client version: 2.5, System: Linux, Architecture: x64 . 2014.09.15 08:06:53 - Reading options from /home/epsilon/.airvpn/AirVPN.xml . 2014.09.15 08:06:55 - Data Path: /home/epsilon/.airvpn . 2014.09.15 08:06:55 - App Path: /usr/lib/AirVPN . 2014.09.15 08:06:55 - Executable Path: /usr/lib/AirVPN/AirVPN.exe . 2014.09.15 08:06:55 - Command line arguments: path="/home/epsilon/.airvpn" . 2014.09.15 08:06:55 - Operating System: Unix 3.13.0.32 - Linux laptop 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux I 2014.09.15 08:06:56 - OpenVPN Driver - Found I 2014.09.15 08:06:56 - OpenVPN - Version: OpenVPN 2.3.2 (/usr/sbin/openvpn) I 2014.09.15 08:06:56 - SSH - Version: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 (/usr/bin/ssh) I 2014.09.15 08:06:56 - SSL - Version: stunnel 4.53 (/usr/bin/stunnel4) I 2014.09.15 08:06:56 - IPV6: Available I 2014.09.15 08:06:56 - DNS of the system restored to original settings (Rename method) ! 2014.09.15 08:06:56 - Ready I 2014.09.15 08:07:02 - Session starting. ! 2014.09.15 08:07:02 - Checking environment ! 2014.09.15 08:07:02 - Checking authorization ! 2014.09.15 08:07:03 - Connecting to Propus (Netherlands, Amsterdam) . 2014.09.15 08:07:03 - OpenVPN > OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Feb 4 2014 . 2014.09.15 08:07:03 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100 . 2014.09.15 08:07:03 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file . 2014.09.15 08:07:03 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:07:03 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:07:03 - OpenVPN > Socket Buffers: R=[212992->131072] S=[212992->131072] . 2014.09.15 08:07:03 - OpenVPN > UDPv4 link local: [undef] . 2014.09.15 08:07:03 - OpenVPN > UDPv4 link remote: [AF_INET]37.48.81.8:443 . 2014.09.15 08:07:03 - OpenVPN > TLS: Initial packet from [AF_INET]37.48.81.8:443, sid=848a1551 23998ff5 . 2014.09.15 08:07:03 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2014.09.15 08:07:03 - OpenVPN > Validating certificate key usage . 2014.09.15 08:07:03 - OpenVPN > ++ Certificate has key usage 00a0, expects 00a0 . 2014.09.15 08:07:03 - OpenVPN > VERIFY KU OK . 2014.09.15 08:07:03 - OpenVPN > Validating certificate extended key usage . 2014.09.15 08:07:03 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2014.09.15 08:07:03 - OpenVPN > VERIFY EKU OK . 2014.09.15 08:07:03 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org . 2014.09.15 08:07:09 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2014.09.15 08:07:09 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:07:09 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2014.09.15 08:07:09 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:07:09 - OpenVPN > Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA . 2014.09.15 08:07:09 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]37.48.81.8:443 . 2014.09.15 08:07:11 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) . 2014.09.15 08:07:11 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.4.0.1,comp-lzo no,route 10.4.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.4.82.134 10.4.82.133' . 2014.09.15 08:07:11 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified . 2014.09.15 08:07:11 - OpenVPN > OPTIONS IMPORT: LZO parms modified . 2014.09.15 08:07:11 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified . 2014.09.15 08:07:11 - OpenVPN > OPTIONS IMPORT: route options modified . 2014.09.15 08:07:11 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified . 2014.09.15 08:07:11 - OpenVPN > ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=wlan0 HWADDR=dc:a9:71:10:90:9b . 2014.09.15 08:07:11 - OpenVPN > TUN/TAP device tun0 opened . 2014.09.15 08:07:11 - OpenVPN > TUN/TAP TX queue length set to 100 . 2014.09.15 08:07:11 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip link set dev tun0 up mtu 1500 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip addr add dev tun0 local 10.4.82.134 peer 10.4.82.133 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip route add 37.48.81.8/32 via 192.168.1.1 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip route add 0.0.0.0/1 via 10.4.82.133 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip route add 128.0.0.0/1 via 10.4.82.133 . 2014.09.15 08:07:11 - OpenVPN > /sbin/ip route add 10.4.0.1/32 via 10.4.82.133 . 2014.09.15 08:07:11 - Starting Management Interface . 2014.09.15 08:07:11 - OpenVPN > Initialization Sequence Completed I 2014.09.15 08:07:11 - /etc/resolv.conf renamed to /etc/resolv.conf.airvpn as backup I 2014.09.15 08:07:11 - DNS of the system updated to VPN DNS (Rename method: /etc/resolv.conf generated) ! 2014.09.15 08:07:11 - Flushing DNS ! 2014.09.15 08:07:11 - Checking route ! 2014.09.15 08:07:12 - Connected. . 2014.09.15 08:07:12 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100 . 2014.09.15 08:07:12 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info . 2014.09.15 08:18:27 - OpenVPN > [server] Inactivity timeout (--ping-restart), restarting . 2014.09.15 08:18:27 - OpenVPN > SIGUSR1[soft,ping-restart] received, process restarting . 2014.09.15 08:18:27 - OpenVPN > Restart pause, 2 second(s) ! 2014.09.15 08:18:27 - Disconnecting . 2014.09.15 08:18:27 - Management - Send 'signal SIGTERM' . 2014.09.15 08:18:27 - OpenVPN > MANAGEMENT: CMD 'signal SIGTERM' . 2014.09.15 08:18:27 - OpenVPN > MANAGEMENT: Client disconnected . 2014.09.15 08:18:27 - OpenVPN > Assertion failed at misc.c:785 . 2014.09.15 08:18:27 - OpenVPN > Exiting due to fatal error . 2014.09.15 08:18:27 - Connection terminated. I 2014.09.15 08:18:27 - DNS of the system restored to original settings (Rename method) ! 2014.09.15 08:18:30 - Waiting for latency tests (55 to go) ! 2014.09.15 08:18:36 - Waiting for latency tests (51 to go) ! 2014.09.15 08:18:36 - Waiting for latency tests (50 to go) ! 2014.09.15 08:18:36 - Waiting for latency tests (49 to go) ! 2014.09.15 08:18:37 - Waiting for latency tests (48 to go) ! 2014.09.15 08:18:37 - Waiting for latency tests (47 to go) ! 2014.09.15 08:18:38 - Waiting for latency tests (46 to go) ! 2014.09.15 08:18:38 - Waiting for latency tests (45 to go) ! 2014.09.15 08:18:39 - Waiting for latency tests (44 to go) ! 2014.09.15 08:18:40 - Waiting for latency tests (43 to go) ! 2014.09.15 08:18:40 - Waiting for latency tests (42 to go) ! 2014.09.15 08:18:41 - Waiting for latency tests (38 to go) ! 2014.09.15 08:18:41 - Waiting for latency tests (36 to go) ! 2014.09.15 08:18:41 - Waiting for latency tests (34 to go) ! 2014.09.15 08:18:42 - Waiting for latency tests (32 to go) ! 2014.09.15 08:18:42 - Waiting for latency tests (30 to go) ! 2014.09.15 08:18:43 - Waiting for latency tests (28 to go) ! 2014.09.15 08:18:43 - Waiting for latency tests (26 to go) ! 2014.09.15 08:18:44 - Waiting for latency tests (24 to go) ! 2014.09.15 08:18:44 - Waiting for latency tests (23 to go) ! 2014.09.15 08:18:45 - Waiting for latency tests (21 to go) ! 2014.09.15 08:18:45 - Waiting for latency tests (19 to go) ! 2014.09.15 08:18:46 - Waiting for latency tests (16 to go) ! 2014.09.15 08:18:46 - Waiting for latency tests (15 to go) ! 2014.09.15 08:18:46 - Waiting for latency tests (12 to go) ! 2014.09.15 08:18:46 - Waiting for latency tests (9 to go) ! 2014.09.15 08:18:47 - Waiting for latency tests (6 to go) ! 2014.09.15 08:18:47 - Waiting for latency tests (3 to go) ! 2014.09.15 08:18:48 - Checking authorization . 2014.09.15 08:18:48 - Invalid input block size. . 2014.09.15 08:18:48 - Invalid input block size. . 2014.09.15 08:18:48 - Invalid input block size. . 2014.09.15 08:18:48 - Invalid input block size. . 2014.09.15 08:18:49 - Invalid input block size. . 2014.09.15 08:18:49 - Invalid input block size. . 2014.09.15 08:18:49 - Invalid input block size. . 2014.09.15 08:18:49 - Invalid input block size. W 2014.09.15 08:18:49 - Invalid input block size. ! 2014.09.15 08:18:52 - Checking authorization . 2014.09.15 08:18:52 - Invalid input block size. . 2014.09.15 08:18:53 - Invalid input block size. . 2014.09.15 08:18:53 - Invalid input block size. . 2014.09.15 08:18:53 - Invalid input block size. . 2014.09.15 08:18:53 - Invalid input block size. . 2014.09.15 08:18:54 - Invalid input block size. . 2014.09.15 08:18:54 - Invalid input block size. . 2014.09.15 08:18:54 - Invalid input block size. W 2014.09.15 08:18:54 - Invalid input block size. ! 2014.09.15 08:18:57 - Checking authorization . 2014.09.15 08:18:58 - Invalid input block size. . 2014.09.15 08:18:58 - Invalid input block size. . 2014.09.15 08:18:58 - Invalid input block size. . 2014.09.15 08:18:58 - Invalid input block size. . 2014.09.15 08:18:59 - Invalid input block size. . 2014.09.15 08:18:59 - Invalid input block size. . 2014.09.15 08:18:59 - Invalid input block size. . 2014.09.15 08:18:59 - Invalid input block size. W 2014.09.15 08:18:59 - Invalid input block size. ! 2014.09.15 08:19:02 - Checking authorization . 2014.09.15 08:19:03 - Invalid input block size. . 2014.09.15 08:19:03 - Invalid input block size. . 2014.09.15 08:19:03 - Invalid input block size. . 2014.09.15 08:19:03 - Invalid input block size. . 2014.09.15 08:19:04 - Invalid input block size. . 2014.09.15 08:19:04 - Invalid input block size. . 2014.09.15 08:19:04 - Invalid input block size. . 2014.09.15 08:19:05 - Invalid input block size. W 2014.09.15 08:19:05 - Invalid input block size. ! 2014.09.15 08:19:08 - Checking authorization . 2014.09.15 08:19:09 - Invalid input block size. . 2014.09.15 08:19:10 - Invalid input block size. . 2014.09.15 08:19:11 - Invalid input block size. . 2014.09.15 08:19:11 - Invalid input block size. . 2014.09.15 08:19:12 - Invalid input block size. . 2014.09.15 08:19:13 - Invalid input block size. . 2014.09.15 08:19:15 - Invalid input block size. . 2014.09.15 08:19:16 - Invalid input block size. W 2014.09.15 08:19:16 - Invalid input block size. ! 2014.09.15 08:19:19 - Checking authorization ! 2014.09.15 08:19:19 - Connecting to Syrma (Netherlands, Amsterdam) . 2014.09.15 08:19:19 - OpenVPN > OpenVPN 2.3.2 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [EPOLL] [PKCS11] [eurephia] [MH] [IPv6] built on Feb 4 2014 . 2014.09.15 08:19:19 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100 . 2014.09.15 08:19:19 - OpenVPN > Control Channel Authentication: tls-auth using INLINE static key file . 2014.09.15 08:19:19 - OpenVPN > Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:19:19 - OpenVPN > Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:19:19 - OpenVPN > Socket Buffers: R=[212992->131072] S=[212992->131072] . 2014.09.15 08:19:19 - OpenVPN > UDPv4 link local: [undef] . 2014.09.15 08:19:19 - OpenVPN > UDPv4 link remote: [AF_INET]37.48.81.7:443 . 2014.09.15 08:19:19 - OpenVPN > TLS: Initial packet from [AF_INET]37.48.81.7:443, sid=ed44041d 6b4933ae . 2014.09.15 08:19:20 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2014.09.15 08:19:20 - OpenVPN > Validating certificate key usage . 2014.09.15 08:19:20 - OpenVPN > ++ Certificate has key usage 00a0, expects 00a0 . 2014.09.15 08:19:20 - OpenVPN > VERIFY KU OK . 2014.09.15 08:19:20 - OpenVPN > Validating certificate extended key usage . 2014.09.15 08:19:20 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2014.09.15 08:19:20 - OpenVPN > VERIFY EKU OK . 2014.09.15 08:19:20 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org . 2014.09.15 08:19:28 - OpenVPN > Data Channel Encrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2014.09.15 08:19:28 - OpenVPN > Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:19:28 - OpenVPN > Data Channel Decrypt: Cipher 'AES-256-CBC' initialized with 256 bit key . 2014.09.15 08:19:28 - OpenVPN > Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication . 2014.09.15 08:19:28 - OpenVPN > Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 4096 bit RSA . 2014.09.15 08:19:28 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]37.48.81.7:443 . 2014.09.15 08:19:31 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) . 2014.09.15 08:19:31 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.4.0.1,comp-lzo no,route 10.4.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.4.81.66 10.4.81.65' . 2014.09.15 08:19:31 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified . 2014.09.15 08:19:31 - OpenVPN > OPTIONS IMPORT: LZO parms modified . 2014.09.15 08:19:31 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified . 2014.09.15 08:19:31 - OpenVPN > OPTIONS IMPORT: route options modified . 2014.09.15 08:19:31 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified . 2014.09.15 08:19:31 - OpenVPN > ROUTE_GATEWAY 192.168.1.1/255.255.255.0 IFACE=wlan0 HWADDR=dc:a9:71:10:90:9b . 2014.09.15 08:19:31 - OpenVPN > TUN/TAP device tun0 opened . 2014.09.15 08:19:31 - OpenVPN > TUN/TAP TX queue length set to 100 . 2014.09.15 08:19:31 - OpenVPN > do_ifconfig, tt->ipv6=0, tt->did_ifconfig_ipv6_setup=0 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip link set dev tun0 up mtu 1500 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip addr add dev tun0 local 10.4.81.66 peer 10.4.81.65 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip route add 37.48.81.7/32 via 192.168.1.1 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip route add 0.0.0.0/1 via 10.4.81.65 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip route add 128.0.0.0/1 via 10.4.81.65 . 2014.09.15 08:19:31 - OpenVPN > /sbin/ip route add 10.4.0.1/32 via 10.4.81.65 . 2014.09.15 08:19:31 - Starting Management Interface . 2014.09.15 08:19:31 - OpenVPN > Initialization Sequence Completed I 2014.09.15 08:19:31 - /etc/resolv.conf renamed to /etc/resolv.conf.airvpn as backup I 2014.09.15 08:19:31 - DNS of the system updated to VPN DNS (Rename method: /etc/resolv.conf generated) ! 2014.09.15 08:19:31 - Flushing DNS ! 2014.09.15 08:19:31 - Checking route ! 2014.09.15 08:19:31 - Connected. . 2014.09.15 08:19:31 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100 . 2014.09.15 08:19:31 - OpenVpn Management > >INFO:OpenVPN Management Interface Version 1 -- type 'help' for more info Quote Share this post Link to post
Staff 10014 Posted ... Hello! What the Network Lock feature does on your operating system is transparently explained in the answer to this FAQ: https://airvpn.org/faq/software_lock/ In candor, I am still using UFW with tunnel only allowed, while also using Eddie's 2.5 network lock feature. Once I run this a few more days I may drop UFW. Your term EXPERIMENTAL left me with ufw still being engaged on my end. Network lock under Linux is performed by iptables, maybe it doesn't conflict with UFW because UFW is just an iptables frontend. Network locks are implemented as plugins, we can think about implementing different versions and leave users the choice of network lock method. So far I am loving this client, but it does not work well with the Windows Firewall Control software when I apply the network lock.We alter at runtime Windows Firewall configuration and rules, as explained in the answer to the aforementioned FAQ. Maybe this software you use doesn't expect that. We can look into that, is it this ? Kind regards Quote Share this post Link to post
fuyeah 0 Posted ... The new "Netlock" feature doesn't work on my machine. I'm using Mac OS X 10.10 and the following log message shows up: ! 2014.09.15 01:21:11 - Activation of Network Lock - OSX PFE 2014.09.15 01:21:11 - Unexpected PF Firewall activation failure Quote Share this post Link to post
Corsair28 8 Posted ... Hello! What the Network Lock feature does on your operating system is transparently explained in the answer to this FAQ: https://airvpn.org/faq/software_lock/ In candor, I am still using UFW with tunnel only allowed, while also using Eddie's 2.5 network lock feature. Once I run this a few more days I may drop UFW. Your term EXPERIMENTAL left me with ufw still being engaged on my end. Network lock under Linux is performed by iptables, maybe it doesn't conflict with UFW because UFW is just an iptables frontend. Network locks are implemented as plugins, we can think about implementing different versions and leave users the choice of network lock method. >So far I am loving this client, but it does not work well with the Windows Firewall Control software when I apply the network lock.We alter at runtime Windows Firewall configuration and rules, as explained in the answer to the aforementioned FAQ. Maybe this software you use doesn't expect that. We can look into that, is it this ? Kind regards Yes it is thank you! I have no issues so far other than the compatibility with Windows Firewall Control. I must also mention that the Linux version and MAC os versions are also very good, but I need more time to test them fully, but so far so good. Quote Share this post Link to post
Philiberti 9 Posted ... Hi, I downloaded and installed version 2.5 and wanted to enable the Network Lock. I right clicked the Air taskbar icon and selected Preferences \ Advanced but could not see Network Lock in order to switch it to Automatic (see attached).I'm sure I'm missing something but don't knw what Quote Share this post Link to post
Philiberti 9 Posted ... Ignore my previous post - just found out I had launched eddie 2.4 by mistake - D'Oh. Quote Share this post Link to post
Lyaios 2 Posted ... The new "Netlock" feature doesn't work on my machine. I'm using Mac OS X 10.10 and the following log message shows up: ! 2014.09.15 01:21:11 - Activation of Network Lock - OSX PFE 2014.09.15 01:21:11 - Unexpected PF Firewall activation failureI had the same error. The solution is very simple. Just do a "sudo pfctl -d" first to deactivate the firewall and then use the Netlock feature of the Airvpn client. It is quite a stupid bug in the client. The function Activation() in NetworkLockOsxPf.cs looks for the string "pf enabled". But if you have pf already enabled, the command "pfctl -e" will return instead "pfctl: pf already enabled".Hope I could help 1 fuyeah reacted to this Quote Share this post Link to post
iwih2gk 94 Posted ... Staff, Thank you for the response to my post. I love 2.5 and its by far the smoothest client so far with 14.04. I do use iptables as the client does, but my lazy a@@ will normally use UFW because its so simple to write rules into. Any linux 14.04 users here will be impressed by how great 2.5 runs. Very impressed!! Quote Share this post Link to post
S.O.A. 83 Posted ... The 2.5 update is working just as well as 2.4 on OSX 10.9.4. I have not yet tried using the network lock feature but, I will get to that soon and report back. Quote Share this post Link to post
PortlyNinja 17 Posted ... I am using on windows 7 and 8 and its working well.Network lock is a great addition.Thanks Quote Share this post Link to post
baneofthesith 8 Posted ... Thank you very much Air for a great client. 2.5 works smoothly and I had no problems with it. You guys made a very good job, constantly improving the client. Quote Share this post Link to post
Guest Posted ... Two questions:On the Mac everytime the client starts it asks for password. Is this a permanent inconvenience or will it be rectifiable in a future version?Also, on Windows, will using Windows Firewall Control intefere with the client?Thank you Quote Share this post Link to post
S.O.A. 83 Posted ... Two questions:On the Mac everytime the client starts it asks for password. Is this a permanent inconvenience or will it be rectifiable in a future version?Also, on Windows, will using Windows Firewall Control intefere with the client?Thank you The answer to your first question is yes. I have contacted the AirVPN staff about that awhile ago and they told me that will be permanent. Here is the reason for it in their response to my question. "You need to enter your password every and each time, because Eddie wants to get administrator privileges (it needs them to run OpenVPN with the same privileges, and OpenVPN needs them to modify the system routing table and access network cards)." In regards to your second question, there is a post made earlier on this thread made by @Corsair28 and I'll quote his post below. "So far I am loving this client, but it does not work well with the Windows Firewall Control software when I apply the network lock. I may drop WFC all together after testing the network lock feature since it is working wonderfully by itself. Great job!!!! " According to @Corsair28 if you disable windows firewall control the client works just fine. So give that a try and see what happens. If you are still having problems then open a support ticket and the AirVPN staff will do their best to help you. Quote Share this post Link to post
Guest Posted ... I can live with inputing a password on the Mac, but I can't live with out Windows Firewall Control.I guess I'll just continue using the older version of AirVpn with VPNCheck Pro.Thank you for your answer. Quote Share this post Link to post
Staff 10014 Posted ... I can live with inputing a password on the Mac, but I can't live with out Windows Firewall Control.I guess I'll just continue using the older version of AirVpn with VPNCheck Pro.Thank you for your answer. Hello! You can also use Eddie 2.5 because Network Lock is optional. You decide to activate it or not. In Eddie 2.5 it is disabled by default. Kind regards Quote Share this post Link to post
Guest Posted ... Network Lock is kind of mandatory I think. Unless, your just browsing the net. That's why I use VPNCheck Pro. It will cut all network connections if your vpn connection drops. Quote Share this post Link to post
Staff 10014 Posted ... Network Lock is kind of mandatory I think. Unless, your just browsing the net. That's why I use VPNCheck Pro. It will cut all network connections if your vpn connection drops. Hello, we were suggesting that you can use anyway Eddie 2.5 without going back to outdated client versions which have more bugs, because you are not forced to use Eddie 2.5 network lock feature. You can just keep it not active, and use your custom or favorite type of leaks prevention. Kind regards Quote Share this post Link to post
Not connected, Your IP: 18.116.24.238
Online: 27811 users - 362201 Mbit/s total BW.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png){kind=avatar}