Jump to content
Not connected, Your IP: 216.73.217.173

Search the Community

Showing results for tags 'nat'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • AirVPN
    • News and Announcement
    • How-To
    • Databases
  • Community
    • General & Suggestions
    • Troubleshooting and Problems
    • Eddie - AirVPN Client
    • AirVPN Suite
    • Third party software
    • DNS Lists
    • Blocked websites warning
    • Reviews
    • Other VPN competitors or features
    • Nonprofit
    • Off-Topic
  • Other Projects
    • IP Leak
    • XMPP

Product Groups

  • AirVPN Access
  • Coupons
  • Misc

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Mastodon


AIM


MSN


ICQ


Yahoo


XMPP / Jabber


Skype


Location


Interests

Found 3 results

  1. AirVPN has decent IPv6 support (certainly the best I've seen from VPN providers). However, they still use NAT66 on the server side, and configure tunnels with a single Unique Local Address (ULA) [fd00::/128]. This results in some weird behavior over native IPv6 (with Global Unicast Addresses (GUAs) [2000::/128] in the tunnel): - Clients don't know their real v6 address. - Most software prefers IPv6 GUA over IPv4 over IPv6 ULA, causing IPv4 to be used even if IPv6 is available. - NAT66 can cause some weird behavior as well. My question is why this design was chosen, other than that it mirrors the v4 side 1:1. Given that IPv6 isn't in short supply and it appears that most servers are given at least a /64 from their respective hoster (e. g. M247 and Netrouting B. V.), it should be possible to configure each tunnel with its own global address and skip NAT66. This would make v6 a proper first class citizen, and make the setup way more similar to a non-VPN IPv6 setup, which also uses GUAs everywhere. I can think of a couple of challenges implementing this, but nothing impossible to solve: - Deanonymizing users is potentially easier if they have their own distinct addresses (correlating traffic). But I think this should be easily solvable with OpenVPN by assigning a new v6 on each reconnect. - Wireguard is a bit more difficult as the tunnel IP is baked into the config: Sharing configs across servers wouldn't be possible, and the address would be static. However, Eddie could just regularly rotate addresses and reconfigure them for the proper server.
  2. Hey, Ok so here is my problem: I have port 443/80 forwarded on my home router to a little server at home, after connecting to the VPN, I'm unable to reach it from outside. now here is my question: Is it possible to be connected to VPN and still be reachable from my private IP, and if so how? Thx <3
  3. This is my setup: I got 2 machines, a dedicated server machine and a normal laptop. The server is running Windows Server 2012 Datacenter The server has 6 NICs (Network Interface Connections). Ethernet 1 has a internet connection to my ISP router which i do not have login access to. Ethernet 5 (also functions as Mgnt) is connected to my laptop. The setup that i have is that any traffic from/to the laptop on Ethernet 5 goes through Ethernet 1. (a basic NAT setup.) The server translates the private ip from Ethernet 5 to the public ip on Ethernet 1. This works without problems. Heres the problem: When i connect to an airVPN Server, the laptop loses its internet access.. I want the laptop to be able to access internet. It doesnt matter if thats through AirVPN or directly with the real IP. That doesnt matter at all. The only thing that matters is an internet connection that the laptop can use.
×
×
  • Create New...