ANSWERED DNS leaks from Mint, and conflicting data from Ipleak and Browserleaks

[Tavvy 0]

Just returned to Air after some time away. Running Linux Mint on an old macbook pro; using Air via Eddie I get DNS leaks. ipleak shows only one server, that of Airvpn, but Browserleaks shows two, the same Air server shown by ipleak and another based in the country I'm in. Have waded through forum threads, which has just wasted my time. I need to sort this pronto, anybody got any quick fix ideas...and an insight on why the conflicting data?

[Staff 9972]

Hello!

Please test Eddie 2.24: https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/

Eddie features support with proper DNS management for every systemd-resolved (a ramshackle systemd component that would have the ambition to offer name resolution to applications) mode from version 2.23.2. Previous versions do not handle correctly a specific systemd-resolved working mode which will cause DNS leaks. If you're running some older Eddie version, including the current stable release, and your Mint has systemd-resolved running and working in on-link mode bypassing /etc/resolv.conf, we may have a rational explanation of the situation. However, the discrepancy between https://ipleak.net and the web site you mention remains unexplained.

Kind regards

[Tavvy 0]

Eddie 2.24 installed but fails to start. Start fail notice screenshot attached

[Staff 9972]

@Tavvy

This error related to the virtual interface tun0 did not occur with Eddie 2.21.8, can you confirm?

Please feel free to add your message (or we can do it for you) to the following thread:
https://airvpn.org/forums/topic/57401-eddie-desktop-224-beta-released/
where bugs discovered by the community are reported, thank you very much.

In any case we will highlight your report to developers.

Kind regards
 

[Tavvy 0]

The problem only presented with the newly installed beta. The message can be added to the beta thread for their information.

[Staff 9972]

9 hours ago, Tavvy said:

The problem only presented with the newly installed beta. The message can be added to the beta thread for their information.

Hello!

Does the problem persist with the new 2.24.1 (upgrade if you haven't already done so), released after you posted the issue? If it persists, please feel free to add on the mentioned thread your report.

Kind regards
 

[Tavvy 0]

Upgraded to 2.24.1, installed, started, logged on, no leaks. Gracias