Leaderboard

Hello! Thank you. We confirm that Eddie round trip times wrong values can not be related to VPN DNS. To perform the tests the system must be outside the VPN and therefore you can't use VPN DNS. Furthermore, Eddie needn't resolve names to perform the tests. You can therefore keep this issue on its own topic (already existing, we see) and split from this one. Kind regards

Hello! We might have solved the problem, please keep reporting to confirm or deny. If you still find problems please mention the VPN server name(s). @Seebarschtian Thank you! Kind regards

Hi, I do notice some other bugs. After setting the MTU, I seem to be getting some issues whereby on disconnect due to network change, Eddie does not automatically connect back. Unlike the other member, I only set "VPN reconnection". I did not use "VPN always on and block connection without VPN" Removing the MTU seems to solve this issue. However, one issue also arise. When Eddie is connected to one of the servers, when changing from wifi to mobile data, Eddie will disconnect and it will not reconnect back. I have uploaded the log via the app. https://eddie.website/report/d0f694af/

thank you! looks like i can access those apps and services now!

Indeed, I can confirm both ProtonMail and TutaNota apps work fine now with MTU size set to 1280 bytes. I've tried with the following servers: Alruba, Hassaleh, Hyadum, Lehman, Maasym. All good!

Can confirm, the problem does not happen anymore for me. Thanks staff for the fix!

I can confirm, that by todays test, the DNS resolution works with minimal latency in resolving the hostnames. Even the weird nslookup response got away: >nslookup genius.com Server: UnKnown Address: fd7d:76ee:e68f:a993::1 Nicht autorisierende Antwort: Name: genius.com Addresses: 2606:4700::6812:1360 2606:4700::6812:1260 104.18.19.96 104.18.18.96 >nslookup genius.com 10.128.0.1 Server: UnKnown Address: 10.128.0.1 Nicht autorisierende Antwort: Name: genius.com Addresses: 2606:4700::6812:1260 2606:4700::6812:1360 104.18.19.96 104.18.18.96 @Staff Thank you very much for solving the problem.

@seebarschtian - Thanks for raising the ticket. I ran both tests on two machines, one of which had experienced some hesitance earlier. Both tests passed on both machines with no errors. @Staff - Thanks for working on this. Achernar DNS resolution issues early Monday afternoon but okay later. Update - Tuesday morning. DNS tests okay. No immediate lag in browsing. Reported latency errors persist, so maybe they are not DNS related? Top ten servers for best latency as reported by Eddie 2.21.8 Bottom ten:

I opened a ticket a week ago #161998. Last status was: Moved to 2nd Level Support.

I'm also using exclusively OpenVPN connection. Here are few DE servers affected by extremely slow DNS responses: Adhara, Alsephina, Dubhe. On the other hand Cujam and Cervantes work as it should (if it somehow will help to pinpoint this bug)

I just discovered this thread and I'm glad to hear that this issue is being investigated. However, I'm a bit confused by this comment about WireGuard and OpenVPN. I am using Ubuntu Mate 22.04 and have always connected with OpenVPN. I just opened my settings to confirm that it is using OpenVPN, not wireguard, yet I am also experiencing slow DNS issues while connected to AirVPN servers.

I opened a ticket and sent the log results. thanks

This is how I configured AirVPN on a Raspberry Pi 3B for our small home network. With this configuration I was able to use our full download speed of 100 Mbit updating the steam library on a saturday night (ger to ger - frankfurth exit node) I took the time to write this down: a) In the hope someone with actual knowledge might look over it and tell me my divine mistake .. go on, .. won't bite.. promise ! b) it helps people getting their OpenWRT / AirVPN I use LUCI, the OpenWRT browser GUI. I started with a clean base install, updated it and configured the pppoe uplink according to the guides on openwrt.org Then I installed the following packages : openvpn-openssl vpnbypass luci-app-vpnbypass luci-app-openvpn Your Router Menu should now have a new Menu Item : VPN with OpenVPN and VPN Bypass as menu items. (reload F5) Next I created a new Interface in the Network config : Add new Interface .. In the General TAB -->> Name: vpntunnel, Proto: unmanaged, Device -> custom : tun0 In the advanced TAB -->> deselect "Use DNS servers advertised by peer" , Use custom DNS servers : 10.4.0.1 (enter IP and hit +) save + save and apply ! .. it should look something like this. The new tun device throws an error since nothing is connected yet, that's fine for now. Next I created a firewall rule in Network Firewall : Add In the General TAB -->> Name : vpnfirewall , input : reject, output, accept, forward : reject. Masqerading : yes , MSS clamping : yes, covered Network : vpntunnel , allowed destination : unspecified, allowed source : LAN save + save and apply ! .. Next I generated the OpenVPN config : https://airvpn.org/generator/ Select -->> Router , OpenVPN UPD 443 and your country and hit generate. You will get a file with ovpn as suffix. This single file contains everything you need to establish a connection via VPN !! Next I uploaded that file to my router via VPN -> OpenVPN in my router menu. Give it a Name, select the ovpn file and hit upload After enabling and starting the configuration it should look something like this : https://ipleak.net/ now should show only VPN ip addresses. (DNS and exit node.) for your whole LAN network. Mission accomplished. additionally there is the VPN Bypass plugin in case you want to exclude certain local hosts , ports, networks from you VPN connetion. It's usage is simple as a dream ... Here are my network, dhcp, vpn, and firewall config for verification : /etc/config/network config interface 'loopback' option device 'lo' option proto 'static' option ipaddr '127.0.0.1' option netmask '255.0.0.0' config globals 'globals' option ula_prefix 'fd4f:b73d:0b1f::/48' config device option name 'br-lan' option type 'bridge' list ports 'eth0' config interface 'lan' option device 'br-lan' option proto 'static' option netmask '255.255.255.0' option ip6assign '60' option ipaddr '10.1.1.1' config interface 'WAN' option proto 'pppoe' option ipv6 'auto' option username 'username@provider.de' option password '12345678' option device 'eth1.7' config device option type '8021q' option ifname 'eth1' option vid '7' option name 'eth1.7' option acceptlocal '1' config interface 'vpntunnel' option proto 'none' option device 'tun0' option peerdns '0' list dns '10.4.0.1' /etc/config/dhcp config dnsmasq option domainneeded '1' option boguspriv '1' option filterwin2k '0' option localise_queries '1' option rebind_protection '1' option rebind_localhost '1' option local '/lan/' option domain 'lan' option expandhosts '1' option nonegcache '0' option authoritative '1' option readethers '1' option leasefile '/tmp/dhcp.leases' option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto' option nonwildcard '1' option localservice '1' option ednspacket_max '1232' config dhcp 'lan' option interface 'lan' option start '100' option limit '150' option leasetime '12h' option dhcpv4 'server' option force '1' option master '1' list ra_flags 'none' config dhcp 'wan' option interface 'wan' option ignore '1' config odhcpd 'odhcpd' option maindhcp '0' option leasefile '/tmp/hosts/odhcpd' option leasetrigger '/usr/sbin/odhcpd-update' option loglevel '4' /etc/config/openvpn config openvpn 'airvpnger' option config '/etc/openvpn/airvpnger.ovpn' option enabled '1' /etc/config/firewall config defaults option input 'ACCEPT' option output 'ACCEPT' option forward 'REJECT' option synflood_protect '1' config zone option name 'lan' option input 'ACCEPT' option output 'ACCEPT' option forward 'ACCEPT' list network 'lan' config zone option name 'wan' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' option masq '1' option mtu_fix '1' list network 'wan' list network 'wan6' list network 'WAN' config forwarding option src 'lan' option dest 'wan' config rule option name 'Allow-DHCP-Renew' option src 'wan' option proto 'udp' option dest_port '68' option target 'ACCEPT' option family 'ipv4' config rule option name 'Allow-Ping' option src 'wan' option proto 'icmp' option icmp_type 'echo-request' option family 'ipv4' option target 'ACCEPT' config rule option name 'Allow-IGMP' option src 'wan' option proto 'igmp' option family 'ipv4' option target 'ACCEPT' config rule option name 'Allow-DHCPv6' option src 'wan' option proto 'udp' option src_ip 'fc00::/6' option dest_ip 'fc00::/6' option dest_port '546' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-MLD' option src 'wan' option proto 'icmp' option src_ip 'fe80::/10' list icmp_type '130/0' list icmp_type '131/0' list icmp_type '132/0' list icmp_type '143/0' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-ICMPv6-Input' option src 'wan' option proto 'icmp' list icmp_type 'echo-request' list icmp_type 'echo-reply' list icmp_type 'destination-unreachable' list icmp_type 'packet-too-big' list icmp_type 'time-exceeded' list icmp_type 'bad-header' list icmp_type 'unknown-header-type' list icmp_type 'router-solicitation' list icmp_type 'neighbour-solicitation' list icmp_type 'router-advertisement' list icmp_type 'neighbour-advertisement' option limit '1000/sec' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-ICMPv6-Forward' option src 'wan' option dest '*' option proto 'icmp' list icmp_type 'echo-request' list icmp_type 'echo-reply' list icmp_type 'destination-unreachable' list icmp_type 'packet-too-big' list icmp_type 'time-exceeded' list icmp_type 'bad-header' list icmp_type 'unknown-header-type' option limit '1000/sec' option family 'ipv6' option target 'ACCEPT' config rule option name 'Allow-IPSec-ESP' option src 'wan' option dest 'lan' option proto 'esp' option target 'ACCEPT' config rule option name 'Allow-ISAKMP' option src 'wan' option dest 'lan' option dest_port '500' option proto 'udp' option target 'ACCEPT' config rule option name 'Support-UDP-Traceroute' option src 'wan' option dest_port '33434:33689' option proto 'udp' option family 'ipv4' option target 'REJECT' option enabled 'false' config include option path '/etc/firewall.user' config zone option name 'vpnfirewall' option input 'REJECT' option output 'ACCEPT' option forward 'REJECT' option mtu_fix '1' list network 'vpntunnel' option masq '1' config forwarding option src 'lan' option dest 'vpnfirewall'

Blatantly looks like they don't particularly like OpenVPN traffic. Try connecting using OpenVPN over SSL or SSH (with Eddie).

@StaliniumComodo config files Windows 7 and Windows 10 are already posted(last-link below) @OpenSorcerer request to re-post them. Have a lot of fun

Hi there, I really love your service and will renew with the next big sale event. Being able to pay with crypto currencies is a must in the industry nowadays I find. I am glad you accept a variety of different currencies, especially Monero. Bitcoin payments are oftentimes prohibitively expensive due to high mining fees to get into the next block. Also they can take a long time if the mempool is overflowing with unprocessed transactions. It would be great if you could also accept payments over the lightning network which makes transactions instant and final for you, basically free for me to send and my service can be instantly activated instead of having to wait a certain amount for blocks to be mined. Integrating lightning payments is easy, free and secure. And even comes with some privacy improvements over regular Bitcoin transactions, so that nobody knows who paid you. please consider adding lightning support to make paying with Bitcoin cheaper, faster and more private while also reducing the load on the main blockchain. Resources like BTCpay Server make it easy to accept lightning payments along regular on-chain transactions all without a third party. Thank you so much, I am looking forward to opening a channel to you ! ☺️

Wow, a guide! Thank you very much for the work you put into it. I'll probably test it out one of these days. This is false. It is available and working as intended on Linux. This is true, though. But in all fairness, most directives in OpenVPN refer to v4 only. One thing came to mind when I read this:

I hate to revive such an old thread, but I wanted to share what fixed it in case it helps anyone in the future. I have a separate OpenVPN server running on my pfSense box that I use for remote access purposes. For some reason, this was conflicting with AirVPN, and I solved my problem by deleting all of the rules under Firewall -> Rules -> OpenVPN (my OpenVPN server, not AirVPN).