Jump to content
Not connected, Your IP: 52.14.110.171

Leaderboard


Popular Content

Showing content with the highest reputation on 11/16/24 in all areas

  1. 2 points
    mp92

    I like AirVPN

    Hi, I just wanted to say I appreciate the simple, easy 3 day trial. I have one more thing I want to try tonight, but I really like this website, I like the ease of the app and connection, and from looking around the forum, it appears the community is competent and very friendly. I unfortunately do not have the budget to purchase a 3 year plan at the present moment, so I will wait for the next sale and make sure I purchase 3 years. Thank you all!
  2. 1 point
    Rotciv

    Provide sub-regions for US region

    Provide sub-regions for US region, perhaps useast.airvpn.org, uscentral.airvpn.org, and uspacific.airvpn.org? This will minimize latency on games that try to connect you to the closest server by having your exit ip to be in the same area. Manually managing the different local region servers is a pain when some are offline while others have high packet loss. It would be nice to be connected to the best performing local region server and not the one across the country.
  3. 1 point
    Hi! Please see here: https://airvpn.org/forums/topic/56430-road-to-openvpn-26-and-dco/?do=findComment&comment=226017 On https://github.com/OpenVPN/ovpn-dco: As we wrote, we are not inclined to deploy something under heavy development that can change radically. Furthermore DCO development has been very slow in the last three years and the interest around OpenVPN DCO is fading away with at least one major VPN provider dropping OpenVPN completely in 2026 (not DCO, OpenVPN in its entirety). We'll see whether the DCO can reach a stable release and if/when the developers release something stable we will re-evaluate the matter for sure. Please check before writing the "road to OpenVPN 2.6" here: https://airvpn.org/road_to_openvpn26/ where you can read that the beta testing phase will be ongoing "Until openvpn-dco stable version is released". After a stable version is released we would start the migration phase. Kind regards
  4. 1 point
    Hello! The most common causes are a "dirty" line and an MTU related problem. Please try to get a stronger WiFi signal, change WiFi channel, test a different Ethernet cable, make sure that network interface driver and router firmware are both up to date. Also set WireGuard's virtual network interface MTU down to 1280 bytes. You will need Eddie 2.24.x to do it, as older versions do not offer an option to modify MTU (so WireGuard default value is enforced). In Eddie 2.24.x please select Preferences > WireGuard, set MTU to 1280 bytes, click Save and test connections to various servers. Kind regards
×
×
  • Create New...