Jump to content
Not connected, Your IP: 3.237.66.86

Clodo

Staff
  • Content Count

    417
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    27

Everything posted by Clodo

  1. I just downloaded 2.19.5, switched to Beta channel, at restart show the notice. What OS you use? Thx.
  2. You are using portable or installer edition? Try the installer OR launch https://eddie.website/windows-runtime/ before launching the portable, i'm waiting for feedback thx
  3. You can retry now? Maybe you try to connect to Netherland servers during the schedulated upgrade yesterday. Honestly, NOTHING are changed in macOS between 2.19.5 and 2.19.6, i don't understand your issue. In general, all our BigSur in our labs works as expected with Eddie, we currently don't reproduce any issue, still under investigation.
  4. Please try to download this: https://eddie.website/windows-runtime/ and retry (it's a dependency that installer edition perform automatically). I know, the Eddie message don't help. I'm waiting for feedback, the next version will have a better solution.
  5. Hi, AA bit issue fixed, https://dnsviz.net/d/ipleak.net/dnssec/ . You can tell me if the issue is resolved? Thanks.
  6. @mazeman23 Please download the latest 2.19.6. Revert to blank the option Preferences -> Advanced -> OpenVPN custom path Revert to blank any Preferences -> OpenVPN directive Restart Eddie 2.19.6 and retry.
  7. I don't understand well, we tested BigSur and don't encounter any particular issue, but i honestly don't know what Little Snitch is.
  8. All of your: please retry the latest beta version, contain the fix. Thanks.
  9. Hi, we compile Eddie with Raspberry OS 64 beta (based on Debian). I don't have currently an Ubuntu rPI for testing. Anyway in the latest release we fix a bug related to elevation in CLI mode under Linux, please recheck. Please note also that aarch64 edition of Eddie include OpenVPN 2.4.8 (armv7 and other platform include the latest 2.5.0). This because OpenVPN build process is not still updated to support aarch64, it's a pending issue.
  10. On Arch launch sudo pacman -S stunnel
  11. This occurs because we use PowerDNS software. https://doc.powerdns.com/authoritative/appendices/FAQ.html IpLeak has this configuration since almost TEN years ago, it's very very difficult for us to think the issue is not yet resolved. Anyway, this is still under investigation, but currently we can't fix, we can't replace PowerDNS.
  12. About the DNS issue, we have a class called IpAddresses (where previous DNS are stored in ram), that wrongly performs a sort that causes the issue, sort removed. Sorry but in our current workflow, our team works on code-base on a private repo, and when a release (not necessarily a stable one, also a beta one) is ready, it's flushed in public GitHub.
  13. Hi, don't need to fill a bugreport, i will check this. Edit: confirmed, will be fixed in the next release
  14. The problem with OpenVPN2.5 rc2 (or rc1, or beta5) with Eddie is caused by recent changes in OpenVPN that produce a compatibility issue. Please be patient, both errors above ("Object reference not set to an instance of an object." and "ERROR: Wintun requires SYSTEM privilege") will be fixed in the next Eddie release, please wait. We plan to release version 2.19.5 in a few days, and another one (or maybe the same) in bundle with OpenVPN 2.5 STABLE when a stable version is released.
  15. This is a known incompatibility problem between Eddie and the latest beta of OpenVPN2.5, it will be fixed in the next beta release, sorry you can only wait for now, we have other issues under investigation before releasing.
  16. It is not mandatory to wait for next Debian version: we are already testing up to date WireGuard version. When we'll make WireGuard available to customers, it will be on all servers. Exactly, it's unavoidable. With OpenVPN that's currently correct. However, with WireGuard we need to keep it, because it's written in .conf file generated via Config Generator and stored by users. See below for users' option to change or invalidate it. Some of our competitors do this. Some accept only their official client software because of the issue. That's neither good nor acceptable for us, as we don't want to lock user into our software. Therefore the change you mention might be an Eddie's additional feature but we will try to make Wireguard main branch as secure as Eddie's, whenever possible. Yes, we still use ifconfig-pool-persist in OpenVPN. It's very different than Wireguard's addresses binary mapping, especially under a legal point of view. When a client is connected, OpenVPN daemon necessarily needs to link clients' public and VPN IP addresses. As soon as the client disconnects the link is lost. One of WireGuard controversies is that client's real IP address remains visible with 'wg show' even after client's disconnection. The issue is resolved by removing and re-adding the peer after a disconnection (disconnection in WireGuard is basically a handshake timeout). Some current testing implementation features are: Unique WireGuard IPv4 and IPv6 subnets across servers which don't conflict with OpenVPN subnets Assigning a non-conflicting, pseudo-random, local IP address for each customer's device (for AllowedIPs), similar to remotely forwarded port assignments Users can renew a local IP address for a device anytime. WireGuard .conf manually used in official client would become invalid. Eddie will automatically update. The same happens when a user regenerates OpenVPN client certificate and key pair: the action invalidates any previously stored OpenVPN profile. We will offer an API to automate the above, letting users write a script that performs HTTPS calls to change local IP address, download updated .conf, and then wg-quick. An API to obtain a .conf file (Config Generator without UI) is already in production for OpenVPN and it will be of course available for WireGuard too. When a device's WireGuard local IP address changes, up to a 10 seconds wait is required. It's the time required to propagate device key onto all VPN servers, in order to update the AllowedIPs peer node. No other solution allowing us to let our customers use the official WireGuard client with a simple .conf file and, at the same time, preserve their privacy currently exists. Please keep the above information as a proposal: we are currently studying pros and cons and something may change before WireGuard public beta support in our VPN servers is available.
  17. This was an already resolved bug, does it still occur in 2.19.3?
  18. Yes thanks, if it is reproducible, enable in Preferences -> Logs both 'Log Debug' and 'Log on File'. Here or open a ticket if you prefer, thanks.
  19. Can you provide the exact message error? During development, sometimes we encounter a mystic "error -47", but it can't be related to Eddie because it disappears with a reboot. Still under investigation. Same as above, when you reboot does the issue disappear? Thx
  20. @Maggie144 has a specific macOS bug that will be fixed soon. @colorman, Linux, If you tick Preferences -> Advanced -> Use Hummingbird, Eddie will search for Hummingbird executable in environment paths. Otherwise a path can be set with option "--tools.hummingbird.path=/path/to/...". Sorry, no UI right now, it will be available in 2.19.3. But remember: you need to ensure "chmod +x /path/to/hummingbird" AND "chown root /path/to/hummingbird". An Eddie security protection requires root ownership.
  21. We hope to release 2.19.3 probably tomorrow, it fixes the "Unable to obtain elevated privileges (required): Object reference not set to an instance of an object" issue. Of course with Hummingbird updated. Please be patient, thx.
  22. Can you post a screenshot of the error by 2.19.2? Thx If you want to test, older 2.19.0 portable version for macOS is here
  23. linux .deb x64 resolved, thx, my apologies, an issue in deployment system.
  24. We cleaned the above post on Linux build crash for simplicity's sake. We have detected the issue and we are working to resolve it.
  25. Version 2.19.1 (Sat, 18 Apr 2020 11:14:36 +0000) [bugfix] Linux - Fix issue with Network Lock IPv6-only incoming whitelist [bugfix] - http-100-continue issue [bugfix] - Special condition elevation checks (may resolve "Unable to start (no-socket)" issues). [change] - Removed curl binary dependencies [new] Linux - New Network Lock with nftables (if nft is present, it is used by default in "Automatic" mode) [new] Windows - New option "Use wintun driver (OpenVPN>=2.5)" under "Preferences -> Advanced" automates ovpn directive
×
×
  • Create New...