go558a83nk

Good job! The speed is there to be had and pfsense is great!

is your server running and listening on the ports you've forwarded?

Doesn't work with AirVPN. You need to use public DNS servers for now as a workaround 10.4.0.1 doesn't work consistently as a monitor IP with pfsense 2.4.x but does absolutely work as a DNS. For monitor IP I've been using the alternate entry IP of the server to which I'm connected at the time.

Which cipher is AES-256-CTR ? Your settings have AES-256-CBC. Not sure if that's the problem or just a typo in the logs. You could set it to AES-256-GCM aes-256-ctr is the control channel encryption that's part of the new tls-crypt option.

you must be new to VPN. errors within the several geolocation databases companies like speedtest use are so common. and it takes time for a change to propagate. the server really is in Chicago no matter where speedtest says it is.

Yep, I used this method. https://airvpn.org/topic/18322-how-to-quicly-test-theoretical-openvpn-throughput/?hl=%2Bopenvpn+%2Bspeed+%2Btheoretical Just change the cipher from aes-256-cbc to whatever you want to test. For me aes-256-gcm was the fastest of the 256 bit ciphers and seed-cbc. And aes-128-gcm was no faster. So, I just stick with 256.

Did I miss an announcement? The specs page https://airvpn.org/specs/ shows a lot more data ciphers available with openvpn > 2.4. Some 128 bit ciphers. That should help some weak CPU get a little better speed. Does anybody know which of the 256bit ciphers is likely to be fastest with an AES-NI CPU? Or, any way to tell which of the ciphers my CPU accelerates?

Looks like you network provider blocks UDP. You'll have to use TCP.

no, those errors wouldn't result in packet loss. those "errors" are the result of settings of the openvpn client that help us use it with pfsense as we want to. What IP address are you using for gateway monitoring that's showing packet loss through the VPN tunnel?

Is the setting pushed from the server?. Why would you want to disable this?

Does any traffic flow to/from utorrent even if port forwarding isn't working? Or is it completely not working? You didn't happen to mess with proxy settings or something? It's probably time to switch to qbittorrent anyway, considering the fact that utorrent is in big trouble for a security vulnerability. Qbittorrent can be bound to the TAP adapter which is another level of security as you don't have to worry about it trying to make connections outside the VPN tunnel.

Yes, The VPN tunnel should enable you forward ports so that you can accept incoming connections.

it's really simple 1) turn of UPnP and NAT-PMP in your torrent client 1) forward a port on this web site 2) enter that port that's assigned to you where applicable in your torrent client If that doesn't work when it did before then may I ask if you've installed or update some software, such as firewall, or other "security" software? Are you binding your torrent client to the TAP adapter? Are you using the network lock in Eddie?

Some people run an openvpn client on their router, etc. In that case, ports do need to be opened on the router. But, not using the usual port forward which goes from WAN to LAN but with iptables so you can specify TUN to LAN. When running Eddie on a PC the encrypted tunnel goes from your PC to the VPN server. Your router only sees the 1 connection your PC and the VPN server communicate on. Everything happens inside that 1 encrypted connection. Thus it's called "tunnel". So, please understand that your router isn't even capable of selectively allowing connections to be established from "outside" through that VPN tunnel because it doesn't even see all the connections happening inside that tunnel. Anyway, port forwarding is working for thousands of people as I write this. If it were not so we'd see a LOT more posts about it.

All proper guides on this site say you DO NOT forward ports on your router if you are using AirVPN Eddie on your PC.

My only concern with that is they didn't seem to answer question 11 thoroughly, especially the DNS question. I don't really care, but wonder what other people might think of that.

Maybe a silly question but have you looked in the ticket to see if Staff replied? My experience is that with every reply the ticket is marked as resolved, even if it's not resolved. But, just keep the communication flowing.

your screenshot above looks correct. port forwarding has always worked for me.

what ports and protocols have you tried?

That's not blocked. That's just the web page saying it's having a problem. Text: Your IP or your IP range are temporarly suspended. Url: https://airvpn.org/blocked/ I'd say that's blocked to me - these IPs are unable to access the website. maybe you're right. they use that same graphic for when their site is having problems. but, your screenshot does have different verbiage.

That's not blocked. That's just the web page saying it's having a problem.

other people are reporting the same thing in the ipleak section of this forum. so, it's probably just a problem with the website. Edit by LZ1: https://airvpn.org/topic/25117-ip-leak-test/?p=69802

I'm sure there's a way but I wouldn't know how to do it. Glad you have it working!

ca.crt is always the same. it sounds to me like you're not configuring the GUI correctly.

well if you're using pfsense 2.4.2 things might be different from those instructions. for example, now stunnel can be installed via the package manager in pfsense. if you've installed the freebsd 10 version of stunnel that might cause problems in pfsense 2.4.2 which is based on freebsd 11. just a guess.