Jump to content
Not connected, Your IP: 216.73.216.7

Search the Community

Showing results for tags 'airvpn-suite'.



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
    • Blocked websites warning
    • Eddie - AirVPN Client
    • DNS Lists
    • 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 2 results

  1. I'm setting up AirVPN's OpenVPN3 Suite on my home headless Arch server over SSH. I've never had a problem with it in prior years (when the server was Debian, which makes a lot of sense considering it probably had some installed program that blocked AirVPN network locking functionality), but recently it's been kicking my ssh session when every activation due to network lock setting up on a different subnet than my LAN (10.x.x.x vs 192.168.x.x). I was further surprised to find that there does not seem to be any native functionality built into goldcrest or bluetit to allow for exceptions to the network lock iptables rules (i.e. allowing a certain IP or subnet in through the filter); all I can seem to find is the ability to toggle the lock between iptables and nftables. My question, then, is just that: is there any way for me to allow certain addresses through my network lock, while keeping it activate for 99% of external traffic? Or, more preferably, allowing my entire 192.168.x.x subnet?
  2. I have three devices, all linux, running airvpn suite (specifically bluetit on boot through systemd). All three devices are connected simulatenously and, therefore, use separate keys. All are configured to connect on boot to country ISO: US. Infrequently, but often enough, these three devices will happen to connect to the same server (whether that be 2/3 or 3/3). This creates a mess out of my port forwards. Is there a simple solution to this issue? I was thinking of setting up the server whitelist so that no device could possibly connect to another devices server, but this solution seems tedious. Is this my only option? Any suggestions are appreciated, thanks!
×
×
  • Create New...