Eddie Desktop 2.21 beta released

[OpenSourcerer 1435]

33 minutes ago, Breeze said:

Is there any information on how to opt-in to the AirVPN beta? 

There is none yet.

[Staff 9971]

@Breeze

Hello!

Thank you! Access activation to Wireguard beta testing will be available in the "Client Area". We will have more information on a definite date very soon, we're still working on it. Announcement will follow in "News" forum.

Can you also tell us your Linux distribution name and version? If you run Eddie beta from other packages (not the AppImage) do you see the same crash?

Kind regards
 

[Breeze 2]

2 hours ago, Staff said:

@Breeze

Hello!

Thank you! Access activation to Wireguard beta testing will be available in the "Client Area". We will have more information on a definite date very soon, we're still working on it. Announcement will follow in "News" forum.

Can you also tell us your Linux distribution name and version? If you run Eddie beta from other packages (not the AppImage) do you see the same crash?

Kind regards
 

Great to hear! I will keep an eye on the announcements. 

Linux distribution is Solus, this is also the reason why I use the AppImage (deb, rpm, ... etc. are not supported on Solus).
Version is 4.3, but it is a rolling distribution so that doesn't mean much. 

[y0wl 0]

Yes, very much so. This was performed to get Eddie 2.21.1 working with Hummingbird 1.1.2 on two different Mac OS machines. I had attempted to use Hummingbird 1.1.1 back in late January with the most current Eddie version at that time and that had also failed.. the infinite loop of trying to connect, disconnects, retry in three seconds.

One system was a fresh (erased drive, restored from Apple's servers with no user data ported, migrated, or time machine'd) Mojave install upgraded to Catalina, the other was a similarly fresh install of Big Sur.

[Staff 9971]

@y0wl

Hello!

Thank you. It's an Eddie 2.21.1 problem, so this is not the proper thread, and we are moving your messages to the following thread:
https://airvpn.org/forums/topic/49638-eddie-desktop-221-beta-released/

Please continue there. We will also make sure that developers get your report.

Kind regards

 

[schwede 0]

Hi,

from time to time airvpn crashes.
its just version 2.21.1 beta and after that a reconnect ist not possible.
just when i turn on on dns in the network adapter.

[Staff 9971]

We deployed a new release which fixes issues with WireGuard (for a public beta testing) and some minor bugs.
Other issues reported in this thread are under investigation.

Version 2.21.2 (Wed, 27 Oct 2021 12:29:20 +0000)

• [bugfix] [all] WireGuard beta support
• [change] [all] Whitelist->Allowlist, Blacklist->Denylist
• [bugfix] [all] Preferences -> Routes error

[takkaria 4]

Getting an error on 2.21.2beta while connecting with nftables network lock, iptables works.
Running 5.14.13 kernel on arch.

E 2021.10.27 19:09:01 - Fatal error occured, please contact Eddie support: Exception: nft issue: exit:1; out:^                       ~~; err:Error: syntax error, options must be specified before commands
E 2021.10.27 19:09:01 -     /usr/sbin/nft list ruleset -n -a -   at Eddie.Core.Elevated.Command.GetSyncResult () [0x00012] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.Elevated.IElevated.DoCommandSync (Eddie.Core.Elevated.Command c) [0x00046] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.Elevated.IElevated.DoCommandSync (System.String command, System.String key1, System.String val1, System.String key2, System.String val2, System.String key3, System.String val3, System.String key4, System.String val4) [0x00051] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Platform.Linux.NetworkLockNftables.DeallowInterface (System.Net.NetworkInformation.NetworkInterface networkInterface) [0x00021] in <112d05afc4f7424db0fe6e6acf375adc>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.NetworkLockManager.DeallowInterface (System.Net.NetworkInformation.NetworkInterface networkInterface) [0x00008] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.ConnectionTypes.IConnectionType.OnClose () [0x0001c] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.ConnectionTypes.OpenVPN.OnClose () [0x00000] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0
E 2021.10.27 19:09:01 -     at Eddie.Core.Session.OnRun () [0x00a5e] in <3cba6f0223fb4ba6b7aa1a17c192b214>:0

[OpenSourcerer 1435]

1 hour ago, takkaria said:

Getting an error on 2.21.2beta while connecting with nftables network lock, iptables works.

Can confirm.

[Clodo 176]

18 hours ago, takkaria said:

Getting an error on 2.21.2beta while connecting with nftables network lock, iptables works.
Running 5.14.13 kernel on arch.

Ouch... Debian nft accepts options also after command, Arch does not...  this will be fixed today, time to redeploy.

Released hotfix without changing version, only Linux builds changed. @OpenSourcerer and @takkaria please redownload. Thx,

[takkaria 4]

Works, thanks for the quick fix!

[puff-m-d 31]

Hello,

I can not get 2.21.2 to work on my Windows 11 machine. I had to rollback to version 2.21.1 which does work (which I assume this version does not work with the WireGuard beta testing).
Logs attached...

 

Edited ... by puff-m-d
Issue fixed: Deleted logs....

[bob1324 1]

Hi,

I also have an Unexpected: NetLock WFP rule.
Windows 10 pro and 2.21.2beta.error eddie.txt

[autone 4]

Version 2.21.2 has a massive memory leak when using wireguard after some long periods. I had high CPU usage and it was using 10GB ram. This is on Windows 10.

[Xirinacs 1]

It works perfectly for me in Windows 10 (without WireGuard) and so far I have not experienced any problems.
But I had to install Eddie with administrator privileges.
Regards

[xaeiou 1]

Quote

We deployed a new release which fixes issues with WireGuard (for a public beta testing) and some minor bugs.
Other issues reported in this thread are under investigation.

Version 2.21.2 (Wed, 27 Oct 2021 12:29:20 +0000)

• [bugfix] [all] Preferences -> Routes error

I confirm this fixes the problem with adding routes I reported.

[frffre 0]

On 10/28/2021 at 1:48 PM, Clodo said:

Ouch... Debian nft accepts options also after command, Arch does not...  this will be fixed today, time to redeploy.

Released hotfix without changing version, only Linux builds changed. @OpenSourcerer and @takkaria please redownload. Thx,

Hi

This same error occurs for me on a fresh Debian 11 install with a package version installed today, so it should have the hotfix. Seems like there is no version that works easily on Debian 11 currently because earlier versions have the libappindicator1 dependency which doesn't exist on it.

[Maggie144 12]

Since this new ping engine I get huge latencies on my favourite servers. In the beginning it's only some, but after Eddie is running for 30min all goes up to 4-digits milliseconds..

I tried different protocols for connecting, but it all ends up like this

[rootinthemood 0]

On 10/27/2021 at 7:21 PM, takkaria said:

Getting an error on 2.21.2beta while connecting with nftables network lock, iptables works.
Running 5.14.13 kernel on arch. 

It's the other way around here.
Getting an exception trying to network lock with iptables. After Installing nftables and enabling it in Eddie, it works again.
Linux 5.15.4 on arch Edited ... by rootinthemood

[DarkWrath 1]

Request: On Windows, similar to the OpenVPN adapter, please add a "do not remove every time" option for the Wireguard network adapter.

This will allow me to use policy routing using the MAC address of that adapter. If that's not possible, at least re-use the same MAC address for the adapter.

This works well for the setup I already have for OpenVPN, so similar functionality will help in easy transition to using WireGuard.

Thanks.

[encrypted 13]

So what's the advice for Debian + offshoots users when Eddie complains about NFT when booting to latest kernel (5.15.5), besides simply downgrading the kernel?


More details:

Running Mint 20 (based on Ubuntu 20.04 LTS which is based on Debian bullseye/sid) with latest mainline kernel for recent hardware support, until recently kernel 5.14.x and Eddie 2.21.1 worked just fine. Apart from the vanished panel indicator for Eddie due to Debian deprecating "libappindicator1".

With Debian and derivatives lagging in nftables adoption (the latest version available is 0.9.3-2 from Dec 2019), only iptables was available/installed and selected automatically for Network Lock.

As the mainline Linux kernel 5.14.21 became EOL I installed and booted into kernel 5.15.5  (still using Eddie 2.21.1) but it would give an iptables error and Network Lock wasn't enabled.
Seeing issues here (previous page) with Debian 11 and Arch, I installed the latest Eddie 2.21.2 (with some 'hotfix' by @Clodo included) as well as that (old) nftables package from repos and now I can boot into Linux kernel 5.15.6 with Network Lock activating.
However I now get frequent "Exception: nft issue: exit:1; err:Error: syntax error, unexpected rule, expecting string" warnings plus one case of "Fatal error occured, please contact Eddie support: Object reference not set to an instance of an object -   at Eddie.Platform.Linux.NetworkLockNftables.DeallowInterface" (similar to errors mentioned earlier in the thread).

Kernel 5.15.x (now mainline) appears to have changed something to make iptables fail under Eddie. The more 'progressive' distros can apparently switch to using nftables, but with more conservative distros (Debian, Mint, Ubuntu 20.04 LTS) nftables might not be up to the task.

Is this something AirVPN can fix with Eddie, or is the solution, for now, to simply downgrade from the mainline kernel (5.15.x) to stock 5.13.x (HWE) and hope for the best?


 

Edited ... by encrypted
Added details

[stretton 0]

On 12/1/2021 at 3:36 PM, encrypted said:

So what's the advice for Debian + offshoots users when Eddie complains about NFT when booting to latest kernel (5.15.5), besides simply downgrading the kernel?


More details:

Running Mint 20 (based on Ubuntu 20.04 LTS which is based on Debian bullseye/sid) with latest mainline kernel for recent hardware support, until recently kernel 5.14.x and Eddie 2.21.1 worked just fine. Apart from the vanished panel indicator for Eddie due to Debian deprecating "libappindicator1".

With Debian and derivatives lagging in nftables adoption (the latest version available is 0.9.3-2 from Dec 2019), only iptables was available/installed and selected automatically for Network Lock.

As the mainline Linux kernel 5.14.21 became EOL I installed and booted into kernel 5.15.5  (still using Eddie 2.21.1) but it would give an iptables error and Network Lock wasn't enabled.
Seeing issues here (previous page) with Debian 11 and Arch, I installed the latest Eddie 2.21.2 (with some 'hotfix' by @Clodo included) as well as that (old) nftables package from repos and now I can boot into Linux kernel 5.15.6 with Network Lock activating.
However I now get frequent "Exception: nft issue: exit:1; err:Error: syntax error, unexpected rule, expecting string" warnings plus one case of "Fatal error occured, please contact Eddie support: Object reference not set to an instance of an object -   at Eddie.Platform.Linux.NetworkLockNftables.DeallowInterface" (similar to errors mentioned earlier in the thread).

Kernel 5.15.x (now mainline) appears to have changed something to make iptables fail under Eddie. The more 'progressive' distros can apparently switch to using nftables, but with more conservative distros (Debian, Mint, Ubuntu 20.04 LTS) nftables might not be up to the task.

Is this something AirVPN can fix with Eddie, or is the solution, for now, to simply downgrade from the mainline kernel (5.15.x) to stock 5.13.x (HWE) and hope for the best?


 

I am on pop-os on kernel 5.15.5 and I am getting the error message exception: iptables don't reply , probabily kernel modules issue.

[sunisland 0]

I have install 2.21.2 today and i have this issue. i came from 2.20 final. Can someone help me?

Eddie_20211208_234521.txt

Edited ... by sunisland

[Clodo 176]

On 10/30/2021 at 2:02 PM, autone said:

Version 2.21.2 has a massive memory leak when using wireguard after some long periods. I had high CPU usage and it was using 10GB ram. This is on Windows 10.

This is confirmed,
Current 2.21.2 (only Windows, only with WireGuard) crasheds after many hours (>8), this issue will be fixed in the next version, as soon as possible.

[DarkWrath 1]

On Windows 10 x64, using a CPU with AES-NI:

Would it be possible to update the WireGuard libraries to the latest version? I'm seeing large CPU usage when I enable WireGuard support, which I attribute to the user layer driver being used right now.

I can't enable the experimental kernel driver, because the version is too old (0.3.x). It needs at least 0.4.x before that can be enabled. The current stable version is 0.5.2 for windows.

I can't simply replace the WireGuard driver dll, as Eddie uses the embedded version of WireGaurd.

In the current version, there's support to run external OpenVPN client, which allows flexibility in this kind of situation. For Example, I've used it in the past to make use of newer OpenVPN features before it was introduced into the native version of Eddie.

So, the second feature request is to allow for a similar flexibility of running an external WireGuard client, so it's easier to use newer features.