go558a83nk

Yes, even the i3 should be plenty. Just be sure to enable cryptographic hardware here /system_advanced_misc.php and then select that hardware in your openvpn config you create. Then AES-NI plus whatever else is on the CPU is in use.

You don't need that much ram or storage for pfsense. You need a good CPU and good network card(s). The celeron j1900 is out due to lacking AES-NI which is very important for running openvpn. Both have intel network cards so you're good there.

That's just the limitation of the CPU. It takes a lot of power to encrypt/decrypt openvpn quickly. Or AES-NI.

Yes though I don't know if you need to install entware for just SSH tunnel. I've done it in the past with an old asus router with merlin and entware. SSL tunnel too.

The bottom line is Air isn't blocking your access to those trackers. So it must be them blocking Air. Why is another question and it really makes one ponder. Could be related to them favoring VPNs that they're working with. But that doesn't explain public trackers.... Maybe all public trackers are just honeypots that want to see your real IP address?

Air has port forwarding which is what you probably need. (I do know some security systems don't require port fowarding for you to be able to monitor them remotely) However, you'll need to run VPN on a router so that the devices (blue iris) behind the router go through the VPN. That means buying another router to sit behind your ISP router. Further steps can be discussed after you decide what to do.

It's just not resolving your remote address in the openvpn config because your DNS server is a private address in AirVPN's network. Since you're not connected yet, you can't access that private address to resolve the remote host. There are 2 solutions. 1) Resolve the remote host separately, then put in the IP address of the remote server, not the domain. This keeps you to the one server. It won't be some random European server, which is what you may intend. 2) Use a public DNS in your general dd-wrt settings, then make sure that the openvpn client switches the router to VPN DNS upon connection. If your version of dd-wrt can't do that, then I suggest you find a firmware that does.

It's stated in the specifications that outbound port 25 is blocked to prevent spam.

No idea. But I am curious, can this thing really do OpenVPN at 300Mbps with that CPU? Where are you getting 300mbps from? Are you reading the wifi standard speed and confusing that with openvpn speed?

Merlin firmware using the policy routing option gives you the additional option to block VPN routed clients if the tunnel goes down. Is that the "killswitch" you're talking about?

In the past squid proxy and openvpn usage didn't play well together. What was meant to go through openvpn tunnel was in the clear. I don't know if that's still the case.

There are different ways to setup pfsense so this is not an easy thing to help with. And, this isn't an AirVPN topic but a pfsense topic. So, it should be moved to an off topic section. If it were my setup I'd create NAT outgoing and LAN firewall rules that allow a device out the WAN instead of the VPN. But, I don't know how you've set yours up.

If you can use tls-crypt over UDP that will likely give you better speed than TCP. What port you use is up to you. You'll need to use the tls-crypt key from a config for entry IP 3 or 4, be sure to use the correct entry IP address too, change the key usage mode to TLS encryption and authentication, and change the auth digest algorithm to SHA512.

DNS records don't exist yet from what I'm seeing.

I was having some issues with my OpenVPN clients from a pfSense box. Setting the send/receive buffers to 512 more than doubled my speeds from ~10-15Mbps to 30-35Mbps on a 50Mbps internet connection. I have the SG-3100, so there's no aes-ni because it's an ARM a9 processor. Curious if you have any other suggestions? Since its a netgate (pfsense) it has built in aes-ni into the arm chip. At 349 USD for the base it better support crypto since 2.5 will require it https://www.netgate.com/solutions/pfsense/sg-3100.html This says nothing about AES-NI. Unfortunately, I think a lot of people will either be buying new hardware or won't be updating to 2.5.