Jump to content
Not connected, Your IP: 216.73.216.49

Leaderboard


Popular Content

Showing content with the highest reputation on 10/28/20 in all areas

  1. 1 point
    Flx

    ANSWERED Unable to Connect

    Disable IPv6 and try connecting IPv4. Other than this disable/uninstall the TAP-adapter and let Eddie install a new one.
  2. 1 point
    whiskey_76

    Won't Connect at checking Ipv6

    Toggle layer IPV6 to blocked. On the second menu just switch it to IPV6 blocked and it should connect?
  3. 1 point
    Auro

    Can't use network lock with ipv6 disabled

    Same problems here. I see many people have this problem. And I see that no one from AirVPN team is replying to any of these complaints. Very disappointing, we paid money for this (faulty) service.
  4. 1 point
    I have the same issue. Sequence of events/tests: - Decided to finally use "Network Lock" - Result was endless loop of "Checking IPV6 Routing" -> "Disconnecting" -> "Connecting" - Read Forum suggestion to Block IPV6 altogether. - That worked, but then utorrent just sat there doing nothing - Disconnected and disabled Network Lock and then reconnected and utorrent worked fine - Allow lan/private has always been checked. - Restored IPV6 settings to normal (default) and still works fine IF "Network Lock" is not engaged. - Eddie Version 2.16.3 on Windows Vista. Otherwise, everything works great. Using UDP on port 443 on entry-IP 3 (tls-script) avoids the ISP throttling I consistently see on many other protocol/port combinations, I just had a torrent download peak at 80% of the maximum unprotected speed, using those settings - with another PC on the same LAN on AirVPN showing a stream as well. So, great performance if you get every set just right. UPDATE: This morning I had the same endless loop of "Checking IPV6 Routing" -> "Disconnecting" -> "Connecting" with Network Lock OFF. So, I again changed to IPV4 only in Network Settings and everything is fine again. I understand the eventual need for IPV6 for the address space, and that businesses are changing first - but is there currently any compelling need for home users to have support for IPV6? ==> In my home LAN, I have my devices set to use static IPV4 addresses (which is needed for two minor applications that I use in my home network). I'm wondering if this is preventing IPV6 from working correctly? 2nd UPDATE: I discovered that on my PC that solely runs utorrent, if the AirVPN server disconnectes and reconnects, then in-between, individual utorrent connections will then all connect to the unprotected Internet connection, and when AirVPN reconnects, it doesn't affect the utorrent connections, which are now connected to the unprotected Internet connection. So, Network Lock is a must for torrent program use. So, I closed utorrent, and set Eddie to IPV4 Only, and turned Network Lock back on, and this time, everything worked fine. I wonder if the problem is on the server end? An intermittent problem? Something just fixed? Also, as a newbie, I cannot post more today, so I also wanted to mention that Anonymity Check now says "VPN fingerprint MTU 1397". Is this a result of tls-script ? (wild guess)
  5. 1 point
    Skicoach

    Won't Connect at checking Ipv6

    ... also had to block Ipv6 Never had a problem until installing eddie yesterday.
  6. 1 point
    Spinone

    Won't Connect at checking Ipv6

    I have the same problem. I can connect to some servers, but others hang at "Checking route IPv6". The logs show cURL timing out after 20000ms, three times, before declaring "Checking route IPv6 failed" and disconnecting. In options/Networking, I had the Layer IPv6 combo dropdown set to "Inside tunnel if supported, otherwise blocked" and had the "Switch to Block if issue is detected" checked. By setting the Layer IPv6 combo dropdown to "Block", I can connect to servers which fail with the default settings active. All other selections result in the "Checking route IPv6 failed" error. Something's not right - it would be nice to know what causes this. Sample log excerpt and system report attached. eddie-ipv6-timeout.txt eddie-system-report.txt
  7. 1 point
    I think you are misunderstanding the problem. You have to activate the network lock before you connect. You cannot activate it after. It seems as if you thought I was activating it after I connected and then it dropped my current internet connections. The purpose of the network lock is to prevent "leaks" as people call them, sure. But this is between the time when you lose a connection and it reconnects. Again, that is not the issue. Maybe it's my fault. I may have not been specific enough. I will go through the steps. 1. I start with a fresh computer, just turned it on. 2. I start the Eddie program. 3. I select "Activate Network Lock". 4. I select "Connect to a recommended server". 5. It connects somewhere and it shows the upload/download speed screen. 6. No internet! It is only supposed to have no internet if it lost its connection. I have no internet all of the time. I used to do the above steps and I could immediately access the internet like normal and programs could do the same. If I lost connection to a server via Eddie, I would lose all internet until it connected to a new server. This is how the lock prevents the leaks. But it is supposed to allow me to get on the internet when I am connected to a server. It doesn't. My understanding is the above suggestions are basically ways to bypass the tunnel created by Eddie. I don't want to do that. As you said, that's the point of the network lock. Right now, the GUI shows that everything is working fine and the tunnel created with the VPN is open and active. Not mine. No traffic in or out, ever. Now, as I previously stated, this is a clean install of 2.15.2. I have not modified any settings what so ever. I do not know what version I was using before, but I know it was not this one. I never changed any settings with that one and it just worked. With this new version, do I have to change settings somewhere? I hope this clears things up. Thanks
×
×
  • Create New...