Leaderboard

@eburom Thank you very much! The problem you found and kindly reported has been fixed and you'll see the fix in the next, imminent version. From the developer: you can't build the Suite now because OpenVPN3 has recently changed ClientAPI::Config definition. They replaced member ipv6 with allowUnusedAddrFamilies which is basically used for the very same purpose. The change has been already imported into OpenVPN3-AirVPN 3.7.1 fork and Bluetit/Hummingbird code has been updated accordingly in the development branch which is to be released very soon, along with some other minor fixes and changes [including the aforementioned one}. Kind regards

Hello @Staff , I tried running this command in Monterey 12.1 and I got sysctl: unknown oid 'kern.ipc.maxsockbuf' and I tried this command Also : sudo sysctl -w kern.ipc.maxsockbuf=33554432 and I got this : sysctl: kern.ipc.maxsockbuf=33554432: Result too large any ideas ? maybe try smaller buffer ? Edit : I tried sudo sysctl -w kern.ipc.maxsockbuf=16554432 and I got : kern.ipc.maxsockbuf: 8388608 -> 16554432 it's seems that 16mb was accepted unlike the 32 I'll test and report back.

Not entirely sure it's possible. This one is Alya. Its primary TLS-Auth IP is .170 and comes up if you query ca.all.vpn.airdns.org. Well, it's not forbidden to run exit nodes behind AirVPN servers, only recommended against to avoid exactly these kinds of incidents. But egoists gotta be egoists. I can neither confirm nor deny it, but it's a strong indication that it is triggering it. Also, please don't try to use VPNs at your workplace if they are expressly forbidden or you can otherwise be held accountable for using one.

Hello everybody, can you please re-perform all of your tests and report back? We have found a bug which potentially might have caused the reported names resolution failures and we have fixed the code. Please let us know whether the problems keeps occurring or not, as our automated DNS testing sentinels deployed on several flag servers have stopped reporting resolution failures since when the fix was applied. A couple of hours ago the fix has been deployed on all the VPN servers. We are looking forward to hearing from you. Kind regards

That Pull option is not set, I believe it corresponds to --pull which is a necessity. --pull This option must be used on a client which is connecting to a multi-client server. It indicates to OpenVPN that it should accept options pushed by the server, provided they are part of the legal set of pushable options (note that the --pull option is implied by --client ). Not sure if your app implies --client. I'd say, try ticking Pull.

Check if the DNS servers are reset back to DHCP, or whatever the normal setting is for you. Here's how to do the reset.

AirVPN Suite does work fine with Slackware 15.0 RC3 64bit, but I suggest to make the change noted below. I have noticed Intermittent issues with IPv6 on my system with my ISP. This assumes you are using Network Manager, which is setup via /sbin/netconfig You should edit file /etc/NetworkManager/conf.d/00-dhcp-client.conf and comment out line 'dhcp=dhcpcd' then uncomment line 'dhcp=dhclient'. Doing that all works fine after a reboot to reset dhcp. Well spoke too soon, above does work most of the time, but I suspect there is an issue in Slackware with its dbus. Once in a great while IPv6 causes problems with goldcrest (or bluetit or my ISP). I will play around and respond here if I track down the issue.

Yeah, good idea and I don't know why I didn't think of that. I did have the secure DNS setting on and have now turned it off. I'll try if for a few days and come back if it fixed the problem. Follow-up - a couple of days after turning off the secure DNS option in Brave, and no messages so far. For what it's worth, I also have DNSSEC enabled on my pfSense router "DNS Resolver" service, pointing to 1.1.1.1 / 1.1.1.2. So whether I am on AirVPN or not, I have a secure DNS connection.

I see. Issue seems to be Brave-specific and points to the issue of the configured Secure DNS provider not being reachable. Disable it, it makes little sense in the VPN network.

Hello! We confirm that it's not possible for Eddie to start during the bootstrap of any un-rooted device running Android TV 10, 11 and 12, and this is not an Eddie-specific limitation, simply because "Always on VPN" has become mandatory for the purpose, but at the same time Android TV has always had this feature removed. Should we find a solution to circumvent this deliberate limitation on un-rooted devices, we will be willing to implement it, but at the moment we are not aware of any solution. OpenVPN connect, OpenVPN for Android and other apps undergo the very same limitation. Kind regards

@m1ster Hello! You can't build Hummingbird or the AirPVN Suite in FreeBSD because OpenVPN3 AirVPN library needs various modification for FreeBSD, you will not be able to even compile it at the moment. We have plans to port the AirVPN Suite to FreeBSD later this year, but first we need to adapt the library, which might be or not a trivial task, and we must release a new Eddie Android edition version before the summer is over. At the moment you only have the Linux binary compatibility mode option (try with Hummingbird, as Eddie will have too many complications due to Mono), and of course OpenVPN 2.5.2. Hummingbird and the Suite support and have always supported pf, the default FreeBSD firewall, but different directory tree and some other issue may cause trouble. https://docs.freebsd.org/en/books/handbook/linuxemu/ Anyway we assure you that FreeBSD support improvement with native applications remains our goal for 2021. Our FreeBSD users are many (25% of our Windows customers, and 20% of our Linux customers, who are currently the absolute majority), not to mention the system outstanding superiority, so stay tuned. Kind regards

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: