Jump to content
Not connected, Your IP: 216.73.216.183

All Activity

This stream auto-updates     

  1. Past hour
  2. Today
  3. This would also solve the same problem for libvirt and Nat for KVM/QEMU I presume.
  4. I gave the procedure you suggested a try. As soon as the lock activates the NAT connection breaks. Thanks for the suggestion though.
  5. I've only used NAT (default). Are you saying a NAT Mint guest does not suffer this issue and the connections works when Eddie lock in in? I've only tested this with a MXLinux, guest. Debian 13 derivative.
  6. Oh, well... I guess we share the same levels of decrepitude then. Started at 13 on a Sinclair ZX-81, but of course the Commodore 64 was THE best computer of all time. At one point, I knew by heart how many CPU cycles each 6510 instruction used and what opcode each Assembly mnemonic translated to. That being said, my advice would be to ignore current MicroSlop's development guidelines - and Linux's, for that matter - and keep all program data in its own installation directory.
  7. Hello! If you run Eddie's uninstaller script for Windows, it does not remove the configuration file in the user's directory. It leaves both the directory and the configuration file inside it, including default.profile. This is intentional as uninstalling a software does not mean purging all the configuration files that can be preserved. No erratic behavior has been detected, it's just a script. This would be catastrophic in many cases. Firefox, Thunderbird, GitLab, Microsoft SQL SRS and probably hundreds of other programs do not support inverse migration (downgrade) in general, exactly for this problem. In case of a downgrade for which the configuration file becomes incompatible with the older version, deleting or overwriting the configuration files etc. will cause serious or, in case of absence of a recent backup, even dramatic inconvenience to the user. EDIT - NOTE BY THE DECREPIT FOUNDER In Eddie, profile preservation has an excellent side effect. The profile (encrypted or not) includes the client keys and server information, and Eddie reads them locally when it can't access the bootstrap servers. When you are in a restrictive network, or typically in specific countries (Iran, China, Russia...) the bootstrap servers or the protocol to reach them are not infrequently blocked. In such cases the user must first find another connection method, establish the connection and only then let Eddie contact the bootstrap servers to download the information that will be valuable for future connections. This is a once and for all operation that may be reproducible and performed in the face of potentially great adversity, so minimization of such a requirement is good. If we want to have a sad contest to see who’s the most decrepit, we have a good competitor. The founder of AirVPN built his first natural language parser in Assembly and BASIC in 1983 with a 1,500-word dictionary, pushing the limits of an 8-bit computer (a Commodore 64). Thirty-five years ago, he was already at CERN with Tim Berners-Lee who was creating HTML and testing and improving HTTP... But rest assured, he’s not the one working on Windows - it gives him an allergic reaction. 🤣 You can bet that he was behind the earlier caustic jokes about Windows. 🤔 Kind regards
  8. You're assuming a lot, aren't you? After uninstalling v2.26.2, and before trying to reinstall the previous version, I triple checked and there were no Eddie leftover directories anywhere in the system drive. Just for the sake of clarity, I did the whole process again, and this time the v2.26.2 uninstall DID leave Eddie config directories behind. It would seem to me that your uninstaller behaves erratically at times. And yes, a well written installer should be smart enough to detect config files from previous versions and, if it's unable to gather useful info from them, at least overwrite them, resetting the config. Were you even alive and already programming 31 years ago? Forgive me, this was irresistible...
  9. Yesterday
  10. It works! 😀 Thank you so much for your work! This fix for a persistent bug related to privilege escalation allows me to upgrade directly from version 2.25.1 to version 2.27.2. I can therefore confirm to anyone who is a bit too quick to criticize the eddie-ui user interface that version 2.27.2 poses no obstacle to its use on current operating systems, and that—among many other options—it allows you to choose between 3 WireGuard protocols and more than 50 for OpenVPN! When free software works perfectly, is secure, and offers the end user so much freedom of choice in a graphical interface, we should 👏 thank and encourage the developers rather than criticizing the project for no good reason without contributing improvements in the form of pull requests or forks. 🌻 I hope that other users who encountered similar privilege escalation issues will take as much pleasure as I did in thanking the development team.
  11. zlimteck

    AltStore source

    Hello, A native AltStore source is now available for the full build (native WireGuard connect/disconnect, Live Activity, widget). It requires a paid Apple Developer account connected or P12 Certificate to AltServer/SideStore and more, since the Personal VPN entitlement can't be granted to a free account. Source Link : https://api.altstore.io/source/raw.githubusercontent.com/zlimteck/AirDash/main/altstore-source.json Last version : Airdash 1.0.12. Zlimteck.
  12. I hope the latest 2.27.2 automatically fix your issue, thanks for the report
  13. Version 2.27.2 (Mon, 14 Sep 2026 08:16:32 +0000) [fix] [macos] Traffic speed and session stats stuck at zero with many network interfaces [change] [all] Updated OpenVPN to 2.7.7 [change] [windows] Updated ovpn-dco Win11 driver to 2.8.7 [fix] [macos] Elevation and service install failed when /Library/PrivilegedHelperTools does not exist [fix] [all] Connect ignored after a session ended by itself [fix] [windows] Use tap-windows6 on Windows 10, the bundled ovpn-dco driver is Win11 only [fix] [all] Enforce OpenVPN script-security in privileged helper [fix] [all] OpenVPN config check now parses directives like OpenVPN [change] [all] Block OpenVPN management interface and pkcs11/engine modules in the privileged process [change] [all] Drop refused OpenVPN directives at config build, with a log warning [fix] [linux/macos] Elevation failed: IPC dir permissions too strict [fix] [all] Network Lock failed when shared state dir was removed
  14. YouTube has been actively blocking or demanding logins from IP addresses it identifies as VPN servers. Since they regularly blacklist these IPs, your best option right now is to simply experiment with different locations and switch between various AirVPN servers until you find one that works, as the list of usable servers changes all the time.
  15. Hello! The problem is different. You pretend a downward compatibility of a configuration file with a previous software version and this is not guaranteed in general. This is the problem. You can downgrade at will Eddie, but remember that you must purge the higher version of the configuration file because sometimes it may contain new supported options, directives, fields for new features and so on that can't be parsed by the older software. This is true for any software, not only for Eddie, and it is not at all ridiculous, it is correct and sometimes strictly necessary for a natural evolution of any software relying on a configuration file. According to nowadays conventions and Microsoft recommendations the configuration file is stored by default in the AppData directory of the user who installed Eddie. See also: https://eddie.website/support/data-path/ You think you have never met this case in 31 years of Windows usage exactly because you've been using Windows for 31 years. 😋 Forgive us, this was irresistible... Kind regards
  16. I've never seen anyone providing a memory dump around here before now I've seen it all, I guess. In any case, this reeks a bit of AI processing, like it's written by some form of AI agent. Kudos for the structured problem report, of course, but there are things in here that absolutely no human would ever write about in such excruciating detail. If the driver is the problem, did the agent try installing the official driver, not the one provided by Eddie? Did it try an older version? Because Eddie only bundles the driver, AirVPN doesn't code it per se, so a "sync gap during the driver's teardown phase" really belongs upstream, and not here, I would think. As outlined in Troubleshooting Performed, this was not tried.
  17. I install Eddie in D:\Net\AirVPN. I try to keep programs out of the Windows directories as much as possible. Anyways, I checked the C drive for any leftovers and also deleted what was left in my install folder. Nothing helped. Installing 2.27 beta will probably work - as reinstalling 2.26.2 did - but I should definitely be able to install the immediate previous version of a program without going through this much trouble.
  18. Hello! Thank you for the report, it will be put under the devs' attention. Your settings look correct. The workaround suggested by @Tech Jedi Alex can't work, as it pertains to the virtual network interface to be used for the tunnel, while here the problem seems that Eddie picks the wrong interface for the connection even when you explicitly tell it to use another one (Ethernet). Kind regards
  19. Hello AirVPN Support and Development Team, I am writing to report a stability issue regarding a non-deterministic Blue Screen of Death (BSOD) with error code **0x3B (SYSTEM_SERVICE_EXCEPTION)** triggered when disconnecting from a WireGuard tunnel via the Eddie client. Because this crash happens intermittently during the teardown sequence, it strongly indicates a **Race Condition** or **Use-After-Free (UAF)** vulnerability inside the `wireguard.sys` driver wrapper, where memory buffers are accessed after being invalidated by the NDIS subsystem. **System Environment** * **OS:** Windows 10 IoT Enterprise LTSC 2021 (64-bit) * **Build Number:** 19044.7725 * **Eddie Version:** Any version utilizing WireGuard 1.0.0.0 * **WireGuard Driver Version:** WireGuard 1.0.0.0 **Bug Check Details & Stack Trace Summary** * **Bug Check Code:** 0x3B (`SYSTEM_SERVICE_EXCEPTION`) * **Exception Code:** 0xC0000005 (`EXCEPTION_ACCESS_VIOLATION`) * **Faulting Address:** `0xfffff8004f01111e` (Inside `ndis.sys`) * **Trigger Event:** Disconnecting from the WireGuard tunnel using Eddie. * **Key Stack Frames:** Crash manifests inside `ndis!ndisDeviceControlHandler` triggered by concurrent execution paths originating from `wireguard.sys+0x13b02` and `wireguard.sys+0x13844` during an IOCTL-driven shutdown. **Technical Analysis (Race Condition Hypothesis)** The crash signature and call stack point to a synchronization gap during the driver's teardown phase: 1. **Teardown Initiation:** Eddie issues an IOCTL call to halt the adapter. 2. **Memory Invalidation:** NDIS begins freeing `NDIS_MINIPORT_BLOCK` structures and associated packet buffers. 3. **Concurrent Access:** A pending network interrupt or timer event inside `wireguard.sys` simultaneously attempts to process packets using stale pointers. 4. **Violation:** The driver dereferences the invalidated memory, throwing an access violation within `ndis.sys`. **Reproduction Steps** 1. Launch Eddie and connect to any WireGuard endpoint. 2. Maintain the connection for an arbitrary duration. 3. Click **Disconnect**. 4. **Result:** The client intermittently crashes with BSOD 0x3B instead of executing a clean disconnect. The failure is purely stochastic and independent of network traffic load. **Troubleshooting Performed** * Fast Startup: Disabled. * Clean Install: Performed complete purges of Eddie and residual `wireguard.sys` drivers, followed by clean reinstalls. The issue persists. * Traffic Load: Tested under both idle and high-throughput states; failures occur uniformly, confirming a state-dependent synchronization bug rather than a load-dependent fault. **Impact & Request** This issue undermines system stability on Windows 10 IoT LTSC environments. Since the official WireGuard for Windows client utilizes `Wintun.sys` (which manages adapter concurrency and teardown safely in user-space/TUN architecture), the legacy `wireguard.sys` wrapper appears to lack robust reference counting or synchronization primitives (such as proper spinlock implementation) during NDIS miniport halts. Could you please clarify: * Are you aware of this specific race condition in `wireguard.sys`, and is there an updated build or fix available? * Are there plans to transition Eddie toward native `Wintun.sys` utilization to bypass these kernel-level concurrency constraints? Thank you for your time and assistance in analyzing this behavior. A full kernel memory dump (`MEMORY.DMP`) is attached to this message. 091326-9562-01.dmp
  20. Last week
  21. Hi, I have been using AirVPN and Eddie for almost 3 years in MacOS and Android. Some time ago (1 year?) I started to have this problem in MacOS when I started Eddie, the computer went to sleep and back or sometimes switching cable/wireless. When the splash window reaches the "network lock" step it shows this message and closes: Unexpected error. Please contact our support staff. - CurrentDomain - Object reference not set to an instance of an object - at Eddie.UI.Cocoa.Osx.AppDelegate.ApplicationShouldHandleReopen (AppKit.NSApplication sender, System.Boolean hasVisibleWindows) [0x0000c] in <4905fd93f6c34a379534a47b943e7e4d>:0 at (wrapper managed-to-native) AppKit.NSApplication.NSApplicationMain(int,intptr) at AppKit.NSApplication.Main (System.String[] args) [0x00048] in <3c4bf011da8d4906a57e81cb141cd836>:0 at Eddie.UI.Cocoa.Osx.MainClass.Main (System.String[] args) [0x0006c] in <4905fd93f6c34a379534a47b943e7e4d>:0 Here is the system report: https://eddie.website/report/5bd201d4/ The worst part is that very often the network lock remains activated, therefore locking the computer network connection. The exact nature of the problem is difficult to replicate. For instance, today I was normally using the computer, Wifi off, cable on, start Eddie and it pops up. Whereas sometimes it has resolved for itself by trying repeatedly, this time I resorted to killing eddie-cli-elevated from the terminal. I have to say, this kind of problem appeared occasionally when I started using AirVPN, but resolved well after killing eddie-cli-elevated. Not anymore after 1 year something ago. Sometimes after killing it a number of times, other times it solves itself after a while of trying, or restarting the computer... or not even restarting the computer (network lock stays there). I had some worrying situations trying to solve it restarting, killing the helper, restarting again, waiting... until somewhat Eddie comes back to life and I can unlock the network (I have been looking for a manual method to do it myself with no luck (any leads here will be well appreciated, I read Eddie documentation but no luck understanding how to work with MacOS PF method). This is rather annoying, but it can be a problem sometimes. Indeed, I stopped using the "Activate network lock at startup" option afraid of being locked out if Eddie crashed like that, but even not having it activated it leaves the network lock activated when it happens (or very often). I wonder if this has happened before and anyone has a solution (I checked the forum and found some cases, but not like mine). A big problem is that Eddie does not offer any option to solve this kind of problems, like removing the network lock or refreshing eddie-cli-elevated (I understand that it requires eddie-cli-elevated for any activity, and the former is not possible if it is not working properly or not connecting to it, but it might be able to try to restart eddie-cli-elevated if there are problems with it). Not the same problem but related to it, sometimes Eddie seems like it is not responding to the Disconnect button. Actually, it is working, but it takes a while to do something. I wonder if it should immediately show a "Disconnecting" message, so you know it is working on it. A "Force disconnect" button for problematic situations could also be handy (not very often, but a server might stop responding an Eddie just sit there with no connection, taking a long time waiting for it when hitting "Disconnect"). Greetings!
  22. @Riesengebirge the answer is here : I didn't find any other solution. I guess you can find where is the eddie profile in windows 10 blablabla and then delete it. Or you can try the 2.27 (beta) version.
  23. Hello, moving to the other thread was done exactly to avoid pollution as it's the exact same problem, but it's your call. The workaround you propose doesn't work. With ZeroTier installed, my network adapter list is this: My settings are these (I tried also "eddie" and "Eddie 1"): but Eddie does this: and fails to connect. Uninstalling ZeroTier (not a solution, but a test) makes Eddie revert to good behavior: and it connects nicely. Thank you.
  24. Hello! Can you please try again now? Kind regards
  25. Hi, Toliman doesnt register in Client Area -> Sessions. Is this by design? The link seems to be established, i just dont see an active session in the UI. Thanks PS. This web is rather bad on mobile. Any chance you guys will work on this?
  26. I tried to go back to version 2.24.6, so I uninstalled the program, made sure there were no leftovers and installed that version. I was unable to start Eddie again - I kept getting this window asking for a password, and it isn't my account's password. The only thing that made the program work again was to reinstall version 2.26.2. Windows 10 LTSC Enterprise 64-bit.
  1. Load more activity
×
×
  • Create New...