Jump to content
Not connected, Your IP: 216.73.216.171

Staff

Staff
  • Content Count

    11391
  • Joined

    ...
  • Last visited

    ...
  • Days Won

    1979

Staff last won the day on July 2

Staff had the most liked content!

About Staff

  • Rank
    AirVPN Team
  • Birthday 05/28/2010

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello! After the hardware replacement the server is apparently working very well. Should you find any anomaly do not hesitate to warn us and/or update this thread. Kind regards
  2. @name8828 Hello! Please read here: https://airvpn.org/faq/port_forwarding We kindly invite you and everyone to read manuals and FAQ answers before posting. Kind regards
  3. Hello! The problem has been finally isolated. From the provider customer service, just a few hours ago: "We have located the issue with the cabling, and have asked to [...] swap cables and ports around. This will correct the issue. [...] We expect this work to be completed within 24hrs". Kind regards
  4. Hello! Sulafat is now up. The problem was that some of its IP addresses remained null-routed after a flood attack. Kind regards
  5. Thank you, under investigation. screen or any other multiplexer is unnecessary thanks to the async mode (option --async). We will keep you posted. Kind regards
  6. @Pwbkkee Hello and thank you for your tests! Please post at your convenience the complete Bluetit log to let us investigate. Suite components are designed after a client-daemon architecture, where Bluetit is a real daemon (not a generic service, a real daemon) and Goldcrest is a client. Your setup is odd and poses a few problems, since you turn a client into a service and you try to have a service-service arch. What is it that you can't do with current architecture that forces you into this sort of aberration? For example, in your case if you want Bluetit to connect by itself you don't need an auxiliary service, you can do it through the run control directives in bluetit.rc file and you would have a connection as soon as Bluetit comes up, instead of being forced to wait for yet another service to come up. Kind regards
  7. Hello! Yes, a problem with the network interface arose, we're sorry. We are bringing the server down. We will work with the datacenter technicians to resolve the issue. Kind regards
  8. Hello! We're very glad to inform you that a new 10 Gbit/s full duplex server located in Toronto (Ontario, Canada), is available: Kornephoros. The AirVPN client will show automatically the new server; if you use any other OpenVPN or WireGuard client you can generate all the files to access it through our configuration/certificates/key generator (menu "Client Area"->"Config generator"). The server accepts connections on ports 53, 80, 443, 1194, 2018 UDP and TCP for OpenVPN and ports 1637, 47107 and 51820 UDP for WireGuard. Kornephoros supports OpenVPN over SSL and OpenVPN over SSH, TLS 1.3, OpenVPN tls-crypt and WireGuard. Full IPv6 support is included as well. As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses. You can check the status as usual in our real time servers monitor . Do not hesitate to contact us for any information or issue. Kind regards & datalove AirVPN Staff
  9. Hello! Thanks, this is a matter for GlueTun developer, we would recommend that you contact him and explain the problem. Please note that in the compose file you set a variable with the = char, not with : . Kind regards
  10. Hello! When VPN_SERVICE_PROVIDER is set to airvpn the optional environment variables deciding the end point are: SERVER_COUNTRIES: Comma separated list of countries SERVER_REGIONS: Comma separated list of regions SERVER_CITIES: Comma separated list of cities SERVER_NAMES: Comma separated list of server names SERVER_HOSTNAMES: Comma separated list of server hostnames https://github.com/qdm12/gluetun-wiki/blob/main/setup/providers/airvpn.md If you feel that this is a bug or unexpected behavior (we see your point: WIREGUARD_ENDPOINT_IP should not be ignored when a non-generic VPN provider is selected, as it apparently happens in your case), the matter should be reported to GlueTun's developer. Please keep in mind that GlueTun is fully compatible and well integrated with AirVPN but it is not developed by AirVPN so every issue should be reported properly also here: https://github.com/qdm12/gluetun-wiki/issues Kind regards
  11. Hello! Your setup is fine and we can reach your listening software through the port that you remotely forwarded. If you need more ports please make sure to pick a free port (the proper tools on the bottom of your AirVPN account port panel will let you find free ports) or just let the system pick a free one for you by leaving the "Port number" field blank and clicking the '+' button. Kind regards
  12. Hello! Thank you! No reason apart from obsolescence of the announcement. Build is anyway for M1. Kind regards
  13. I am also interested in this, but I didn't get it working. Could you please provide more details on how to set it up? A few snippets for the Powershell would be very helpful. Allowing DHCP traffic out, seems to be an default rule with Windows 10. Hello! Something like this will do the trick, starting from a clean status and Windows Firewall enabled. Make sure you operate from a Powershell with administrator privileges. The rules will survive at reboot. You must adjust your local network address/netmask (change 192.168.0.0/16 and fe80::/10 if necessary). Do not proceed if you don't understand exactly every single command; instead, get documented first. netsh advfirewall set allprofiles firewallpolicy blockoutbound netsh advfirewall firewall add rule name="Allow DHCPv4" protocol=UDP dir=out localport=67,68 action=allow netsh advfirewall firewall add rule name="Allow DHCPv6" protocol=UDP dir=out localport=546,547 action=allow netsh advfirewall firewall add rule name="Allow Local IPv4 Network" protocol=TCP dir=out remoteip=192.168.0.0/16 action=allow netsh advfirewall firewall add rule name="Allow Local IPv6 Network" protocol=TCP dir=out remoteip=fe80::/10 action=allow You may also consider to backup the rules and enable them only when needed, instead of keeping them permanent. Check your system manual to do this. Kind regard
  14. Hello! Yes, perfectly possible. Just configure your application(s) to connect to your proxy and use it/them while the system is connected to the VPN. Kind regards
  15. @Hitotsume Hello! Traffic splitting on a destination address basis is not implemented in the Suite and as a consequence exceptions to Network Lock are not available from the options: you would need to add specific rule(s) after the lock has been enforced. However, in your case this is not necessary as Network Lock already allows local networks. Furthermore, the Suite may take care to avoid VPN traffic tunneling into the local network even with WireGuard (default behavior). The behavior can be set through the specific option allowprivatenetwork as you might already know from the manual: * allowprivatenetwork (yes/no) Control how the local and private network traffic can pass through the Network Lock. When disabled, only VPN traffic is allowed through the Network Lock. When enabled local and private network traffic, as well as VPN traffic, is allowed to pass through the Network Lock. Default: yes Please note that WireGuard support and configuration of Network Lock behavior for local network are implemented on AirVPN Suite 2.0.0, currently available as Release Candidate 2: https://airvpn.org/forums/topic/66706-linux-airvpn-suite-200-preview-available/ AirVPN Suite 2.0.0 also implements traffic splitting on an application basis. Although not required in your specific case, since from your description it sounds like you need to connect to sshd only locally, in various scenarios per app traffic splitting may be more useful and/or a valid replacement of traffic splitting on a destination basis. In your case, if you need to have sshd traffic outside the VPN tunnel (i.e. you explicitly want to leak SSH traffic outside the VPN tunnel so that you can reach sshd from the Internet without pointing to AirVPN server addresses and without AirVPN remote port forwarding) it's preferable to just split ssh traffic (read the 2.0.0 user's manual to achieve in a very simple way this purpose if it is necessary). Kind regards
×
×
  • Create New...