Mac OS X Mavericks DNS leakage

[gonashimusha 0]

Hi

 

I tried accessing some torrent sites in the UK yesterday while using AirVPN (Eddie client, connected to Atik, Netherlands server) and they still seemed to be blocked "by the high court" which led me to believe that somehow the VPN isn't working on that there's a leak as it's seeing that I'm in the UK. So I went to https://www.dnsleaktest.com/ and it says I'm in the Netherlands, which seems correct as that's the server I've connected to but then when I do the standard test, it shows me 4 servers with my country and ISP provider. I have enabled Network Lock at startup in the preferences but that doesn't seem to change anything. Is there something else I should be doing? Sorry I'm new to this. Why would I not be able to access these sites if I'm connected to the Netherlands where they're not blocked?

 

Thanks.

 

EDIT: El Capitan, not Mavericks!

[Keksjdjdke 35]

Mavericks is no longer supported by Apple and you no longer get security updates you should update to macOS Sierra and see if the issue still occurs.

HT207922

[gonashimusha 0]

Sorry I meant El Capitan, not Mavericks..!

[Keksjdjdke 35]

  On 8/20/2017 at 1:54 PM, gonashimusha said:

Sorry I meant El Capitan, not Mavericks..!

Ok, install the latest Eddie beta download. Make sure Eddie is closed, delete the whole .airvpn folder here  /Users/"Your Username"/.airvpn

Then open Eddie and sign in, enable network lock and test the ons leak test again.

[gonashimusha 0]

It is now telling me "Unable to start PF firewall". Any idea what the issue could be? I followed your steps in reinstalling. Thanks for the help by the way!

[Keksjdjdke 35]

  On 8/22/2017 at 7:37 PM, gonashimusha said:

It is now telling me "Unable to start PF firewall". Any idea what the issue could be? I followed your steps in reinstalling. Thanks for the help by the way!

Are you running Eddie 2.13.5? If not download and install it here https://eddie.website/download/?platform=macos&arch=x64&ui=ui&format=installer.pkg&version=experimental&r=0.5254369456023126

See if that fixes your issue.

[Johmcalistic 0]

May post in your thread? I hope so. =) Related issue.

 

If it helps at all I'm using Disable WebRTC add on for Firefox and seems to have taken care of the leak, at least for browsing.

 

I also get "Unable to start PF firewall" when I activate the "Network Lock" feature. Eddie 2.13.5, El Capitan.

 

Also, if I try to connect over Tor within the Eddie prefs (tests fine) it will freeze upon trying to save the preferences and I have to force quite it.

 

I'd like to get the Network Lock working asap, and eventually sort out the Tor issue, should I need it.

 

Thanks

[Keksjdjdke 35]

  On 8/23/2017 at 4:42 AM, Johmcalistic said:

May post in your thread? I hope so. =) Related issue. If it helps at all I'm using Disable WebRTC add on for Firefox and seems to have taken care of the leak, at least for browsing. I also get "Unable to start PF firewall" when I activate the "Network Lock" feature. Eddie 2.13.5, El Capitan. Also, if I try to connect over Tor within the Eddie prefs (tests fine) it will freeze upon trying to save the preferences and I have to force quite it. I'd like to get the Network Lock working asap, and eventually sort out the Tor issue, should I need it. Thanks

Update to macOS Sierra and Make sure Eddie is closed, delete the whole .airvpn folder here  /Users/"Your Username"/.airvpn

Then open Eddie and sign in, enable network lock and test the ons leak test again.

[Johmcalistic 0]

  On 8/23/2017 at 6:12 AM, Keksjdjdke said:

Update to macOS Sierra and Make sure Eddie is closed, delete the whole .airvpn folder here  /Users/"Your Username"/.airvpn

I'd really like to avoid Sierra. It would be a shame to update to Sierra, screw up a stable environment for my other purposes, just to find out I still can't save preferences and or activate the Network Lock feature. The client is working fine besides those two issues and I'd like to try alternative solutions.

 

It might help to know why the client is "Unable to start PF firewall", and what that means, for example. If it helps I'm using Little Snitch 3.7 with built in OS firewall off.

[Keksjdjdke 35]

  On 8/23/2017 at 4:48 PM, Johmcalistic said:

 

  On 8/23/2017 at 6:12 AM, Keksjdjdke said:

Update to macOS Sierra and Make sure Eddie is closed, delete the whole .airvpn folder here  /Users/"Your Username"/.airvpn

I'd really like to avoid Sierra. It would be a shame to update to Sierra, screw up a stable environment for my other purposes, just to find out I still can't save preferences and or activate the Network Lock feature. The client is working fine besides those two issues and I'd like to try alternative solutions.

 

It might help to know why the client is "Unable to start PF firewall", and what that means, for example. If it helps I'm using Little Snitch 3.7 with built in OS firewall off.

macOS Sierra is stable. You might want to disable/uninstall little snitch and see if Eddie works correctly.

[Johmcalistic 0]

Sorry, what I mean by "stable environment" is stable for my old soft I depend on and I cant afford to upgrade at the moment.

 

I tried taking LS out of the equation, still get the error.

Thanks for trying to help by the way.

 

Edit: Interesting. I decided to try an older version of Eddie, 2.12.4 and Network Lock activates fine. I'll give it shot and see how this version does.

[gonashimusha 0]

I still seem to have the same problem after updating to Sierra and the latest version of eddie.. the "Unable to start PF firewall" is gone but the leak is still there.. any idea what else it could be?

[Keksjdjdke 35]

  On 8/24/2017 at 5:30 PM, gonashimusha said:

I still seem to have the same problem after updating to Sierra and the latest version of eddie.. the "Unable to start PF firewall" is gone but the leak is still there.. any idea what else it could be?

1.Update to the latest Eddie beta download.

2.Make sure Eddie is closed, delete the whole .airvpn folder here  /Users/"Your Username"/.airvpn

 

3.Then open Eddie and sign in, enable network lock and test the ons leak test again.