Staff

Hello! Please see here for a quick solution to the quoted critical error: https://airvpn.org/forums/topic/70745-eddie-cant-connect-to-any-server/?do=findComment&comment=249545 Kind regards

Hello! Excellent. We also see the ports as open, we can reach your service(s) from the Internet and we receive back a proper reply. The port tester is successful but remember that the test is only over TCP. Kind regards

Hello! This is an error, please set an IP address for the namespace virtual interface, not a whole subnet. Do you mean that the problem started when you deleted and re-created /etc/netns, or it was solved when you did this? Can you please send us the output of: ls -l /etc Furthermore, please send us the complete Bluetit log, that you can generate with: sudo journalctl | grep bluetit > bluetit.log # if you have systemd based Arch sudo grep bluetit /var/log/syslog > bluetit.log # if you have Arch-systemd-free cuckoo: error while loading shared libraries: libxml2.so.2: cannot open shared object file: No such file or directory Yes, this is a required library. It is pre-installed on many distributions and we considered it as available by default. We shall ponder revising the minimum requisites list, thank you. Kind regards

Hello! Confirmed. This is a bug that has been lurking in the code for a long time (probably since the early 2.0.0 testing versions). It has been addressed so you will see a fix on the next version already. Kind regards

Hello! AMule uses both TCP and UDP protocols for different functions. TCP is primarily used for client-to-client transfers and connections to eDonkey servers, while UDP is used for extended protocol features, according to Wikipedia. For your account you have forwarded a few UDP only ports. Please change them to "TCP and UDP" and test again. Furthermore, if your system is Windows, make sure that the Windows Firewall (or Defender etc.) allows incoming packets for aMule on both private and public networks: if the VPN is considered a public network (check it out) by default incoming packets will be rejected or dropped. Kind regards

Hello! We're glad to inform you that AirVPN Suite 2.1.0 beta 1 is now available. Packages for ARM 64 bit architecture are available as well, if you wish to test. https://airvpn.org/forums/topic/80022-linux-airvpn-suite-210-preview-available/ Kind regards

Hello! We're very glad to inform you that AirVPN 2.1.0 beta 1 is now available. Please check here: https://airvpn.org/forums/topic/80022-linux-airvpn-suite-210-preview-available/ This version includes even more bug fixes and IPv6 management improvements. It is linked against updated libraries. NEW BLUETIT AND GOLDCREST OPTION air-4to6 Enables or disables IPv4 over IPv6 for AirVPN connection. This option is available when the tunnel is built on IPv6, i.e. air-ipv6 on. When air-4to6 option is on or omitted, both IPv4 and IPv6 traffic will be sent over the IPv6 tunnel. Values: on | off . Default: on Kind regards

Hello! Thank for your choice! The infrastructure servers are updated periodically and rebooted on a scheduled, slow rotation to avoid excessive disruptions, except when an urgent update is absolutely necessary. On the 1st of May, an urgent update became essential to address a paramount, critical vulnerability affecting all Linux kernels. Therefore, after having verified that no exploit was attempted on the servers, and after applying a temporary patch preventing the exploit, we proceeded at a rapid pace to update all kernels and reboot the servers in large batches to complete all updates within 24 hours. Kind regards

Hello! Roughly 30% to 50% of peers in a typical Linux distro swarm have working IPv6 connectivity. However, BitTorrent clients or systems may prefer IPv4 and the perceived percentage of IPv6 peers can be dramatically lower. Kind regards

Hello! We can't provide an ETA right now but stay tuned. Are you sure that blocks from Russia are effective when you use QUIC CPS of a real .ru website? According to a few reports, that's good to bypass current blocks. However, it must be said that different ISPs implement different blocking techniques. Kind regards

Hello! Syntax error. Check our previous message and fix accordingly, there's an undue space character between "Nftables" and "TableOwner" that must be deleted, otherwise the option is not recognized. Kind regards

Hello! We already told you where to look at and you already provided evidence of the duplicate and exposing Bluetit's bug, don't worry and thank you. No further action is required at the moment. You must see that Bluetit's warning about exclusive tables ownership disappears and Network Lock now works properly. firewalld exclusive tables ownership prevents Network Lock from working properly on any Suite version, obviously. Kind regards

Hello! Exactly. Add it (you can edit the file with any text editor with root privileges), set it to "no" and verify that the issue gets resolved. NftablesTableOwner=no then re-start firewalld. This is vital to let Bluetit operate "Network Lock" properly. Exclusive ownership of the firewall tables must be pondered on a case by case basis. In this case if you wish to enable "Network Lock" you can't assign exclusive ownership of the tables to firewalld. You have two default routes via 192.168.178.1 on the same interface (enp6s0), one without explicit metric (so metric 0) and one with metric 100. Such duplicates are harmless in general but Bluetit detects them, probably fails to understand that the metric of one of them is 0, and throws a critical error believing that the metric is the same for both. We'll work on the matter carefully. In the meantime just delete the duplicate route and configure your interface either fully static or fully DHCP to keep on testing Kind regards

@colorman Hello and thank you for your tests! This is a critical situation which will cause Network Lock to falter and lead to firewall system settings restore problems. Please fix it according to the quoted instructions. Should you have already adhered to the aforementioned guidance and Bluetit continues to issue that warning, we kindly ask you to apprise us forthwith. This critical error suggests that something goes wrong in Bluetit's gateway(s) detection. Probably the error shall endure even after the prior misconfiguration has been rectified. If so, please send us the output of the following commands: ip a ip route show ip route get 0.0.0.0 Kind regards

Hello! This message has been picked to experiment answers by a selected LLM. The answer has been verified manually and slightly edited. In short, the hops you mention are in Singapore. No changes in Singapore infrastructure took place to justify the change in latency you detect. Operator: locate countries of: vlan12.as06-10g.wco1.sg.m247.ro irb-1906.agg1v.wco1.sg.m247.ro be-2-3111.bb1n.wco1.sg.m247.ro All three hostnames point to infrastructure in Singapore. Here’s how that breaks down: wco1.sg.m247.ro sg is the standard country/location code for Singapore wco1 likely refers to a specific data center or site within that region m247.ro is a Romanian network provider (M247), but they operate globally So for each: vlan12.as06-10g.wco1.sg.m247.ro → Singapore irb-1906.agg1v.wco1.sg.m247.ro → Singapore be-2-3111.bb1n.wco1.sg.m247.ro → Singapore Summary: All three are part of M247’s network presence in Singapore, despite the .ro domain. Operator: Break down names with additional details These hostnames follow fairly typical ISP / backbone naming conventions. Each segment encodes device role, interface, and location. Let’s break them down piece by piece. 🌍 Common suffix (applies to all) m247.ro → Network operated by M247 (Romanian-origin ISP with global PoPs) sg → Singapore wco1 → Likely “West Coast / core site 1” (internal site code for that Singapore PoP) So all three are devices inside the same Singapore location. 1️⃣ vlan12.as06-10g.wco1.sg.m247.ro Breakdown: vlan12 A VLAN interface (Virtual LAN ID 12) Used for logical segmentation inside a router/switch as06-10g as06 → likely “access switch / aggregation switch #6” 10g → 10 Gigabit interface/uplink wco1.sg.m247.ro Location + provider (Singapore PoP) Interpretation: 👉 A VLAN interface (ID 12) on an access/aggregation switch with a 10G link 👉 Likely used for customer traffic or internal segmentation 2️⃣ irb-1906.agg1v.wco1.sg.m247.ro Breakdown: irb-1906 IRB = Integrated Routing and Bridging Interface number 1906 Common on Juniper gear (Layer 3 gateway for a VLAN) agg1v agg → aggregation router/switch 1 → device number v → possibly “virtualized” or variant of the node wco1.sg.m247.ro Same Singapore site Interpretation: 👉 A Layer 3 gateway interface (IRB) on an aggregation router 👉 Handles routing between VLANs or customer subnets 3️⃣ be-2-3111.bb1n.wco1.sg.m247.ro Breakdown: be-2-3111 BE = Bundle Ethernet (port-channel / LAG) 2 → bundle ID 3111 → internal interface identifier bb1n bb → backbone router 1 → device number n → possibly “north” (directional naming is common) wco1.sg.m247.ro Same location Interpretation: 👉 A backbone router interface using a bundled (aggregated) high-capacity link 👉 Likely part of core transit or inter-PoP connectivity 🧠 Big picture (network hierarchy) Putting them together: Access layer → as06-10g (customer-facing / edge connectivity) Aggregation layer → agg1v (traffic consolidation + routing) Backbone/core layer → bb1n (high-capacity transit) This is a classic ISP architecture: Customer VLAN → Access Switch → Aggregation Router → Backbone Router ⚠️ Important note These interpretations are informed guesses, not guaranteed facts. Naming conventions vary by provider, but M247’s style aligns closely with standard ISP practices. Kind regards