go558a83nk

Definitely odd. As you can see by the status page AirVPN doesn't disconnect people. Some have been connected for weeks.

So, you've followed the guide but do not understand what things like "192.168.1.0/24" mean? Because I know such IP ranges are in the guide. Why would you follow a guide and not understand what you're being asked to do? Look up CIDR notation.

https://airvpn.org/topic/17444-how-to-set-up-pfsense-23-for-airvpn/?p=61027

It's probably a nightly release of your ISP connection. Perhaps it boils down to how the different firmwares handle DHCP release.

Weird. Why did this pop up as unread suddenly?

What different ports and protocols have you tried?

Some time ago Air did list Netflix as one of the services they could make work via their micro-routing, etc. But, when Netflix started to block VPNs a year or so ago Air removed Netflix from the "supported" list. I was thinking there may be some old "advertisement" that tittiger saw but isn't valid anymore.

what ad copy?

those are settings you'd write in the custom options of the openvpn client

Are pfsense and eddie using the exact same port and protocol? Have you tried messing with mssfix settings, receive and send buffer in pfsense?

so, actually, an AES-NI CPU is used by openvpn/openssl automatically. In fact, many people find better performance completely disabling hardware crypto support in the advanced settings of pfsense. Sounds crazy, but I tested it on my AMD CPU and performance is increased. again, try selecting "none" in system>advanced>miscellaneous>cryptographic hardware. Also select "none" for hardware crypto in the openvpn client setup. Then reboot. However, your speeds are so diminished as compared to Eddie that I suspect something else needs to be fixed first.

Is this the action you're looking for?

LOL. I'm sure you're joking. Audrey was obviously removed as a user for spam, with posts deleted. And I'm glad for it.

Wrong thread for this question. Also, you can search the web for what's possible with that router just the same as anybody else.

I assume you're using Merlin firmware if you have policy routing. First thing is to try just rebooting if your sure your policy rules are good. If that doesn't work try turning off hardware acceleration (CTF + FA). That did the trick for me when I used Asus in the past.

Old thread but since I use comcast I might as well say that TCP and even SSL have always been slow for me with comcast from this location. UDP is the way to go for me.

There is no automatic way to get low latency when using configs. Just load configs for servers that you know are low latency to where you are or will be.

TCP 443 is not the same as SSL 443. And openvpn always uses openssl, except when it doesn't (e.g. polarssl).

If you're not using a specific server it'll connect you to the least busy server of the region you've chosen.

How to do this has been discussed in other threads quite recently. Namely, the actual pfsense guide thread.

The north american configuration file will connect you to the least busy server in north america at the time you connect. It can't take anything else into account because it doesn't know your location or your latency to VPN servers.

change the scoring rule to latency

Failed at editing routes. Have you tried simply rebooting?

even with network lock on there is still an option to keep the local network available. look in the settings.

You must like that datacenter as you kept adding servers. I saw two new ones, then two more. Scorpius was added just since yesterday morning (my time).