Not connected, Your IP: 216.73.216.124
Online: 38768 users - 484327 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
- Today
-
-
-
-
-
-
-
-
-
- Yesterday
-
I want to run this by you guys because I have a small project to complete this weekend - hopefully - and I am a little sketchy on it. Lets say I use Airvpn Android (wondering if version 4 is production ready yet even though its beta) on my flagship Samsung. I also have openvpn setup and working on my router for LAN access when I am not at home ( Also DDNS is setup and working as well). I currently connect to it using an app --- not related to airvpn at all. I am looking for a slick way to simply copy a certificate from/to the router so that AIRVPN can do all I need. To help you picture my quest: I want to be able to connect to my home router while I am away so that my security system can send alerts to me from LAN. I will NEVER give my cameras and security devices internet access for any reason --- only LAN. So then in my perfect quest the security app on my Android will receive alerts if something happens because the camera system will see the Android as being on LAN for that ONE app. I do NOT want to walk around having to use my router VPN for all my Android activities. Its too slow being openvpn and only has a midrange chipset, which is far inferior to my flagship Android. Hope this makes sense. So then I am envisioning a form of split tunneling. I don't know if I could simply use the OpenVPN connect app I am using now while using Airvpn for other things/apps. Another complication is that I love Wireguard on my Android but my stupid router vpn is limited to openvpn only. I will replace it someday but life is expensive! Is there any chance I could somewhat easily accomplish what I need? Any links or suggestions to simplify my seeing the needed scheme? ps - I realize and can manually keep clicking things on and off to connect but I want my security system to reach out 100% of the time and yet NO router being used by my Android otherwise just full on Airvpn Android.
-
I'm having this exact issue on linux mint but with one odd exception. I've got Eddie installed on two different pc's, my main pc runs has an AMD processor/gpu and Eddie runs just fine on it, no lag or visual glitches at all. But on my living room pc, which is a repurposed HP elitedesk with an Intel processor/gpu, it runs exactly like you're experiencing.
-
-
-
-
At the top of every AirVPN page is a line that includes the name of the server I am using. For example, currently, this is Chow. It would be handy if a click on this name took you to the page of statistics for that server. Currently, it takes you to the client area instead. eg: https://airvpn.org/servers/Chow/ and not https://airvpn.org/client/
-
UK Infrastructure upgrade to 10 Gbit/s full duplex
ASiC666 replied to Staff's topic in News and Announcement
Nice one I was getting better speeds from servers abroad than the UK ones (I'm in the UK) This upgrade will hopefully sort it out! Thanks! -
-
I have tired 100+ times—Taiwan VPN is not accessible on my Ubuntu! Please resolve, thanks!
-
-
-
Hello! We are very pleased to inform you that we are taking the necessary steps to completely renovate our infrastructure in the United Kingdom. The current servers will be dismissed and replaced by six 10 Gbit/s servers with newer and much more powerful hardware. Each 10 Gbit/s server will be connected to a full duplex 10 Gbit/s dedicated line and port. Each new server replaces 2.5 current 1 Gbit/s servers in order to increase remarkably the available bandwidth per connected client. At the end of the upgrade, UK will offer a theoretical peak of 60 Gbit/s (full duplex) instead of the current 15 Gbit/s, through adequately powerful servers. According to our plan, three servers will be located in London and three in Manchester. The new servers will start operations around 19-22 February 2026. Current 1 Gbit/s servers will cease operations on the night between 28 February and 01 March (UTC). Any plan changes and/or delays will be communicated promptly. Kind regards & datalove AirVPN Staff
- Last week
-
I recently downloaded Eddie version 2.24.6 for Windows 7 - 32 Bit. And installed it, but after installing it my computer crashed and now whenever I try to start Eddie (GUI) I get the following error: "Unable to obtain elevated privileges (required): Unable to Start (an existing connection was forcibly closed by the remote host)" Then when I click OK, Eddie closes. This occurs with both the installed version and the portable version. This has continued to occur even through reboots and power offs. If I don't start Eddie, I do not have any Internet access at all - so it seems like the "Network Lock" is active. What can I do? -
-
-
-
-
-
-
What is "batch mode" ? How to rotate servers?
Lizzzaa replied to MikeHawkener's topic in Eddie - AirVPN Client
Hello, please help. The configuration files on OpenVPN 10 iOS aren't working. AirVPN_Asia_TCP-443-Entry3.ovpn -
https://www.phoronix.com/news/OpenVPN-2.7-Released Quick snippet from the article: "The OpenVPN 2.7 user-space can also work with the OpenVPN DCO kernel module for data channel offload that was upstreamed into the Linux 6.16 kernel in enhancing the OpenVPN performance. The OpenVPN DCO kernel driver performance yields some nice gains as the project recently showcased."
-
-
ANSWERED slskd port forwarding
pulmonary5024 replied to p1pb0y's topic in Troubleshooting and Problems
Could you share your docker-compose please? -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
This is very helpful, because knowing that the internal VPN IP doesn't change, not the exit IP but the internal IP, means that I can create firewall rules blocking everything but that internal IP. That can act as a secondary kill-switch. -
ANSWERED How to basic configuring Eddie + qBitorrent ?
MikeHawkener replied to Christophe95870's topic in Eddie - AirVPN Client
@Staff thanks for the explanation. that makes a lot more sense. I almost always use the default protocol which is Wireguard (for me at least) so I noticed this address was always the same (at least for the servers I've used). I've only used openvpn once or twice so far and noticed that was the only time the VPN IP was different. but probably only once since I don't remember having to change the VPN IP for openvpn (or maybe I was lucky getting the same daemon on the same server. idk) -
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
ANSWERED How to basic configuring Eddie + qBitorrent ?
Staff replied to Christophe95870's topic in Eddie - AirVPN Client
@thetechnerd @MikeHawkener Hello! Some additional related information that may be valuable for you both. When you run OpenVPN: the assigned VPN IP address depends on the daemon of the VPN server you connect to. Each one lives in a separated /24 subnet somewhere inside 10.0.0.0/10 When you run WireGuard: WireGuard lacks any DHCP feature it lives in a unique, gigantic 10.128.0.0/10 subnet throughout the whole AirVPN infrastructure the VPN IP address of each node is linked permanently to the node's key and it is unique in the whole WireGuard address space thus you will have always the same VPN IP address when you use the same key and you don't renew it, no matter which VPN server you connect to Kind regards -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
Oh really?! That's great to hear that the internal 10.x.x.x session IP is unique to the user and not the session, despite its name. Thanks @MikeHawkener! -
-
the help documentation just says "for non-interactive mode" I was wonder if it might be a feature that batch uses different servers? like rotates them every certain amount of time so you don't use the same server over a long period time ? Is there any feature in Eddie that allows this?
-
ANSWERED How to basic configuring Eddie + qBitorrent ?
MikeHawkener replied to Christophe95870's topic in Eddie - AirVPN Client
I would recommend it. I prefer the private IP address over the interface, though I'm on macos so it shows as a `utun#` number. I found that the IP has higher precedence than the specific utun. So often between boots, this IP will be the same but the `utun` number might change (e.g. `utun2` or `utun4`) depending on other services that might create their own utuns (probably not for Windows as it just shows 'Eddie'). I set both utun and IP, but if the utun is different but IP is correct, it still runs fine. Plus the private IP will (virtually) always be unique. but I think if you change LANs/networks a lot from say a laptop, then theoretically I think there is a tiny chance that LAN could also assign that local IP (I could be mistaken) also this IP only seems to change based on whether one is using wireguard or openvpn. I suspect this might be how AirVPN implements VPN servers for their clients. perhaps AirVPN usually tries to provide the same private IP to a particular customer regardless of the server as long as its the same protocol (Wireguard, openvpn). and the other protocol will try to use its own IP too. perhaps the purpose is for convenience so the customer wouldn't have to frequently change these settings in their apps etc. Just a hunch though -
But, I've just started recently...)
-
Running a tor entry/middle relay over airvpn
moejoe replied to Brisbaneforhound's topic in General & Suggestions
Is it allowed to tunneling an tor exit node over air vpn ? Asking also @Staff regards -
ANSWERED How to basic configuring Eddie + qBitorrent ?
thetechnerd replied to Christophe95870's topic in Eddie - AirVPN Client
Apologies for my ignorance, but is it not advisable to bind the optional IP address to found in the client area > session IP to qbittorrent just in case? I mean, it is a local 10.x.x.x address, and doesn't seem to change i I'm connected to the same server. Am I wrong? -
-
-
-
BettyIsBoop reacted to a post in a topic:
Debian Trixie: apt update fails for Eddie repo since 2026-02-01 (SHA1 rejected) ...
-
I just wanted to be helpful here in case anyone reading this thread is sideloading their ONN Google TV device updated to Android 14. 3.3.0 is running flawlessly and with the correct VPN server selection I never see a "spinning circle" or any hesitation at all. It fully executes my settings when I click on the Eddie app. I do NOT have it configured for device bootstrap but when I want the VPN its one click and five seconds later its rock solid good to go. I am reading about the version 4 series and may move there soon. Its tough to leave perfection, which is what 3.3.0 is for me on my end. .02
-
After updating any attempt to creat a vpon tunnel fails. I reinstalled Eddie, and I am out of ideas. Generated: Sat, 07 Feb 2026 19:41:09 +0000 Expiration: Mon, 09 Mar 2026 19:41:09 +0000 DELETE NOW Eddie System/Environment Report - 07.02.2026 - 19:40 UTC Eddie version: 2.24.6 Eddie OS build: linux_x64 Eddie architecture: x64 OS type: Linux OS name: Fedora Linux OS version: 43 (Workstation Edition) OS architecture: x64 Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 OpenVPN: 2.6.17 - OpenSSL 3.5.4 30 Sep 2025, LZO 2.10 (/usr/sbin/openvpn) Hummingbird: Not available WireGuard: 1.0.0 SSH: OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025 (/usr/bin/ssh) SSL: 5.75 (/usr/bin/stunnel) Profile path: /home/user/.config/eddie/default.profile Data path: /home/user/.config/eddie Application path: /usr/lib/eddie-ui Executable path: /usr/lib/eddie-ui/eddie-ui Command line arguments: (1 args) path.resources="/usr/share/eddie-ui" Network Lock Active: No Connected to VPN: No OS support IPv4: Yes OS support IPv6: Yes Detected DNS: 127.0.0.53 Test DNS IPv4: Ok Test DNS IPv6: Ok Test Ping IPv4: 48 ms Test Ping IPv6: Failed Test HTTP IPv4: Error: Fetch url error:Could not connect to server Test HTTP IPv6: Error: Fetch url error:Could not connect to server Test HTTPS: Ok ---------------------------- Important options not at defaults: login: (omissis) password: (omissis) remember: True key: (omissis) servers.allowlist: 04c8003cc011ead147020baa01cb5301b409a49bddea1291127c67e1b156b6ce proxy.mode: none ---------------------------- Logs: . 2026.02.07 20:39:25 - Eddie version: 2.24.6 / linux_x64, System: Linux, Name: Fedora Linux, Version: 43 (Workstation Edition), Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 . 2026.02.07 20:39:25 - Command line arguments (1): path.resources="/usr/share/eddie-ui" . 2026.02.07 20:39:26 - Raise system privileges . 2026.02.07 20:39:31 - Collect network information . 2026.02.07 20:39:32 - Reading options from /home/jens/.config/eddie/default.profile . 2026.02.07 20:39:34 - OpenVPN - Version: 2.6.17 - OpenSSL 3.5.4 30 Sep 2025, LZO 2.10 (/usr/sbin/openvpn) . 2026.02.07 20:39:34 - SSH - Version: OpenSSH_10.0p2, OpenSSL 3.5.4 30 Sep 2025 (/usr/bin/ssh) . 2026.02.07 20:39:34 - SSL - Version: 5.75 (/usr/bin/stunnel) . 2026.02.07 20:39:35 - Service systemd-resolved restarted I 2026.02.07 20:39:40 - Ready . 2026.02.07 20:39:42 - Collect information about AirVPN completed I 2026.02.07 20:39:44 - Session starting. . 2026.02.07 20:39:44 - Activation of Network Lock - Linux iptables-nft I 2026.02.07 20:39:45 - Checking authorization ... ! 2026.02.07 20:39:45 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:45 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:45 - WireGuard > Setup start . 2026.02.07 20:39:45 - WireGuard > Setup complete . 2026.02.07 20:39:45 - WireGuard > Setup interface . 2026.02.07 20:39:46 - WireGuard > Received first handshake . 2026.02.07 20:39:46 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:47 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:47 - Disconnecting . 2026.02.07 20:39:47 - WireGuard > Stop request received . 2026.02.07 20:39:47 - WireGuard > Stopping . 2026.02.07 20:39:47 - WireGuard > Completed . 2026.02.07 20:39:47 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:47 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:48 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:39:48 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:39:48 - Service systemd-resolved restarted . 2026.02.07 20:39:48 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:39:48 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:39:48 - Collect network information . 2026.02.07 20:39:48 - Connection terminated. I 2026.02.07 20:39:51 - Checking authorization ... ! 2026.02.07 20:39:52 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:52 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:52 - WireGuard > Setup start . 2026.02.07 20:39:52 - WireGuard > Setup complete . 2026.02.07 20:39:52 - WireGuard > Setup interface . 2026.02.07 20:39:53 - WireGuard > Received first handshake . 2026.02.07 20:39:53 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:53 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:53 - Disconnecting . 2026.02.07 20:39:54 - WireGuard > Stop request received . 2026.02.07 20:39:54 - WireGuard > Stopping . 2026.02.07 20:39:54 - WireGuard > Completed . 2026.02.07 20:39:54 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:54 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:39:54 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:39:54 - Service systemd-resolved restarted . 2026.02.07 20:39:54 - DNS of the interface 'wwan0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:54 - Default Route of the interface 'wwan0' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:54 - DNS of the interface 'enp0s31f6' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'enp0s31f6' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:55 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:39:55 - DNS of the interface 'docker0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:39:55 - Default Route of the interface 'docker0' restored to 'no' - via systemd-resolved . 2026.02.07 20:39:55 - Collect network information . 2026.02.07 20:39:55 - Connection terminated. I 2026.02.07 20:39:58 - Checking authorization ... ! 2026.02.07 20:39:58 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:39:58 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:39:58 - WireGuard > Setup start . 2026.02.07 20:39:58 - WireGuard > Setup complete . 2026.02.07 20:39:58 - WireGuard > Setup interface . 2026.02.07 20:39:59 - WireGuard > Received first handshake . 2026.02.07 20:39:59 - DNS of the system switched to VPN DNS - via /etc/resolv.conf) W 2026.02.07 20:39:59 - Routes, add 0.0.0.0/1 for interface "Eddie" failed: Exception: exit:2; err:Error: Device for nexthop is not up.; path:/usr/sbin/ip; arg:-4; arg:route; arg:add; arg:0.0.0.0/1; arg:dev; arg:Eddie; arg:metric; arg:0 ! 2026.02.07 20:39:59 - Disconnecting . 2026.02.07 20:40:00 - WireGuard > Stop request received . 2026.02.07 20:40:00 - WireGuard > Stopping . 2026.02.07 20:40:00 - WireGuard > Completed . 2026.02.07 20:40:00 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:00 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:01 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:40:01 - DNS of the system restored - via /etc/resolv.conf) . 2026.02.07 20:40:01 - Service systemd-resolved restarted . 2026.02.07 20:40:01 - DNS of the interface 'wwan0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'wwan0' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'enp0s31f6' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'enp0s31f6' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'wlp0s20f3' restored to '192.168.2.1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'wlp0s20f3' restored to 'yes' - via systemd-resolved . 2026.02.07 20:40:01 - DNS of the interface 'docker0' restored to '10.128.0.1 fd7d:76ee:e68f:a993::1' - via systemd-resolved . 2026.02.07 20:40:01 - Default Route of the interface 'docker0' restored to 'no' - via systemd-resolved . 2026.02.07 20:40:01 - Collect network information . 2026.02.07 20:40:01 - Connection terminated. I 2026.02.07 20:40:04 - Checking authorization ... ! 2026.02.07 20:40:05 - Connecting to Alderamin (Austria, Vienna) . 2026.02.07 20:40:05 - Routes, add 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:05 - WireGuard > Setup start . 2026.02.07 20:40:05 - WireGuard > Setup complete . 2026.02.07 20:40:05 - WireGuard > Setup interface ! 2026.02.07 20:40:20 - Disconnecting . 2026.02.07 20:40:21 - WireGuard > Stop request received . 2026.02.07 20:40:21 - WireGuard > Stopping . 2026.02.07 20:40:21 - WireGuard > Completed . 2026.02.07 20:40:21 - Routes, delete 0.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 128.0.0.0/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete ::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 8000::/1 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 185.9.19.109/32 for interface "wlp0s20f3". . 2026.02.07 20:40:21 - Routes, delete 185.9.19.107/32 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Routes, delete 2001:ac8:29:5::3/128 for interface "Eddie", not exists. . 2026.02.07 20:40:21 - Service systemd-resolved restarted . 2026.02.07 20:40:21 - Collect network information . 2026.02.07 20:40:22 - Connection terminated. I 2026.02.07 20:40:22 - Cancel requested. . 2026.02.07 20:40:22 - Deactivation of Network Lock ! 2026.02.07 20:40:22 - Session terminated. ---------------------------- Network Info: { "routes": [ { "destination": "0.0.0.0\/0", "gateway": "192.168.2.1", "interface": "wlp0s20f3", "metric": "600", "proto": "dhcp", "src": "192.168.2.45" }, { "destination": "172.17.0.0\/16", "interface": "docker0", "proto": "kernel", "scope": "link", "src": "172.17.0.1" }, { "destination": "192.168.2.0\/24", "interface": "wlp0s20f3", "metric": "600", "proto": "kernel", "scope": "link", "src": "192.168.2.45" }, { "destination": "fe80::\/64", "interface": "wlp0s20f3", "metric": "1024", "pref": "medium", "proto": "kernel" } ], "ipv4-default-gateway": "192.168.2.1", "ipv4-default-interface": "wlp0s20f3", "interfaces": [ { "friendly": "lo", "id": "lo", "name": "lo", "description": "lo", "type": "Loopback", "status": "Unknown", "bytes_received": "320867", "bytes_sent": "320867", "support_ipv4": true, "support_ipv6": true, "ips": [ "127.0.0.1", "::1" ], "bind": true }, { "friendly": "wwan0", "id": "wwan0", "name": "wwan0", "description": "wwan0", "type": "0", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [], "bind": false }, { "friendly": "enp0s31f6", "id": "enp0s31f6", "name": "enp0s31f6", "description": "enp0s31f6", "type": "Ethernet", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [], "bind": false }, { "friendly": "wlp0s20f3", "id": "wlp0s20f3", "name": "wlp0s20f3", "description": "wlp0s20f3", "type": "Wireless80211", "status": "Up", "bytes_received": "2278710", "bytes_sent": "512860", "support_ipv4": true, "support_ipv6": true, "ips": [ "192.168.2.45", "fe80::91ee:1179:5e88:ccc4" ], "bind": true }, { "friendly": "docker0", "id": "docker0", "name": "docker0", "description": "docker0", "type": "Ethernet", "status": "Down", "bytes_received": "0", "bytes_sent": "0", "support_ipv4": true, "support_ipv6": true, "ips": [ "172.17.0.1" ], "bind": true } ] } ---------------------------- ip addr show: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host noprefixroute valid_lft forever preferred_lft forever 2: wwan0: <POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/none 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether 8c:8c:aa:a6:81:3f brd ff:ff:ff:ff:ff:ff altname enx8c8caaa6813f 4: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 22:99:d5:df:3b:3e brd ff:ff:ff:ff:ff:ff permaddr e8:84:a5:b0:c4:17 altname wlxe884a5b0c417 inet 192.168.2.45/24 brd 192.168.2.255 scope global dynamic noprefixroute wlp0s20f3 valid_lft 43092sec preferred_lft 43092sec inet6 fe80::91ee:1179:5e88:ccc4/64 scope link noprefixroute valid_lft forever preferred_lft forever 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 66:7b:0a:fa:1d:aa brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever ---------------------------- ip link show: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: wwan0: <POINTOPOINT,NOARP> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/none 3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000 link/ether 8c:8c:aa:a6:81:3f brd ff:ff:ff:ff:ff:ff altname enx8c8caaa6813f 4: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000 link/ether 22:99:d5:df:3b:3e brd ff:ff:ff:ff:ff:ff permaddr e8:84:a5:b0:c4:17 altname wlxe884a5b0c417 5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 66:7b:0a:fa:1d:aa brd ff:ff:ff:ff:ff:ff
-
The last version that worked without being sluggish or suffered slow GUI was 2.22.2 but that had a problem in the with Eddie window open, the kde application launcher would not stay open at the same time. I have just initiated Eddie to run through terminal so I could see it load, this was in the first line or the output: $ eddie-ui (eddie-ui:26517): Gtk-WARNING **: 10:32:05.005: Unable to locate theme engine in module_path: "adwaita", . 2026.02.07 10:32:05 - Eddie version: 2.24.6 / linux_x64, System: Linux, Name: Ubuntu 24.04.3 LTS, Version: 24.04.3 LTS (Noble Numbat), Framework: 6.8.0.96 (tarball Wed Jan 15 10:20:48 UTC 2020); Framework: v4.0.30319 This is the Linux version I use: Kubuntu Operating System: Kubuntu 24.04 KDE Plasma Version: 5.27.12 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.8.0-90-generic (64-bit) Graphics Platform: X11
-
WireGuard>Handshake Timeout Error
Tech Jedi Alex replied to ColeCrackles's topic in Troubleshooting and Problems
Close Eddie, reopen and try a connection, then provide a system report. It's interesting that you noticed all the troubleshooting attempts, but not the very first thing that is usually asked: The request for more information.. - Earlier
-
Eddie Desktop - APT Repository Signing Key Update
qitorin replied to Staff's topic in Eddie - AirVPN Client
Thank you for the update - is there going to be new version of the Eddie any time soon? -
I also find the Eddie ui a bit sluggish - I wonder when there will be a updated version or a different client altogether. It is a shame because Windows Eddie is so smooth and fast overall and Android client is just superb, perhaps the Linux-desktop client is not a high priority any more.
