Jump to content
Not connected, Your IP: 34.228.185.211

Search the Community

Showing results for tags 'IPv6'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Frequently asked questions
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Blocked websites warning
    • Eddie - AirVPN Client
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP
    • Mirrors
    • Net Neutrality Monitor

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 41 results

  1. I've just installed Eddie 2.16.3 on a new Windows 10 system. When Network Lock is active, I can't seem to get Eddie to connect to any of the servers because it gets stuck at "Checking route IPv6" and the connection keeps timing out. I have put exceptions in both Malwarebytes and Windows Firewall for all components used by Eddie including the OpenVPN Daemon but it still refuses to connect when Network Lock has been activated. It works fine otherwise, but it is annoying since Network Lock is a useful feature for preventing DNS leaks. I have attached a log file to see if anyone can help me figure out what's causing the problem. Bizarrely this problem is not present in earlier builds of Eddie such as 2.14.5, which I don't want to use for security reasons. I am using Windows 10 Home, Version 1803, OS build 17134.345. I hope this information is sufficient to help resolve the issue. Eddie_20181011_131408.txt
  2. . 2019.01.30 14:37:29 - Eddie version: 2.17.2 / windows_x64, System: Windows, Name: Windows 10 Pro, Version: Microsoft Windows NT 10.0.17763.0, Mono/.Net: v4.0.30319 . 2019.01.30 14:37:29 - Reading options from C:\Users\tharr\AppData\Local\AirVPN\default.xml . 2019.01.30 14:37:29 - Command line arguments (1): path="home" . 2019.01.30 14:37:29 - Profile path: C:\Users\tharr\AppData\Local\AirVPN\default.xml . 2019.01.30 14:37:31 - OpenVPN Driver - TAP-Windows Adapter V9, version 9.21.2 . 2019.01.30 14:37:31 - OpenVPN - Version: 2.4.6 - OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 (C:\Program Files\AirVPN\openvpn.exe) . 2019.01.30 14:37:31 - SSH - Version: plink 0.67 (C:\Program Files\AirVPN\plink.exe) . 2019.01.30 14:37:31 - SSL - Version: stunnel 5.40 (C:\Program Files\AirVPN\stunnel.exe) . 2019.01.30 14:37:31 - curl - Version: 7.54.1 (C:\Program Files\AirVPN\curl.exe) . 2019.01.30 14:37:31 - Certification Authorities: C:\Program Files\AirVPN\res\cacert.pem I 2019.01.30 14:37:32 - Ready . 2019.01.30 14:37:36 - Cannot retrieve information about AirVPN: Length of the data to decrypt is invalid. - Status: HTTP/1.1 100 Continue - Headers: - Body (127875 bytes): HTTP/1.1 200 OK . 2019.01.30 14:37:36 - Server: nginx . 2019.01.30 14:37:36 - Date: Wed, 30 Jan 2019 20:37:32 GMT . 2019.01.30 14:37:36 - Content-Type: application/octet-stream . 2019.01.30 14:37:36 - Content-Length: 127376 . 2019.01.30 14:37:36 - Connection: keep-alive . 2019.01.30 14:37:36 - Pragma: no-cache . 2019.01.30 14:37:36 - Expires: 0 . 2019.01.30 14:37:36 - Cache-Control: max-age=0, no-cache, no-store, must-revalidate . 2019.01.30 14:37:36 - x-air-bk: 1 . 2019.01.30 14:37:36 - x-air-cache: 0 . 2019.01.30 14:37:36 - X-Frame-Options: SAMEORIGIN . 2019.01.30 14:37:36 - X-XSS-Protection: 1; mode=block . 2019.01.30 14:37:36 - X-Content-Type-Options: nosniff . 2019.01.30 14:37:36 - Referrer-Policy: strict-origin-when-cross-origin . 2019.01.30 14:37:36 - Strict-Transport-Security: max-age=31536000; includeSubdomains; preload . 2019.01.30 14:37:36 - wSX<X7??????~?\5?(???????~UTh9????v??Q???|??4??BpE?
  3. Hello! I'm facing a strange issue regarding IPv6. On the same machine (macOS Mojave) with latest Eddie client and IPv6, enabled some browser do work with IPv6 (Chromium based) and others - Safari & Firefox - do not. I tested with IPleak.net and other IPv6 tests online. I also reset both browsers and disabled all extension/plugins to see if any of them would interfere maybe. Still no love for IPv6. What could be causing this? Is this to be expected? Am I missing something? Thank you for your help!
  4. When trying to add a .ovpn to Gnome network manger with ipv6 enabled (Linux | >=2.4 | UDP 53 Entry 2 | IPv4 & IPv6 (connect with IPv6) | continent > America) It gives the error seen in the Attached file The VPN Plugin failed to import the VPN connection correctly configuration error: invalid 1th argument to 'proto' (line 23) With line 23 being proto udp6 OS Info System: Kernel: 4.19.7-103.current x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Budgie 10.4-85-g36667bcb Distro: Solus 3.9999 Is this something wrong with the Config Generator or should I contact Solus support and try to debug there
  5. Does Android 9 (Pie) fully support IPv6? I'm wondering because I'm not sure which options to choose in AirVPN's Config Generator. Should I choose "IPv4 only," "IPv4 & IPv6 (connect with IPv4)," or "IPv4 & IPv6 (connect with IPv6)?" Right now, I'm using an AirVPN configuration with just IPv4. But, I'm wondering if one of the IPV6 options might be a better choice.
  6. I use Windows 10 Pro and every time I connect using Eddie I saw the following "toast" warning: The Wi-Fi properties had IPv6 enabled: ... so I was puzzled why I am getting this warning repeatedly. According to the following reference I had 0xff set in ...\Tcpip6\Parameters\DisabledComponents: https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users Initially I tried 0xfe, and after a reboot the warning was still there when Eddie connects to a server. I then set 0x20 (as recommended by Microsoft) and now the warning no longer appears. Please be aware that changes to the registry need to be done with great care and I advise a manual key backup as well as creating a System Restore Point. You are responsible for all eventualities.
  7. Hello, This has been asked in quite a few places already but there is no clear answer as far as I can tell. Long story short, if you ISP provides you with both IPv4 and IPv6 addresses, then by connecting to AirVPN VPN only the IPv4 traffic is being routed through the tunnel. If a website (or any other remote endpoint) runs on IPv6, then your real IPv6 (the one provided to you by your ISP) will be used and so you end up with an IP leak. Not good. The easiest choice is to disable IPv6 per host basis or use some iptables or other firewall magic to filter out all the IPv6 traffic. This is only a workaround and a very inconvenient one especially when you run AirVPN on a router. The best solution would be for AirVPN to provide a dual stack IPv4/IPv6 tunnel so connected clients can reach the modern IPv6 world privately and securely in a similar fashion to IPv4. Are there any plans to support this option? As far as I can see there are only a handful of VPN providers out there which actually provide dual stack VPNs so it would be nice for AirVPN join this effort.
  8. heyhey, i'm having trouble setting up a ipv6 vpn connection with the (manjaro/arch) linux "network-manager". when i want to set up a ipv4 connection, i go to the "client area" on airvpn.org, start the "config generator", check "advanced" an then set: OS: LinuxOpenVPN version >= 2.4Need IPv6?: "IPv4 only"Protocol: UDP | Port: 443 | Entry IP: 1In the advanced section i check "Separate keys/certs from .ovpn file" and "Resolved hosts in .ovpn file"Server: xxxi then generate the config and download all the files into a new/empty folder. afterwards i start the network-manager connection editors gui ($ nm-connection-editor), click the "+" button, select "import a saved vpn configuration", click "create", navigate to the folder with the config and key files, select the "xxx.ovpn" file and then just click "save", since the nm-connection-editor automatically sets up the right key files etc. in this case everything works as expected. HOWEVER if i try to do the same with a IPv6 config file ("Need IPv6?" set to "IPv4 & IPv6 (connect with IPv6)" - all other settings the same) i get an error when trying to "import a saved vpn configuration" with the nm-connection-editor. when i open the "xxx.ovpn" file with a text editor and change the line "proto udp6" (this is the line before "tls-auth 'ta.key' 1") to "proto udp", i can import without the error message however the connection is not working afterwards. do you have any ideas what i could do different? should i set up the connection manually? thanks in advance!
  9. I just added in IPv6 support on my pfSense box, using AirVPN and a VLAN. Note that I already had the VPN VLAN setup and working correctly with IPv4, so this guide is only about what needed to be changed to add in IPv6 support. Recently, AirVPN has implemented IPv6 across their servers. Provided you are running a recent version of OpenVPN (>= 2.4), and you adjust your client configuration properly, you will be assigned an IPv6 address along with the typical IPv4 address. In my setup, I’m using pfSense as my firewall / router, and have several VLANs configured for various purposes. One of these VLANs is specifically for VPN usage. So the question becomes, how to take the single IPv6 address assigned from AirVPN and make it usable on a VLAN, for multiple hosts. This setup is severely sub-optimal, as IPv6 was designed to avoid NAT (there are what, 3.4x10^38 available addresses?). Given that the design of the protocol and AirVPN’s implementation are at odds, there are some problems that you will encounter. The most annoying being that browsers don’t want to use your IPv6 address, and you will continue to use IPv4, despite having everything setup “correctly.” It may be possible to overcome this with some per-host modifications (on Linux, look to /etc/gai.conf), but that is perhaps not maintainable in the long run. This problem stems from the fact that the address Air is providing is a Unique Local Address (ULA), which, by definition, is not globally routable. This address gets translated at Air’s servers into a normal, globally routable, address. But what the software on your machine sees is a ULA, and since that isn’t a globally routable IP address, the software will prefer the IPv4 address, where it is understood that NAT will probably be used. Given this implementation, I am not convinced it is worth it to setup IPv6 in this type of configuration. Having said all that, here is how I configured things to get IPv6 “working” with AirVPN on a pfSense VLAN: 1: Get an IPv6 address from AirVPN Assuming you are running a recent release of pfSense, you should have the necessary OpenVPN version for this to work (I’m on pfSense 2.4.4, which is using OpenVPN 2.4.6). Go into your OpenVPN client configuration and set “Protocol” to “UDP IPv4 and IPv6 on all interfaces (multihome)” scroll down to “Custom options” and make sure you have these 2 lines: push-peer-info; setenv UV_IPV6 yes; Save, and possibly restart the service. You should now have both IPv4 and IPv6 addresses assigned to your VPN connection 2: Create a new Gateway I can’t remember if the gateway was automatically created at this point. If not, Add a new gateway. If one was auto created, edit it. Then Make sure Interface is set to the VPN Address family is IPv6 Give it a name (VPN1_WAN_IPv6 in my case) I’ve left everything else at default settings, then set a description, and Save and reload 3: Modify your VPN VLAN From the “Interfaces” menu, select your VPN VLAN entry, then Set “IPv6 Configuration Type” to “Static IPv6” Scroll down to the “Static IPv6 Configuration” section and set an address and prefix. I chose a “random” ULA (FDxx:xxxx:xxxx:10::1). Obviously, choose hex characters in place of the “x”s and the “10” matches my vlan number. Set the prefix to /64 Leave the “use IPv4 connectivity” unchecked and the gateway set to “None” Save and reload 4: Configure Router Advertisements and/or DHCPv6 From the “Services” menu, select “DHCPv6 Server & RA” - then choose your VLAN. In my setup, I’m not bothering with DHCP, just using SLACC, so I go directly to the “Router Advertisements” tab. Set Router Mode to unmanaged Priority to Normal You may choose to put your IPv6 DNS server into the DNS configuration section (I believe Air’s server is fde6:7a:7d20:4::1 Leave everything else as is (blank) Save and reload 5: Set NAT Rules From the “Firewall” menu, select “NAT”, then go to the “Outbound” tab Click the second “Add” button Set “Interface” to your VPN gateway “Address Family” is “IPv6” Source type is “network” Source network is the ULA you setup earlier (“Fdxx:xxxx:xxxx:10::/64”) I did this using an alias. Note that the subnet drop down doesn’t list anything above a /32 (it’s meant for IPv4), so I left it at /32. Seems to work anyway. The Translation Address should be set to “Interface Address” Add in a description, if you wish, and Save and reload 6: Set Firewall Rules From the “Firewall” menu, select “Rules” and then the appropriate VLAN tab Click the second “Add” button “Action” is “Pass” “Interface” is your VLAN “Address Family” is “IPv6” Set the rules appropriately for your situation. In my case, just to get things working, I set “Protocol” to “Any” “Source” to “[VLAN] net” Click the “Display Advanced” button Scroll down to “Gateway” and select your previously configured VPN IPv6 gateway Save and reload NOTE: Be sure to move the rule you just created into the correct spot in your rules list! Remember, the rules are checked in order, so if you have a deny rule above your new pass rule in the list, it won’t work. At this point I rebooted pfSense and my VPN client machine. I now have an IPv6 address, assigned from the ULA block I setup. Visiting https://ipleak.net shows I have both IPv4 and IPv6 connectivity. Going to https://test-ipv6.com gives me a 10/10, but with the note that the browser is avoiding using the IPv6 address. See the note from AirVPN Staff about this: https://airvpn.org/topic/25140-the-issue-your-browser-is-avoiding-ipv6/ Hopefully this is helpful to someone out there. MrFricken
  10. Since yesterday I cannot connect to the AirVPN servers using the Eddie client anymore. It used to work just fine, but now when I try to connect to a recommended server, it will flush the DNS, check IPv4 routes and finally check IPv6 routes and then the connection is cancelled. I get a pop-up message (notification) saying "Checking route IPv6 failed" and then I am disconnected. Eddie automatically tries to reconnect to the next server then, but that also failed. I have waited for about 5 retries, and also tried manually selecting servers from different countries. Still I cannot connect. I just updated my Eddie client to version 2.16.3. My OS is Linux Mint 18. I am now connected using openvpn from the command line: sudo openvpn AirVPN_UDP-443.ovpn still works. Any idea how I can get the Eddie client to connect again? Any help would be appreciated, thanks in advance! Also, please let me know if I can provide more information that you might need to help.
  11. Hi, Ive been using Airvpn for a few years now with now real issues. About a week ago had problems with Eddie 2:13:6 and connection dropping out because of "server and updates" failing. Updated yesterday to Eddie 2:15:2 and have similar problems, Eddie will not connect unless I uncheck the "check Airvpn tunnel" in options, had to do this because Eddie kept hanging on checking IPV6 on startup. When it does connect to any server - I have tried a lot of them along with different protocols - the speed drops to zero very quickly and get the "Cannot retrieve systems & servers data" error . 2018.07.09 13:15:16 - Eddie version: 2.15.2 / windows_x64, System: Windows, Name: Windows 7 Home Premium, Version: Microsoft Windows NT 6.1.7601 Service Pack 1, Mono/.Net: v2.0.50727 . 2018.07.09 13:15:16 - Reading options from C:\Program Files\AirVPN\default.xml . 2018.07.09 13:15:17 - Command line arguments (0): . 2018.07.09 13:15:17 - Profile path: C:\Program Files\AirVPN\default.xml . 2018.07.09 13:15:20 - OpenVPN Driver - TAP-Windows Adapter V9, version 9.21.2 . 2018.07.09 13:15:20 - OpenVPN - Version: 2.4.6 - OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 (C:\Program Files\AirVPN\openvpn.exe) . 2018.07.09 13:15:20 - SSH - Version: plink 0.67 (C:\Program Files\AirVPN\plink.exe) . 2018.07.09 13:15:20 - SSL - Version: stunnel 5.40 (C:\Program Files\AirVPN\stunnel.exe) . 2018.07.09 13:15:20 - curl - Version: 7.54.1 (C:\Program Files\AirVPN\curl.exe) . 2018.07.09 13:15:20 - Certification Authorities: C:\Program Files\AirVPN\res\cacert.pem ! 2018.07.09 13:15:21 - Activation of Network Lock - Windows Filtering Platform . 2018.07.09 13:15:21 - Updating systems & servers data ... I 2018.07.09 13:15:21 - Ready . 2018.07.09 13:15:22 - Systems & servers data update completed I 2018.07.09 13:15:29 - Session starting. I 2018.07.09 13:15:30 - Checking authorization ... ! 2018.07.09 13:15:30 - Connecting to Alathfar (United Kingdom, Maidenhead) . 2018.07.09 13:15:30 - Routes, added a new route, 185.103.96.146 for gateway 192.168.1.254 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: stunnel 5.40 on x86-pc-mingw32-gnu platform . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: Compiled/running with OpenSSL 1.0.2k 26 Jan 2017 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: Threading:WIN32 Sockets:SELECT,IPv6 TLS:ENGINE,OCSP,PSK,SNI . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: Reading configuration from file C:\Program Files\AirVPN\cb1b90540e7095dd0a0a5d83eae2bfeb2ac25471cf9c04369f2b50cb42ccb2ba.tmp.ssl . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: UTF-8 byte order mark not detected . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[ui]: Initializing service [openvpn] . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG4[ui]: Service [openvpn] needs authentication to prevent MITM attacks . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[ui]: Configuration successful . 2018.07.09 13:15:31 - OpenVPN > OpenVPN 2.4.6 x86_64-w64-mingw32 [sSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Apr 27 2018 . 2018.07.09 13:15:31 - OpenVPN > Windows version 6.1 (Windows 7) 64bit . 2018.07.09 13:15:31 - OpenVPN > library versions: OpenSSL 1.1.0h 27 Mar 2018, LZO 2.10 . 2018.07.09 13:15:31 - Connection to OpenVPN Management Interface . 2018.07.09 13:15:31 - OpenVPN > MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:3100 . 2018.07.09 13:15:31 - OpenVPN > Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key . 2018.07.09 13:15:31 - OpenVPN > Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication . 2018.07.09 13:15:31 - OpenVPN > Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key . 2018.07.09 13:15:31 - OpenVPN > Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication . 2018.07.09 13:15:31 - OpenVPN > TCP/UDP: Preserving recently used remote address: [AF_INET]127.0.0.1:60783 . 2018.07.09 13:15:31 - OpenVPN > Socket Buffers: R=[8192->262144] S=[8192->262144] . 2018.07.09 13:15:31 - OpenVPN > Attempting to establish TCP connection with [AF_INET]127.0.0.1:60783 [nonblock] . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[0]: Service [openvpn] accepted connection from 127.0.0.1:49333 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: s_connect: connecting 185.103.96.146:443 . 2018.07.09 13:15:31 - OpenVPN > TCP connection established with [AF_INET]127.0.0.1:60783 . 2018.07.09 13:15:31 - OpenVPN > TCP_CLIENT link local: (not bound) . 2018.07.09 13:15:31 - OpenVPN > TCP_CLIENT link remote: [AF_INET]127.0.0.1:60783 . 2018.07.09 13:15:31 - OpenVPN > MANAGEMENT: Client connected from [AF_INET]127.0.0.1:3100 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[0]: s_connect: connected 185.103.96.146:443 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG5[0]: Service [openvpn] connected remote server from 192.168.1.81:49335 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: SNI: sending servername: 185.103.96.146 . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: Peer certificate not required . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: Certificate verification disabled . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: Client certificate not requested . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: TLS connected: new session negotiated . 2018.07.09 13:15:31 - SSL > 2018.07.09 13:15:31 LOG6[0]: Negotiated TLSv1.2 ciphersuite ECDHE-RSA-AES256-GCM-SHA384 (256-bit encryption) . 2018.07.09 13:15:31 - OpenVPN > TLS: Initial packet from [AF_INET]127.0.0.1:60783, sid=b2b90158 7d1916da . 2018.07.09 13:15:31 - OpenVPN > VERIFY OK: depth=1, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=airvpn.org CA, emailAddress=info@airvpn.org . 2018.07.09 13:15:31 - OpenVPN > VERIFY KU OK . 2018.07.09 13:15:31 - OpenVPN > Validating certificate extended key usage . 2018.07.09 13:15:31 - OpenVPN > ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication . 2018.07.09 13:15:31 - OpenVPN > VERIFY EKU OK . 2018.07.09 13:15:31 - OpenVPN > VERIFY OK: depth=0, C=IT, ST=IT, L=Perugia, O=airvpn.org, CN=server, emailAddress=info@airvpn.org . 2018.07.09 13:15:32 - OpenVPN > Control Channel: TLSv1.2, cipher TLSv1.2 DHE-RSA-AES256-GCM-SHA384, 4096 bit RSA . 2018.07.09 13:15:32 - OpenVPN > [server] Peer Connection Initiated with [AF_INET]127.0.0.1:60783 . 2018.07.09 13:15:33 - OpenVPN > SENT CONTROL [server]: 'PUSH_REQUEST' (status=1) . 2018.07.09 13:15:33 - OpenVPN > PUSH: Received control message: 'PUSH_REPLY,comp-lzo no,redirect-gateway ipv6 def1 bypass-dhcp,dhcp-option DNS 10.5.39.1,dhcp-option DNS6 fde6:7a:7d20:127::1,tun-ipv6,route-gateway 10.5.39.1,topology subnet,ping 10,ping-restart 60,ifconfig-ipv6 fde6:7a:7d20:127::1000/64 fde6:7a:7d20:127::1,ifconfig 10.5.39.2 255.255.255.0,peer-id 0,cipher AES-256-GCM' . 2018.07.09 13:15:33 - OpenVPN > Pushed option removed by filter: 'redirect-gateway ipv6 def1 bypass-dhcp' . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: timers and/or timeouts modified . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: compression parms modified . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: --ifconfig/up options modified . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: route-related options modified . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: peer-id set . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: adjusting link_mtu to 1627 . 2018.07.09 13:15:33 - OpenVPN > OPTIONS IMPORT: data channel crypto options modified . 2018.07.09 13:15:33 - OpenVPN > Data Channel: using negotiated cipher 'AES-256-GCM' . 2018.07.09 13:15:33 - OpenVPN > Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key . 2018.07.09 13:15:33 - OpenVPN > Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key . 2018.07.09 13:15:33 - OpenVPN > interactive service msg_channel=0 . 2018.07.09 13:15:33 - OpenVPN > ROUTE_GATEWAY 192.168.1.254/255.255.255.0 I=11 HWADDR=00:24:8c:3e:fe:f6 . 2018.07.09 13:15:33 - OpenVPN > GDG6: remote_host_ipv6=n/a . 2018.07.09 13:15:33 - OpenVPN > NOTE: GetBestInterfaceEx returned error: Element not found. (code=1168) . 2018.07.09 13:15:33 - OpenVPN > ROUTE6: default_gateway=UNDEF . 2018.07.09 13:15:33 - OpenVPN > open_tun . 2018.07.09 13:15:33 - OpenVPN > TAP-WIN32 device [Local Area Connection 2] opened: \\.\Global\{854F057F-7592-4A70-90F5-0CB7FD030F92}.tap . 2018.07.09 13:15:33 - OpenVPN > TAP-Windows Driver Version 9.21 . 2018.07.09 13:15:33 - OpenVPN > Set TAP-Windows TUN subnet mode network/local/netmask = 10.5.39.0/10.5.39.2/255.255.255.0 [sUCCEEDED] . 2018.07.09 13:15:33 - OpenVPN > Notified TAP-Windows driver to set a DHCP IP/netmask of 10.5.39.2/255.255.255.0 on interface {854F057F-7592-4A70-90F5-0CB7FD030F92} [DHCP-serv: 10.5.39.254, lease-time: 31536000] . 2018.07.09 13:15:33 - OpenVPN > Successful ARP Flush on interface [12] {854F057F-7592-4A70-90F5-0CB7FD030F92} . 2018.07.09 13:15:33 - OpenVPN > do_ifconfig, tt->did_ifconfig_ipv6_setup=1 . 2018.07.09 13:15:34 - OpenVPN > NETSH: C:\Windows\system32\netsh.exe interface ipv6 set address interface=12 fde6:7a:7d20:127::1000 store=active . 2018.07.09 13:15:35 - OpenVPN > NETSH: C:\Windows\system32\netsh.exe interface ipv6 set dns Local Area Connection 2 static fde6:7a:7d20:127::1 validate=no . 2018.07.09 13:15:36 - Detected an OpenVPN bug (On-Link route on VPN range), autofix. . 2018.07.09 13:15:36 - OpenVPN > add_route_ipv6(fde6:7a:7d20:127::/64 -> fde6:7a:7d20:127::1000 metric 0) dev Local Area Connection 2 . 2018.07.09 13:15:36 - OpenVPN > C:\Windows\system32\netsh.exe interface ipv6 add route fde6:7a:7d20:127::/64 interface=12 fe80::8 store=active . 2018.07.09 13:15:36 - OpenVPN > env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem . 2018.07.09 13:15:41 - OpenVPN > TEST ROUTES: 1/1 succeeded len=0 ret=1 a=0 u/d=up . 2018.07.09 13:15:41 - OpenVPN > C:\Windows\system32\route.exe ADD 127.0.0.1 MASK 255.255.255.255 192.168.1.254 . 2018.07.09 13:15:41 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4 . 2018.07.09 13:15:41 - OpenVPN > Route addition via IPAPI succeeded [adaptive] . 2018.07.09 13:15:41 - OpenVPN > C:\Windows\system32\route.exe ADD 0.0.0.0 MASK 128.0.0.0 10.5.39.1 . 2018.07.09 13:15:41 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4 . 2018.07.09 13:15:41 - OpenVPN > Route addition via IPAPI succeeded [adaptive] . 2018.07.09 13:15:41 - OpenVPN > C:\Windows\system32\route.exe ADD 128.0.0.0 MASK 128.0.0.0 10.5.39.1 . 2018.07.09 13:15:41 - OpenVPN > ROUTE: CreateIpForwardEntry succeeded with dwForwardMetric1=20 and dwForwardType=4 . 2018.07.09 13:15:41 - OpenVPN > Route addition via IPAPI succeeded [adaptive] . 2018.07.09 13:15:41 - OpenVPN > add_route_ipv6(::/3 -> fde6:7a:7d20:127::1 metric -1) dev Local Area Connection 2 . 2018.07.09 13:15:41 - OpenVPN > C:\Windows\system32\netsh.exe interface ipv6 add route ::/3 interface=12 fe80::8 store=active . 2018.07.09 13:15:41 - OpenVPN > env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem . 2018.07.09 13:15:41 - OpenVPN > add_route_ipv6(2000::/4 -> fde6:7a:7d20:127::1 metric -1) dev Local Area Connection 2 . 2018.07.09 13:15:41 - OpenVPN > C:\Windows\system32\netsh.exe interface ipv6 add route 2000::/4 interface=12 fe80::8 store=active . 2018.07.09 13:15:41 - OpenVPN > env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem . 2018.07.09 13:15:42 - OpenVPN > add_route_ipv6(3000::/4 -> fde6:7a:7d20:127::1 metric -1) dev Local Area Connection 2 . 2018.07.09 13:15:42 - OpenVPN > C:\Windows\system32\netsh.exe interface ipv6 add route 3000::/4 interface=12 fe80::8 store=active . 2018.07.09 13:15:42 - OpenVPN > env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem . 2018.07.09 13:15:42 - OpenVPN > add_route_ipv6(fc00::/7 -> fde6:7a:7d20:127::1 metric -1) dev Local Area Connection 2 . 2018.07.09 13:15:42 - OpenVPN > C:\Windows\system32\netsh.exe interface ipv6 add route fc00::/7 interface=12 fe80::8 store=active . 2018.07.09 13:15:42 - OpenVPN > env_block: add PATH=C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem . 2018.07.09 13:15:42 - Interface Local Area Connection 2 metric changed from Automatic to 3, layer IPv4 . 2018.07.09 13:15:42 - Interface Local Area Connection 2 metric changed from Automatic to 3, layer IPv6 . 2018.07.09 13:15:42 - DNS leak protection with packet filtering enabled. . 2018.07.09 13:15:43 - DNS IPv4 of a network adapter forced (Local Area Connection 2, from manual (10.50.0.1) to 10.5.39.1) . 2018.07.09 13:15:44 - DNS IPv6 of a network adapter forced (Local Area Connection 2, from automatic to fde6:7a:7d20:127::1) . 2018.07.09 13:15:44 - Routes, added a new route, 185.103.96.143 for gateway 10.5.39.1 . 2018.07.09 13:15:44 - Routes, added a new route, 2a01:a500:320:52a4:c626:3328:bc3c:1a5f for gateway fde6:7a:7d20:127::1 . 2018.07.09 13:15:44 - Flushing DNS I 2018.07.09 13:15:51 - Checking DNS ! 2018.07.09 13:15:52 - Connected. . 2018.07.09 13:15:52 - OpenVPN > Initialization Sequence Completed . 2018.07.09 13:16:31 - SSL > 2018.07.09 13:16:31 LOG6[cron]: Executing cron jobs . 2018.07.09 13:16:31 - SSL > 2018.07.09 13:16:31 LOG6[cron]: Cron jobs completed in 0 seconds . 2018.07.09 13:26:22 - Updating systems & servers data ... . 2018.07.09 13:27:43 - Cannot retrieve systems & servers data. (curl: (28) Connection timed out after 20000 milliseconds) Id be very grateful if anyone could take a look at the log and see whats going on, Thanks.
  12. When I connect to any other IPv6-enabled AirVPN server using the Eddie client, I can go to ipleak.net and it will show me the server's IPv6 address and I am able to browse IPv6 only sites. However, two of the Fremont, CA, USA servers, Heze and Persei, both say that they are IPv6 supported on the airvpn.org status page and in the client when you connect to them you can see the IPv6 address, but when I go to ipleak.net on any one of these two servers, the IPv6 test fails, and I am not able to browse IPv6 only websites. I think maybe there is an issue with the configuration on the servers or something like that.
  13. Hi, I've purchased a Windows 10 PC and I'm not overly familiar with the OS, other than the basics. I've installed Eddie and and signed in ok, but when I try to connect to any server Eddie gets to "Checking Route IPv6" and then fails to connect Then Eddie disconnects and tries to reconnect only to fail again. I'm at a loss of what to do. Any suggestions are welcomed. Thank you.
  14. greetings, I'm currently testing out AirVPN before buying a longer subscription. However I currently have some trouble with WebRTC leaks of my IPv6 address. My setup is the following: Arch Linux 64 BitEddie 2.15.2Network Lock enabledChrome/FirefoxUBlock origin option to prevent WebRTC leaks enabled.ISP Unitymedia DSLite (IPv6) When I connect to a suggested server (with network lock enabled) and check IPLeak.net, it looks like this: The address seen under WebRTC IPv6 is the same when not connected, so something is definitely leaking. I tried with both Firefox and Chrome. Is there a way to solve this issue? Can WebRTC leaks be an issue when using torrents? Regards
  15. Hello I've been searching the boards for a solution, but am not really sure how to describe the issue so as to search. Essentially the issue is that when I attempt to connect to an Air US based server, the connection proceeds until the IPv6 stage then the connection is terminated. However, I can connect to the Switzerland based servers without any trouble. I am using Ubuntu 16.04, Eddie 2.14.5. All up to date. I'm sure there is a solution, but not sure how to find it. Thank you for reading and any response. Regards T
  16. I am using the Eddie for Android latest version, and with the IPv6 setting set to "request", and when I connect to one of the IPv6 enabled servers such as Capricornus, I do not have IPv6 connectivity, only IPv4. ipleak.net only shows the VPN IPv4 address, and I am unable to view IPv6 only sites such as ipv6.google.com. how can I fix this and be able to use the VPN'S IPv6 address?
  17. Good morning! Sorry if I posted this in the wrong area, but I've been looking for a guide to help setup IPV6 on PfSense over AirVPN's updated servers. No, I don't want IPV6 from my ISP (I already have that and have been testing that); instead, I would like someone who is knowledgeable about the subject to help me (and other people) out with setting it up. If I figure something out in the meantime, I will post w/ my results. Thanks in advance! ------- Mods: please move the topic if I put it in the wrong area. I is sorry in advance.
  18. Burper

    Ipv6

    Can you make a page that informs us of when servers become Ipv6?
  19. After installing the recent version from the APT repository (2.13.6), I got a message upon connecting to a server that I didn't manage to reproduce afterwards, something like: "IPv6 cannot be safely disabled on Linux in order to make the network lock effective. This can make your IPv6 address leak if your provider supports IPv6. This setting can be changed in Preferences / Advanced / IPv6." This sounds worrying to me, but I don't understand the message. The quoted setting is set to "disable". Does this safely disable my IPv6 or not? I know how to disable IPv6 on the kernel level, but I'm not sure whether that is necessary or not. Sorry that the above message is not an exact quote, it's just what I remember from it. It didn't appear again, which is even more worrying to me... Edit: Here is the exact message that I copied from Github: This message is confusing because first it says that "our software can't disable (...) safely IPv6 on Linux", then it talks about IPv6 detection, and the actual settings entry is about disabling the use of IPv6 altogether... So I assume that this just means that "we can't forward IPv6 on Linux, so we will disable it completely"? Sounds ok to me that way. Please confirm that this message just means that everything is working as expected. xD
  20. Hi, I understood you are working hard on getting IPv6 up and running. Any update for us ?
  21. Hello, now i get my new connection and with it i get ipv6 only. There is a ds-lite tunnel for ipv4 things but it won't work with the AirVPN client. I always get the following: The machine runs with Xubuntu 16.10 64bit. You will find my logfile in the Attachment. I can't use AirVPN now. :-( What can i do? Cheers AirVPN_20161202_090120.txt
  22. Hi, This is going to sound weird but... while I'm tunneled, how do I re-enable IPv6 on my android? After fighting with this for a long time, I've discovered that in order for WiFi calling to work on T-Mobile, IPv6 has to be enabled on the phone. IPv6 doesn't have to be available, so I can disable it on my router to prevent IP leaks, but I do need this enabled on the phone itself. When I connect I see this line: did_ifconfig_ipv6_setup=0 which is disabling IPv6 How do I override and set it back to 1? I'm on a rooted Nexus 6P so getting access won't be an issue although I'd prefer to set it directly in the OpenVPN config. Thanks!
  23. Hello everyone! This is my first post, so keep that in mind. Also, while I have better-than-average I.T. skills, I'm hardly an expert. I have recently encountered several problems, all of which I did not notice until after I installed the Windows 10 Fall Creators Update. Note that that does not necessarily mean they weren't present before the update; I just didn't notice them until afterwards. I also have some other questions. 1. If I open Eddie and activate network lock, remain unconnected to a server, attempt to load a webpage, and it doesn't work -- does that definitively mean that Network Lock is working and secure? (Assuming, of course, that it does work with network lock deactivated.) 2. I keep getting the message, "Recovery. Unexpected Crash?" (the question mark is part of the message). 3. I keep getting this message too: "The requested protocol has not been configured into the system, or no implementation for it exists." 4. If I run ipleak.net while connected to an AirVPN server, and: my IPv4 is the AirVPN server, no forwarded IP is detected, IPv6 test is not reachable, RTCPeerConnection is not available, and the DNS addresses are all AirVPN servers -- then am I definitively secured? 5. It appears IPv6 doesn't work (I get the "IPv6 test not reachable" message on ipleak.net) at all times, even if I'm not running Eddie. This was not the case when I first installed and set up Eddie. Toggling Eddie's "Disable IPv6 at OS level if requested" option doesn't seem to make a difference. 6. In Eddie's preferences, under Advanced, for the IPv6 dropdown menu, what's the difference between "None" and "Disable"? 7. What does "Force TAP interface UP" mean? I probably won't have time to check this thread again until Sunday. Thanks a bunch!
  24. Hi all, I've followed the instructions at https://airvpn.org/topic/11431-using-airvpn-with-linux-from-terminal/ in order to set up my account. This works fine and leak-free, when my local networks gives me an IPv4 address -- but if I get an IPv6 address, that address is leaked to remote sites according to https://ipleak.net/ . How do I prevent that? Thanks, Chris
  25. This may be a newb question, but I need to satisfy my curiosity. Whenever I fire up a VPN connection, I like to check with www.ipleak.net to make sure everything is on the up & up after connecting. I've noticed that on the results page, it shows "IPv6 test not reachable", which I assume means that the Eddie client is doing it's job and disabling IPv6 when connecting. I then see that under "DNS Addresses" it's show 2 servers, One using an IPv4 IP address and the other using an IPv6 address, but of course these two addresses are connected to the VPN IP address I've been assigned. This tells me that there is no DNS leaking going on. I've only witnessed this situation when using AirVPN's servers and the Eddie client (as opposed to, for example, using another VPN service and their connection client). I attached a screencap to show what I am talking about: So, after my long-winded explanation of the issue, here's my question. Because it is showing two DNS servers, and one being a IPv6 server, is this a potential leak for IPv6 traffic since the test is able to connect to this particular server? Is it also possible for it to be a DNS leak, even though it is obviously associated with VPN server that gave me this particular IP address? I'm wondering about this simply because when I use other VPN providers and check ipleak.net, it only shows the one DNS server (IPv4) with the same IP address as the one issued to me by the VPN server. This would lead me to believe that my VPN connection is correctly blocking leaks and using DNS servers provided by the VPN service. Any help with this would be greatly appreciated, and of course, please don't hesitate to ask if I need to clarify any information.
×
×
  • Create New...