Not connected, Your IP: 216.73.216.117
Online: 40081 users - 438191 Mbit/s total BWAll Activity
This stream auto-updates
- Past hour
-
-
-
- Today
-
-
-
-
Seems to work again. Might have just caught the server during a bad time. All good now.
-
-
-
-
-
-
-
-
-
- Yesterday
-
-
Hello, I had a functioniong Gluetun setup, but it seems I can no longer functionally connect to the Server Achenar. I assume something is wrong with that server, somehow. I did not change anything on my side of the set up. Can any one of you confirm or deny? Thank you.
-
Thank you for providing clarity on the issue and your commitment to providing a secure environment.
-
-
-
ANSWERED Configuring White listed servers and traffic splitting
0bacon replied to 0bacon's topic in AirVPN Suite
I think it had something to do with Fedora, specifically the SELinux. I switched to Arch and everything went smoothly. -
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
-
-
DeepAnger reacted to a post in a topic:
Ratio (percentage) of IPv4 vs IPv6 peers in your torrents ? ...
-
.thumb.png.8be84fd39f94c1640ac8c5456fbf3449.png)
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 -
- Last week
-
Hello, Ive been using AirVPN for about a year now, but recently all servers have had extremely high latency and very low speeds, before I was capable of atleast 50mb or so now Im lucky to get into triple digits of kbits, Ive tried reinstalling and updating nothing worked.
-
It is what it is -
Is this a planned maintenance or something? I've got multiple paid accounts and am using 15 sessions on a variety of different VPNs. Over half of them have abruptly gone out at some point today.
-
Esurient, i'm curious what is the baseline server you're using for the baseline test ? What is the max speed you normally reach with your line ? Cause to me with a baseline 350MB up and down and you got more speed, you've an issue with your baseline test being capped. So far i'm able to get 1,1GB on a VPN speedtest on a 2.5GB line and i have them without VPN. Not that it is an issue, most of the time there is no no possibility to reach that speed in my use anyway. But i wonder why. Edit : FYI, updating the MTU from 1320 to 1400 in Eddie has me going up from 1,1GB to 1,4GB in the same conditions. Imo watch out the speedtest limitations, it may very well depends on what server you're using for the test.
-
I have recently been able to add IPv6 to my LAN (but ULA only to avoid IPv6 leaks) and add a port forward in my OpenWrt router that acts as a Wireguard client for a Windows qBittorrent client in my Ethernet LAN. Everything seems to work fine and I've been able to reach the "Top User Speed" a few times while seeding to around 800 peers. But the one thing that annoys me is that IPv6 traffic appears way too low compared to IPv4, usually between 5 to 10 % (90 % or more for IPv4). I have tried some online speed tests that can do both IPv4 and IPv6 and I saw no huge difference between the two. Then I tried to select IPv6 only in qBittorrent and restarted it. After a few minutes, I got only 80 peers (instead of 800; look at the graph). The AirVPN, forwarded ports, test open, confirms that both IPv4 and IPv6 port I selected for torrents are "Open!". I can't believe that only 5% of torrent users have IPv6 so there must be a problem in my installation. For those who use a computer as a seed-box with both IPv4 and IPv6, how many peers do you see connected in IPv6 (compared to IPv4) ? -
-
Please close Eddie, reopen, retry a connection, then provide a system report:.
-
-
-
The reason there is leakage is that you'retch not NAT'ing the traffic from the Synology to AirVPN. My suggestion is to do the following: For the purposes of this guide, I'll call whatever device you're using to access the OpenWRT Web Interface as "laptop", but in reality, it can be a desktop, smartphone, tablet, or anything else with a web browser. (Topmost Menu is the Black Bar of OpenWRT LUCI, which has, by default: OpenWRT, Status, System, Network,Tools): 1. Reset your OpenWRT router to default settings(but the firmware should still be OpenWRT, not the stock firmware). 2.For now, Just plug your laptop into a LAN port so you can configure the router according to the next steps here and the WAN port to your pre-existing network, so that you can install Wireguard . 3. Install the OpenWRT Package for Wireguard 4. Download the AirVPN config file you want to use onto your laptop. 5. Disconnect the router from your pre-existing network that was attached via the WAN port, but leave your laptop plugged in. From here on out, you will not have internet access as you're configuring the OpenWRT router, but you will regain it later at the step where I tell you to reattach the cable from the network to your OpenWRT. You MUST do this, else the next step will fail. DO NOT plug your pre-existing network into any hole on the OpenWRT till you reach the step where I tell you to do so. 4. !!!VERY IMPORTANT!!! PLEASE READ THIS STEP IN FULL, INCLUDING THE EXPLANATION AT THE END Go to Network>Switch and assign 1 port to VLAN 1(We'll use this for LAN) and VLAN 2(We'll use this for your NAS). To assign a router port to a VLAN, within a single row, select "untagged" for the port you want to assign to the VLAN, "off" for very other port, and "tagged" for CPU(eth0). Your table can look like this(I'm going to write it out in JSON-style, where a JSON single object is a table row, the key is a column header, and the value is either what you write in the empty box or select from a dropdown in the empty box. I'm doing this because actually recreating a table in text is more challenging than I'd like) {VLAN ID:1, Description:"", CPU(eth0): tagged, LAN 1: untagged, LAN 2: untagged, LAN 3: off, LAN 4: off, WAN: off }, {VLAN ID:2, Description:"", CPU(eth0): tagged, LAN 1: off, LAN 2: off, LAN 3: off, LAN 4: off, WAN: untagged }, {VLAN ID:3, Description:"For NewLAN", CPU(eth0): tagged, LAN 1: off, LAN 2: off, LAN 3: untagged, LAN 4: off, WAN: off }, {VLAN ID:4, Description:"For NAS", CPU(eth0): tagged, LAN 1: off, LAN 2: off, LAN 3: off, LAN 4: untagged, WAN: off } You're free to choose different ports than what I choose here, as long as your choices are consistent between this step and the following steps. Notice that when I donate a port to NAS and to NewLAN, I remove those same ports from LAN. That is, when I mark them as untagged for the New VLANS I create, I mark them as off for the pre-existing LAN bridge. Whatever you do, DO NOT donate the port that your laptop is currently plugged into to NewLAN or to NAS. 5. Go to the Network>Interfaces Section of OpenWRT and create 3 interfaces, NewLAN, AirVPN(This is what I'll call your Wireguard Interface from now on), and NAS. 5.1.Set the Device of NewLAN to the VLAN ID 3 from earlier, then give it an IP address that is in the same subnet as your pre-existing LAN(i.e. if your pre-existing LAN's gateway is 192.168.1.1, then a potentially nice candidate is 192.168.1.254, if you don't have another device sitting there yet), but not part of the DHCP range. Set the gateway to be the address of your pre-existing router. DO NOT plug the OpenWRT into your pre-existing LAN yet. DO NOT enable DHCP Server on this interface 5.2. Set the Device of NAS to VLAN ID 4. Then, give this interface an IP address that is outside your pre-existing subnet, and also that is not in AirVPN's IP 10.0.0.0/8 range. For example, if your pre-existing LAN is 192.168.1.0/24, then make this interface have address 192.168.2.1. If you have more than 1 LAN, choose a new address that is not part of any network you have yet. Enable DHCP Server on this interface. Set the MTU to be the same as the MTU of your Wireguard conf from AirVPN. 5.3. Copy the Wireguard config file into the AirVPN interface. You will be able to select the Device to bind the new interface to in the Device: field after clicking the "Add new interface..." button in network Interfaces. Do not assign any pre-existing firewall zone to any of these new interfaces. Create a new zone for each. 6. In Network>Firewall, if these zones do not exist yet, create 3 new zones called NewLAN, NAS, and AirVPN. Enable Masquerading for all of these interfaces. Allow NAS to forward to AirVPN. Allow NewLAN to forward to NAS. Allow INPUT, OUTPUT, and Intrazone Forward for NewLan and NAS. Allow OUTPUT but block INPUT and Intrazone Forward for AirVPN. If they already exist, still configure them as I told you. 7. Go back to Network>Interfaces, then edit NewLAN, AirVPN, and NAS interfaces. For each of them go to the Firewall Settings tab (visible after clicking Edit) and set each interface to the firewall zone with the same name. 8. Plug your pre-existing router into the port you donated to NewLAN. 9. Plug your NAS into the ethernet port you donated to NAS. 10. Find out what the IP of the NAS is from Status->Overview and scrolling down. 11. Go to Network->DHCP and DNS->Static Leases and add a static lease for the NAS using the IP address you learned from step 10. Set the lease time to infinite 12. Go to Network->Firewall->Port Forwards and Add a Rule. Specify AirVPN as Source Zone and NAS as Destination Zone. Fill Internal Address with what you learned from step 10. Try your best to make the internal and external port the same. If you cannot, either remap the port from AirVPN's Port Forward page in the Client Area or here in OpenWRT's Port Forward Window. 12. Activate the Wireguard Profile 13. Test the setup 14. Please report the results back here. If there is an error in this guide, let me know so I can correct it. -
Hagezi is great, and i mean great. I exclusively use their Ultimate list and get virtually zero false positives, and when there is one they are the fastest to remove it (even if i never encountered one, whereas i used to a lot with other lists). If the Air team adds it I hope they consider the Ultimate and Pro++, not only Pro. If you feel like it i consider giving it a chance as well!
-
Got this message today on Tahoe. I know it could be a while before they shut down Rosetta but this message may alarm some Mac users.
-
Little update. After i was advised to use Wireguard and that the NAS did not provide any native support i remembered i had an old tplink archer C7 lying around and wondered if i could do a middle box of it. Long story short : I flashed it for openwrt, made it a dumb ethernet access point (no WAN, no DHCP, no wifi), installed wireguard and managed to setup airvpn. I then connected the nas to it but now i have a bit of an issue : dumb AP works as even with the openwrt router between may main gateway (isp box) and the NAS i can find it and access the DSM UI fine but then when i activate the wireguard interface i loose connexion. The connexion from my PC is wifi to ISP box then ethernet to openwrt then nas. My take is that the wireguard interface tunnels all to the airvpn exit node and there is no way for me to reach the nas from the LAN with it's local IP) Is there a way to dissociate so that the WG connexion is only for outside of the actual LAN (the DSM VPN system did that perfectly) ? May be some port routing black magic (because honestly i only need the torrent to go trhough the vpn, rest not so much) BTW also noticed that with the WG interface activated, the tailscale network i use to reach the nas from outside loose trace of it when it never did it with the openvpn on DSM. EDIT : after tweaking for hours i now have access to the devices after the router but the traffic doesn't go to the router and ip leak test show my torrents on my own. I found places where they seem to think that dumb AP and vpn client just don't work as the principle of dumb AP is to be transparent. -
HowTo: OPNsense using Wireguard with IPv6 support
DeepAnger replied to OPN-UserGuide's topic in How-To
I could have a public IPv6 from my ISP (in relay mode because they don't give PD) but I decided not to use them. I don't use pfsense but I disabled the wan6 interface and made the LAN to act as a DHCPv6 and SLAAC server. For the port forwarding to work (on OpenWrt) I had to define a port forward rule (from WAN and VPN to a LAN device) and a traffic rule. IPv6 masquerading is needed too for outbound traffic on the WAN+VPN firewall zone. Now, I have both IPv4 and IPv6 working for my selected ports to forward on the LAN (and a perfect result on ipleak.net site). -
Hi there, I'm trying to get Eddie to run on a headless server. Instead of running -user=xx -pass=yy in the terminal, I'd like to get the profile to remember user/pass. However, this seems impossible: https://airvpn.org/forums/topic/79263-eddie-cli-remember-not-remembering/?tab=comments#comment-261130 Did anyone find a workaround for this situation? Since the default.profile file is encrypted, copying it from another machine wont work.
-
That's a great feature to have so at least keeps you protected. prevent app or the os from making queries out side of the vpn making easier for your isp to see what you are searching for
-
HowTo: OPNsense using Wireguard with IPv6 support
Joe Bleau replied to OPN-UserGuide's topic in How-To
I don't have an IPv6 address from my ISP so I have my own local ipv6 network. Some people consider this setup broken as ipv6 addresses are supposed to be globally unique and handed out by ISPs. -
Internet Blocked When Eddie VPN off
bijour replied to VortexSimp482's topic in Eddie - AirVPN Client
If you think you've an issue with your routeur or your ISP, then go inside your routeur launch your routeur diagnostics to see if you have internet before you toss everything away. I'd disable the auto connect on startup in Eddie and the network lock, then close Eddie. If need be reset the connexions in the network and sharing center. And reboot the computer. Your DHCP should be ok. Then see whats hapenning with putting back Eddie. If you've renewed your public key in your client area, you may get somes issues with Eddie still using your previous key. I've already made a fool of myself with a distant computer because Eddie is not automatically relocking with the new certificate so the computer was unreachable. -
Is this the kind of socks5 proxy?
-
Well i think that's a new Download speed record if i'm not mistaken using Toliman in Switzerland via gluetun used for qbt only although i'm curious why upload is drasticly lower i've symetrical 8gbps fiber line so that's not it and when i run that on my host network i get 7gbps down 5/6gbps up using wireguard config on port 1637 mtu of host is at 1500 mtu of wireguard tunnel is 1320 will keep trying by increasing that to 1420 which is the theoritical best value edit 1 : new record with mtu 1420 seems to be the highest i can get to avoid fragmentation
-
I tried many script found in this forum, but seems all not work for me 1. I connected to a random server by using AirVPN UI 2. Start the "ROTATING Script" 3. I use what is my IP to check my public IP, every 24 hours, no change. Anything I did wrong ? How to make my AprVPN rotating server every 15 mins ? Please help !
-
-
-
-
-
-
I have a Unifi Dream Machine SE (UDM-SE), configured AirVPN with wireguard client inside of it. I am trying to force all traffic inbound/outbound of my qBittorent lxc through the wireguard client. I can download torrents just fine, but I am unable to seed and upload for anyone which is killing my tracker ratio. On the UDM-SE I have LAN-In firewall rule to allow anything from my AirVPN going to my qBittorrent, I have a DNAT from any traffic on the specific AirVPN port to be translated to the qBittorrent IP, I have a policy based route taking any traffic from my qbittorrent and sending through the wireguard client. I have qbittorrent listening on the forwarded port. I'm at a loss as to "Test Open" is failing for the forwarded port I have. I'd greatly appreciate a look over from anyone
