Not connected, Your IP: 216.73.216.120
Online: 36597 users - 442786 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
-
-
-
-
-
- Today
-
-
-
-
-
Hi! Thank you for joining! In the FileRepository, i've got one folder wireguard and many wireguard files. Should i only delete the folder? All good for the wireguard.sys and i found nothing through the Device Manager.
-
Staff, Only windows defender is active. I turned off the firewall and the protection vs the virus but nothing changed. Same error. Here is the journal is that helps : 2025-12-09 14:29:03.231049: [MGR] Starting WireGuard/0.5.3 (Windows 10.0.26100; amd64) 2025-12-09 14:29:03.244177: [MGR] Starting UI process for user ‘admin@DESKTOP-7EDM8FG’ for session 26 2025-12-09 14:33:50.165239: [TUN] [wg] Starting WireGuard/0.5.3 (Windows 10.0.26100; amd64) 2025-12-09 14:33:50.165239: [TUN] [wg] Watching network interfaces 2025-12-09 14:33:50.170649: [TUN] [wg] Resolving DNS names 2025-12-09 14:33:50.271950: [TUN] [wg] Creating network adapter 2025-12-09 14:33:50.560462: [TUN] [wg] Using existing driver 0.10 2025-12-09 14:33:50.591911: [TUN] [wg] Creating adapter 2025-12-09 14:33:50.930792: [TUN] [wg] Using WireGuardNT/0.10 2025-12-09 14:33:50.930792: [TUN] [wg] Enabling firewall rules 2025-12-09 14:33:50.902400: [TUN] [wg] Interface created 2025-12-09 14:33:50.942891: [TUN] [wg] Dropping privileges 2025-12-09 14:33:50.943440: [TUN] [wg] Setting interface configuration 2025-12-09 14:33:50.944575: [TUN] [wg] Peer 1 created 2025-12-09 14:33:50.946176: [TUN] [wg] Sending keepalive packet to peer 1 (213.152.186.37:1637) 2025-12-09 14:33:50.946176: [TUN] [wg] Sending handshake initiation to peer 1 (213.152.186.37:1637) 2025-12-09 14:33:50.946176: [TUN] [wg] Interface up 2025-12-09 14:33:50.956310: [TUN] [wg] Receiving handshake response from peer 1 (213.152.186.37:1637) 2025-12-09 14:33:50.956310: [TUN] [wg] Keypair 1 created for peer 1 2025-12-09 14:34:01.453036: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:34:11.692617: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:34:22.447712: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:34:33.456590: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:34:44.456663: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:34:50.952377: [TUN] [wg] Unable to create network adapter: TCP/IP interface for adapter did not appear after one minute 2025-12-09 14:34:51.111467: [TUN] [wg] Shutting down 2025-12-09 14:34:51.114346: [MGR] [wg] Tunnel service tracker finished 2025-12-09 14:35:46.968946: [TUN] [wg] Starting WireGuard/0.5.3 (Windows 10.0.26100; amd64) 2025-12-09 14:35:46.968946: [TUN] [wg] Watching network interfaces 2025-12-09 14:35:46.975098: [TUN] [wg] Resolving DNS names 2025-12-09 14:35:46.994182: [TUN] [wg] Creating network adapter 2025-12-09 14:35:47.213012: [TUN] [wg] Using existing driver 0.10 2025-12-09 14:35:47.233532: [TUN] [wg] Creating adapter 2025-12-09 14:35:47.555078: [TUN] [wg] Using WireGuardNT/0.10 2025-12-09 14:35:47.555610: [TUN] [wg] Enabling firewall rules 2025-12-09 14:35:47.528691: [TUN] [wg] Interface created 2025-12-09 14:35:47.564776: [TUN] [wg] Dropping privileges 2025-12-09 14:35:47.571208: [TUN] [wg] Setting interface configuration 2025-12-09 14:35:47.571730: [TUN] [wg] Peer 1 created 2025-12-09 14:35:47.572830: [TUN] [wg] Sending keepalive packet to peer 1 (213.152.186.37:1637) 2025-12-09 14:35:47.572830: [TUN] [wg] Interface up 2025-12-09 14:35:47.572830: [TUN] [wg] Sending handshake initiation to peer 1 (213.152.186.37:1637) 2025-12-09 14:35:47.590126: [TUN] [wg] Receiving handshake response from peer 1 (213.152.186.37:1637) 2025-12-09 14:35:47.590126: [TUN] [wg] Keypair 1 created for peer 1 2025-12-09 14:35:57.931168: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:36:08.171736: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:36:18.921786: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:36:29.931008: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:36:40.943255: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.186.37:1637) 2025-12-09 14:36:47.583625: [TUN] [wg] Unable to create network adapter: TCP/IP interface for adapter did not appear after one minute 2025-12-09 14:36:47.739477: [TUN] [wg] Shutting down 2025-12-09 14:36:47.742422: [MGR] [wg] Tunnel service tracker finished 2025-12-09 15:22:04.939420: [TUN] [wg] Starting WireGuard/0.5.3 (Windows 10.0.26100; amd64) 2025-12-09 15:22:04.939420: [TUN] [wg] Watching network interfaces 2025-12-09 15:22:04.942684: [TUN] [wg] Resolving DNS names 2025-12-09 15:22:05.044963: [TUN] [wg] Creating network adapter 2025-12-09 15:22:05.248893: [TUN] [wg] Using existing driver 0.10 2025-12-09 15:22:05.271745: [TUN] [wg] Creating adapter 2025-12-09 15:22:05.567554: [TUN] [wg] Using WireGuardNT/0.10 2025-12-09 15:22:05.569281: [TUN] [wg] Enabling firewall rules 2025-12-09 15:22:05.544065: [TUN] [wg] Interface created 2025-12-09 15:22:05.577540: [TUN] [wg] Dropping privileges 2025-12-09 15:22:05.578770: [TUN] [wg] Setting interface configuration 2025-12-09 15:22:05.579324: [TUN] [wg] Peer 1 created 2025-12-09 15:22:05.580444: [TUN] [wg] Sending keepalive packet to peer 1 (213.152.161.231:1637) 2025-12-09 15:22:05.580444: [TUN] [wg] Sending handshake initiation to peer 1 (213.152.161.231:1637) 2025-12-09 15:22:05.580444: [TUN] [wg] Interface up 2025-12-09 15:22:05.598247: [TUN] [wg] Receiving handshake response from peer 1 (213.152.161.231:1637) 2025-12-09 15:22:05.598247: [TUN] [wg] Keypair 1 created for peer 1 2025-12-09 15:22:15.809056: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.161.231:1637) 2025-12-09 15:22:26.305812: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.161.231:1637) 2025-12-09 15:22:36.798333: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.161.231:1637) 2025-12-09 15:22:47.804209: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.161.231:1637) 2025-12-09 15:22:58.810823: [TUN] [wg] Receiving keepalive packet from peer 1 (213.152.161.231:1637) 2025-12-09 15:23:05.588762: [TUN] [wg] Unable to create network adapter: TCP/IP interface for adapter did not appear after one minute 2025-12-09 15:23:05.690754: [TUN] [wg] Shutting down 2025-12-09 15:23:05.692326: [MGR] [wg] Tunnel service tracker finished 2025-12-09 15:23:09.620094: [MGR] [wg] Tunnel service tracker finished
-
This is a driver issue; I've encountered this problem before. Windows may have remnants of an older version of the Wireguard service (the driver has been modified by other software). You can try deleting the wireguard.sys driver (check in Device Manager for a network adapter named "Wireguard Tunnel," right-click to uninstall the device, and check the box to delete its driver), then restart your computer and run Wireguard again to see if you can connect. If the network adapter cannot be found in Device Manager, delete wireguard.sys in the directory C:\Windows\System32\drivers, and delete the folders containing "wireguard" in the directory C:\Windows\System32\DriverStore\FileRepository. Then restart your computer and run the Eddie or Wireguard client again to connect. (Deleting the drivers in this directory requires system privileges or can be done in a PE system. Do not delete other files, otherwise it will cause system errors.) Hope this helps.
-
Hello! Something is blocking the creation of the virtual network interface that WireGuard needs, so it was not an Eddie's problem. Do you run any antimalware tool that might be blocking networking operations and/or blocking software that needs to modify network configuration with administrator privileges? Kind regards
-
Hi! I followed the steps but i've got an error at the end. "Unable to create network adapter." Here some screenshots to see step by step what i did.
-
-
-
I installed AmneziaVPN, downloaded generated configuration (Nederland) UPD 1637 and connected. It works with and without these changes in [Interface] section. I did not change any other config values in AmneziaVPN. Now, I tried to use EddieUI with default params and it works too! Looks like domestic regulators have holiday in Uzbekistan... I will try again tomorrow.
-
-
Yes, the addition of the AmneziaWG protocol can solve the connection problems for most people at present, and I hope that AmneziaWG can be used for a long time. If in the future, when the existing protocol can no longer connect, I believe that AirVPN will add a new protocol to solve the connection problem. I will always believe in your technology and capabilities, and I believe that you will always let us breathe real internet. I will always love you, AirVPN. Keep it up!😘😘😘
-
Hello! Not anymore, and even less in the near future. HTTP/3 is quickly spreading. Today, HTTP/3 is used by 36.5% of all the websites, including major web sites inside countries that enforce blocks against VPN. Furthemore, blocking UDP as such is no more realistic, not even in China, where UDP has become an instrumental protocol for many companies in any sector (video streaming, video conference, VoIP, marketing, social media marketing, regime propaganda and more), for regime aligned or regime owned activities. In China you have a near 100% success rate and no shaping (apart from the normal shaping for anything outside China) with the current Amnezia "weak obfuscation" (no CPS) implementation, i.e. at the moment you don't even need QUIC mimicking (which is anyway available and very effective). Currently, bypassing blocks via UDP than via TCP is more efficient in China. At the moment there is nothing more effective than mimicking QUIC with the signature / fingerprint of an existing web site that's not blocked, and you have this option right now. We see > 95% success rate, which is better than the success rates of SSH (not exceeding 75%), shadowsocks and XRay, V2Ray etc (but a lot faster!). The success rate is similar to any VPN protocol over HTTP/2, but, again, dramatically faster. We're glad to know it. It is also very flexible. Thanks to CPS, you may mimic any transport layer protocol built on UDP, for example DNS, QUIC, SIP. Kind regards
-
Hello! The problem is that WireGuard doesn't start. Please try a re-installation from the official package available here: https://www.wireguard.com/install/ Then test WireGuard native utilities to connect, in order to discern whether the problem is Eddie specific or not. Instructions are available here: https://airvpn.org/windows/wireguard/gui/ Kind regards
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
Hello! Please set MTU to 1280 bytes and test again. If the problem persists please test from the host, without containers, to determine whether it's a GlueTun specific problem or not. Keep MTU to 1280 bytes and increase at small steps. Kind regards -
-
Nobody? Maybe it's not the place to ask for some support? Let me know
-
-
-
With the AmneziaWG protocol, the obfuscation capability at the UDP layer is greatly improved, but what about at the TCP layer? Other countries may completely block the UDP protocol, making it impossible for AmneziaWG to connect. In that case, they can only connect via the TCP protocol. Currently, AirVPN only has early obfuscation solutions such as SSH and SSL for TCP obfuscation. In China's IPv4 environment, SSH and SSL are fully recognized, rate-limited, and blocked. This means that AirVPN's TCP-level obfuscation performance is relatively poor. I think the next step for AirVPN could be to focus on TCP obfuscation. X-ray, Shadowsocks, and V2Ray are all protocols with high levels of obfuscation. You could choose one of these protocols to make an outer proxy for OpenVPN TCP to enhance the obfuscation capabilities at the TCP layer. I know that AirVPN's strongest shield against TCP is the pluggable bridges developed by the Tor team. However, Tor is blocked in China at a much higher level than SSH and SSL (because the dark web is hidden within the Tor network). The newly developed WebTunnel is unlikely to survive more than three months in China. Blocking Tor isn't about identifying the bridge protocol; it's about blocking Tor-related domains, node IPs, and bridge IPs, making Tor unusable in China. AirVPN might be able to utilize the obfuscated bridge protocols developed by the Tor team without using Tor nodes, using bridge protocols like WebTunnel as an outer proxy for OpenVPN TCP, directly connecting to the AirVPN server network. AirVPN may still rely on Tor for TCP protocol obfuscation in the short term, which is understandable, given that adding a new protocol to all servers would require a significant amount of time and resources. The addition of the AmneziaWG protocol is sufficient for my needs; thank you, AirVPN. However, with increasing global internet censorship and the emergence of new obfuscation protocols, switching to more modern obfuscation protocols is definitely the future trend for VPN vendors, because there will always be people in the dark side of the internet. These are all my personal opinions, thanks.
-
Eddie is endlessly "checking authorization" and continuously getting "server closed: high packet loss" . It was working this morning, internet seems fine. Windows 11 recently updated and also I changed isp a few days ago. But Eddie has worked fine since, so idk if that is relevant. Edit: Currently working again today (the following morning). The ONLY server listed is Kornephoros Canada though. Is this normal??
-
- Yesterday
-
Hello, I’m having trouble with very low download speeds when using AirVPN (WireGuard) through the Gluetun Docker container, and I’m hoping for some guidance or pointers on what to check next. ### Setup - Host OS: Linux (Docker host) - VPN client: qmcgaw/gluetun Docker image - VPN_TYPE: wireguard - VPN_SERVICE_PROVIDER: airvpn - Gluetun is used as a “VPN gateway” container for my download stack. - Applications: - qBittorrent (behind Gluetun) - SABnzbd (was also behind Gluetun, now temporarily bypassed for testing) - Location: Germany - ISP speed (real, without VPN): ~80 MB/s down on the same machine In Gluetun I pass the WireGuard parameters from the AirVPN config: - WIREGUARD_PRIVATE_KEY = <PrivateKey from [Interface]> - WIREGUARD_PRESHARED_KEY = <PresharedKey from [Peer]> - WIREGUARD_ADDRESSES = <Address from [Interface], e.g. 10.x.x.x/32> - WIREGUARD_ENDPOINT_PORT = 1637 - SERVER_HOSTNAMES or SERVER_REGIONS used to select servers (mainly DE/NL) ### What works The connection itself comes up fine: - Gluetun logs show: - WireGuard setup is complete - Public IP address is an AirVPN IP (usually NL/DE) - DNS is working, healthcheck is green. - Traffic from containers behind Gluetun does go through the VPN (confirmed by IP checks). ### The actual problem: speed When my download applications (especially SABnzbd) are routed through Gluetun/AirVPN via WireGuard, I only get about **8–10 MB/s** download speed. However: - Without AirVPN / without Gluetun (direct connection), using the same host, same Usenet provider and same test downloads, I get around **80 MB/s**. - If I take SABnzbd out of the VPN (normal Docker network, SSL directly to my Usenet provider), I’m immediately back at ~80 MB/s. So the bottleneck appears to be specifically the AirVPN WireGuard tunnel / routing, not my hardware, not Docker, and not my Usenet provider. ### What I have already tried 1. **MTU tuning** - I tested path MTU and ended up setting: - `WIREGUARD_MTU=1380` in Gluetun. - Before MTU tuning I was down in kB/s. - After setting MTU to 1380, speeds improved to ~9 MB/s, but that’s still far from the ~80 MB/s I get without VPN. 2. **Different servers / regions** - I first used `SERVER_REGIONS=Europe` / `SERVER_COUNTRIES=Germany`. - I then switched to **specific servers** with `SERVER_HOSTNAMES=<server>.airvpn.org` (mainly DE/NL servers with low load according to the AirVPN status page). - In all cases, the WireGuard tunnel works, but the throughput is stuck around 8–10 MB/s. 3. **Local checks** - Host CPU/RAM/IO are fine. - No container resource limits that would explain the cap. - The same host and same downloads without VPN consistently hit ~80 MB/s. ### What I would like to know - Is there any **known routing or peering issue** between German ISPs and certain AirVPN DE/NL servers when using WireGuard? - Are there **recommended optimal settings** (MTU, ports, specific servers or protocols) for high-throughput WireGuard usage with Docker / Gluetun? - Would you recommend trying **OpenVPN UDP** instead of WireGuard in my situation, and is it expected that WireGuard might perform worse in some routes? - Are there any additional **debug logs or tests** you would like me to run from my side (e.g. mtr from inside the tunnel to certain locations, specific AirVPN servers to test, etc.)? I fully understand that there is overhead and that I won’t necessarily get 100% of my line speed through a VPN, but dropping from ~80 MB/s without VPN to ~9 MB/s with AirVPN WireGuard is quite drastic. I’d be very grateful for any suggestions on how to troubleshoot or improve this. If needed, I can provide: - anonymized Gluetun logs, - specific server names I tested, - and speedtest outputs from inside the VPN tunnel. Thank you in advance for any help or hints! Yes i got help from AI english is not my first language -
Thank you! Please use the Configuration Generator. Turn on the "Advanced" switch. Generate a file with the Configuration Generator for WireGuard for the server or country you want to test. Download the file and edit it with any text editor. To begin with, add these parameters in the [Interface] section: Jc = 20 Jmin = 50 Jmax = 1000 S1 = 0 S2 = 0 H1 = 3 H2 = 1 H3 = 4 H4 = 2 Import the file into your PC AmneziaWG client, or use it with the AirVPN Suite component Hummingbird, and even in Eddie 4.0.0 (you can do it in the "VPN profiles" view once the file is in your Android device) and use it to test a connection in Amnezia mode. If it fails please try a connection directly from Eddie, without profile, in Amnezia WG. If it fails too enable QUIC mimicking in "Settings" > "Advanced" > "Custom AmneziaWG directives" and test again a connection. Keep us posted! Kind regards
-
I am just installing Eddie UI and using it. If you provide steps - I am in to test. I am currently on windows 11... Where should I edit [Interface] section? I cannot find any file with that in AirVpn installation folder.
-
Hello! It's available right now if you can edit the generated file. An integration with the configuration generator will require time so we suggest that you test by editing your own file (generated by the CG for WireGuard). Integration with Eddie Android edition is already available in the 4.0.0 beta version. ~100% success at the moment comes from reports from Russia and China. It would be good to have an additional report from Uzbekistan. 😋 Kind regards
-
AmneziaWG may be a good idea, but will require time.. It seams like AirVpn needs to follow these DPI and other restrictions and make sure that customers can just pay and use the service. I am using AirVPN for years and for the first time I was not able to connect to ANY server using ANY available protocol withing Eddie UI.. From Uzbekistan.
-
Up
-
Hello, My AirVPN was working fine 2 days ago but it's not able to connect to any server since yesterday's morning. I don't thing i've change or did anything particular. Here is the logs : . 2025.12.08 09:55:11 - Eddie version: 2.24.6 / windows_x64, System: Windows, Name: Windows 10 Pro, Version: 10.0.26100.0, Framework: v4.0.30319 . 2025.12.08 09:55:12 - Command line arguments (1): path="home" . 2025.12.08 09:55:12 - Collect network information . 2025.12.08 09:55:13 - Reading options from C:\Users\admin\AppData\Local\Eddie\default.profile . 2025.12.08 09:55:13 - OpenVPN - Version: 2.6.12 - OpenSSL 3.3.1 4 Jun 2024, LZO 2.10 (C:\Program Files\AirVPN\openvpn.exe) . 2025.12.08 09:55:13 - SSH - Version: OpenSSH_for_Windows_9.5p2, LibreSSL 3.8.2 (C:\WINDOWS\System32\OpenSSH\\ssh.exe) . 2025.12.08 09:55:13 - SSL - Version: 5.69 (C:\Program Files\AirVPN\stunnel.exe) I 2025.12.08 09:55:14 - Ready . 2025.12.08 09:55:15 - Collect information about AirVPN completed I 2025.12.08 09:55:15 - Session starting. . 2025.12.08 09:55:15 - Activation of Network Lock - Windows Filtering Platform I 2025.12.08 09:55:15 - Checking authorization ... . 2025.12.08 09:55:15 - Collect information about AirVPN completed ! 2025.12.08 09:55:16 - Connecting to Alphard (Netherlands, Alblasserdam) . 2025.12.08 09:55:16 - Routes, add 213.152.187.202/32 for interface "Ethernet (Realtek PCIe GbE Family Controller)". . 2025.12.08 09:55:16 - WireGuard > Setup start E 2025.12.08 09:55:29 - WireGuard > Error: Failed to start: not running . 2025.12.08 09:55:29 - WireGuard > Stopping ! 2025.12.08 09:55:29 - Disconnecting . 2025.12.08 09:55:40 - WireGuard > Completed . 2025.12.08 09:55:40 - Routes, delete 213.152.187.202/32 for interface "Ethernet (Realtek PCIe GbE Family Controller)". . 2025.12.08 09:55:40 - Collect network information . 2025.12.08 09:55:40 - Connection terminated. I 2025.12.08 09:55:43 - Checking authorization ... ! 2025.12.08 09:55:44 - Connecting to Alphard (Netherlands, Alblasserdam) . 2025.12.08 09:55:44 - Routes, add 213.152.187.202/32 for interface "Ethernet (Realtek PCIe GbE Family Controller)". . 2025.12.08 09:55:44 - WireGuard > Setup start E 2025.12.08 09:55:55 - WireGuard > Error: Unable to clean previous ring file (Le processus ne peut pas accéder au fichier car ce fichier est utilisé par un autre processus.) . 2025.12.08 09:55:55 - WireGuard > Stopping ! 2025.12.08 09:55:55 - Disconnecting . 2025.12.08 09:56:06 - WireGuard > Completed . 2025.12.08 09:56:07 - Routes, delete 213.152.187.202/32 for interface "Ethernet (Realtek PCIe GbE Family Controller)". . 2025.12.08 09:56:07 - Collect network information . 2025.12.08 09:56:07 - Connection terminated. I 2025.12.08 09:56:10 - Checking authorization ... ! 2025.12.08 09:56:10 - Connecting to Alphard (Netherlands, Alblasserdam) . 2025.12.08 09:56:10 - Routes, add 213.152.187.202/32 for interface "Ethernet (Realtek PCIe GbE Family Controller)". . 2025.12.08 09:56:10 - WireGuard > Setup start E 2025.12.08 09:56:31 - WireGuard > Error: Failed to start: not running . 2025.12.08 09:56:31 - WireGuard > Stopping ! 2025.12.08 09:56:31 - Disconnecting Could you help me? Kind regards, Michael
-
@Staff I have been using wurren for a long time without issues, getting 600mbit up and down. Since it's being decommissioned, I gave kornephoros a try. Unfortunately, I'm getting significantly slower speeds at 30mbit up and down. Are there any issues with it?
- Last week
-
Care to share some of those?
-
TLS handshake failing on 2/3 servers
Staff replied to bananaphone69's topic in Troubleshooting and Problems
Hello! We're very glad to know that the problem is solved. From the OpenVPN manual: Since mssfix 1280 resolved the problem, a plausible explanation that comes to mind is that before the problem started your network had frames fitting the previous MTU, and this is no more possible now So, it could be a change on your ISP side. Kind regards -
TLS handshake failing on 2/3 servers
bananaphone69 replied to bananaphone69's topic in Troubleshooting and Problems
Hi, thanks for your prompt and helpful response. I will respond to your points in reverse, if that's okay. 1. On some devices I have the ufw/network-manager/ovpn config setup. All of them started failing on certain addresses around one week ago. On a different device where I use wireguard with port 1637, entry3, UDP, I have not had issues with any servers. I can also make an attempt with Eddie or other tools for comparison if that would help. 2. With or without ufw, I was not able to connect to any servers via openvpn CLI. 3. I added mssfix 1280 to the config file for Hercules (a problematic server) and it worked without issue. Adding the same to Libra (a non-problematic server) made no change and it still continues to function as normal. Failing all else, I can add this to all the config files and it should work but I don't understand why this has suddenly happened when I have made no change on the files on my side and about one third still work as normal without the additional mssfix line. Are there other diagnostics or fix attempts that would help clarify the issue? -
HowTo: OPNsense using Wireguard with IPv6 support
twistabled4alt replied to OPN-UserGuide's topic in How-To
Hello @OPN-UserGuide and AirVPN users in general, I've done the tutorial and the IPv4 part is working as intended. The IPv6 on the other hand is not working. Basically when setting up all as in the tutorial, IPv6 traffic works but wouldn't be recognized as it because the IPv6-ICMP pings are wrongly translated and it result in source and destination being the same (in this case the internal VPN IPv6 IP addr). The IPv6 is working on my LAN and I'm able to ping my router from the network. Any help would be greatly appreciated! Have a great day!
