go558a83nk

Thanks but it doesn't work as soon as i turn on the VPN PlanePlotter stops uploading and downloading Is there a way to test if the port forwarding is actually working? My guess is that planeplotter need to announce to peers what the external (public) port is since it's different from the usual due to having to share the VPN with other users. Peers try to connect to the default and that's not what's setup. Do you have such a setting in the server? Apps that rely on port forwarding for remote access (e.g. Plex) have an option to use an alternate external (public) port.

Online Sessions: 15973 - BW: 71229 Mbit/s

Of course. But, you can setup a port forwarding rule with AirVPN and have remote access to Plex through the VPN.

https://airvpn.org/topic/28153-ipv6-support-and-new-smart-features/

Commendable work but what happens when your ISP loses the route to the server that was working so well?

1 is the default 2 is the same server setup as 1 but a different entry IP in case the default IP is blocked by your ISP 3 is tls-crypt 4 is the same server setup as 3 but a different entry IP in case the 3 IP is blocked by your ISP

Did you do anything "special" with your router to get that speed? I've seen others with that router struggle to get high speed even though it has the AES-NI CPU.

yep, those pfsense forums block a lot. it makes no sense for a firewall software to have as a huge part of their software openvpn server and client and yet block those of us using such a thing.

Think of it like this. You've got a huge map of Bitcoin addresses on a whiteboard. You know who sent some transaction, but not all. If you can get any clues as to who's who, it helps you to deduce the rest by process of elimination. Using vanity addresses (1myNaMEisBoBhfsfdfdhjfhdfdjfh) is a clue, and hurts everyone's privacy a little. For instance, anyone looking at the 1Air... addresses can assume these are all AirVPN addresses. That means any change that gets sent back to AirVPN customers is identified (although before, the Bitcoin payments service AirVPN required the customer email from AirVPN, so this is better) One thing: if anyone else uses 1Air... addresses, by random chance or deliberately as AirVPN do, then that will screw with doing analysis like this. But it's better if there's no extras info to use at all, I really hope this is changed OK, I'm looking at it from the perspective of having purchased my bitcoin anonymously using cash and hold it in an electrum wallet...and the receiving address is different from the sending addresses I use. So, even that it's seen that Air receives from "me" they don't know who "me" is. Then to link that transaction with my account on Air is a whole other big leap.

It's connected There's no problem here. That's just pfsense disconnecting from monitoring itself. I get hundreds of those notices. The "initialization sequence completed" is what matters. If you can't get any traffic through the VPN tunnel then your NAT and/or firewall rules are incorrect.

Have you tried just changing servers to see if that fixes it? I was having problems and changed server and it worked. Then I switched back to the location I liked, and it worked.

Yeah, I think all that "management" stuff is normal. It's just the router making a note that it checked on itself basically.

hash is not sha256. it's sha1 unless you're using tls-crypt configs, where it's sha512.

Those two default rules need to be deleted and it looks like you have a duplicate rule for "airvpn_lan allow outbound".

You need to follow the guide. Firewall rules are required. This note is under the "i" at the bottom of the firewall rules pages - "Everything that isn't explicitly passed is blocked by default." Therefore, if you don't create rules to pass traffic out the AirVPN gateway (or wherever you want it) it'll be blocked!

the AC86U has an AES-NI CPU so it should be the best that I know of.

Looks like you did something wrong around the TLS key. Also, is your local network really 192.168.0.0? What is your DHCP server subnet?

That CPU has AES-NI and can go up to 2.8ghz. I don't think it's your CPU keeping your speed down.

RARBG wouldn't.. In fact they're one of the ones like Pirate Bay and Demonoid that have warnings all over the place about how you SHOULD be using a VPN. Some providers however, have been flagged. I get a message when I go to RARBG that my IP range has caused suspicious activity in the past, but the site still works fine (I get one at ETTV as well). I cant recall running into trouble with any of the Nor Cal servers, but I spend most of my time on the LA ones and they're all fine with RARBG. Been using the new Arizona ones the last few weeks, and believe it or not, they're faster and seem to be running even better than the ones here at home in LA.. Shorter ping times too. RARBG trackers *do* block many of Air servers. I use them too and usually have to rely on DHT only as the RARBG trackers don't respond. On a few servers I've tried their trackers respond normally. Again, it's not AirVPN doing the blocking, so it must be RARBG. I understand it seems ironic for them to suggest you use a VPN but then block some VPN IP but it's the truth.

Sounds like sometimes your torrent client doesn't bootstrap DHT - maybe those DHT bootstrap servers are overloaded or blocking some VPN servers? The one remedy I know of is to just keep everything connected. If your torrent client continues to have an internet connection (through the VPN) it'll gather up many DHT nodes and won't lose them. Hopping around or disconnecting causes your torrent client to lose DHT nodes and then it has to bootstrap again.

I can't say much about most of your problems but I will say that trackers block VPN IPs. Air is not blocking your access to trackers.

Hash algorithm is SHA1 (not SHA) for tls-auth configs.

OK, either way (router, or eddie) you must create a port forward rule in the client area on this web site. The servers must know to forward a port to you. If you use your raspi as openvpn client then you must create some iptables rules I imagine, much like other routers. Though I'm not sure as I've never used one. Anyway, the iptables rules basically tell the OS to forward traffic from the openvpn interface to whatever LAN device. Your ISP router can remain untouched, as the VPN tunnel (between raspi and VPN server) contains all traffic and can't be manipulated by the ISP router anyway. If using eddie it's easier. Once a rule is created in client area on this web site it should just work for any server listening on the same device that's running eddie. Again, do not touch the ISP router. Oh, and make sure your server is listening on the port that is setup in the rule you create in client area.

Give some more details on what ports you've opened, including if you specified a local port, and what port your game is listening on. My guess is that you haven't told the game to listen on the port that AirVPN has opened for you. Furthermore, unless your game can tell your buddies what internet facing port (that of the VPN server) to connect to, it still won't work.

I'm confused about how your setup. Are you using your RasPi as openvpn client, or Eddie?