go558a83nk

You can't forward a port to a NAS when you're running AirVPN (Eddie) on a PC. You must run AirVPN on the NAS or run an openvpn client on a router/gateway.

By default that's what the Eddie app uses.

1) did you verify the interface is TUN0? 2) Also can you be more detailed with your port forward rule on this site? Did you specify the internal (local) port as 10001 but external is something different?

The OP of this thread is wanting to use the openvpn client on a router. That's not what you are doing. Port forwarding through the VPN tunnel to the Eddie app has nothing to do with what router you have. Everything goes through the encrypted VPN connection, the router cannot affect it at all. If you've seen a change in behavior with a new router it's just coincidence. If you had/have DNS leaks it sounds like you're not using network lock in Eddie.

Wow, three of the Dallas servers are gone from status page.

No, iptables are not created in the GUI on ddwrt or tomato.

For clarity I think what you mean is you were able to forward ports without problem using Eddie (AirVPN software) but now that you use your edgerouter as openvpn client you have problems. I did a quick web search and it looks like there's plenty of help on this topic. You can do it through the web GUI of your router by creating DNAT and firewall rules.

Doesn't seem much different really. Just different arrangement. I was hoping for the ability to just edit configs but I still can't do that that I can see.

Amazon Prime wasn't part of the announcement. This thread is about Netflix.

Sorry you're getting no help on this. I don't use the app so I'm unfamiliar with its details and behaviors. Otherwise I'd help.

Since these Dallas servers have been so glitchy I've setup my pfsense box with a gateway group. Dallas server tier 1, Atlanta server tier 2. Twice today it's failed over to Atlanta, then back to Dallas when it's working. So, I'm not stressing now. Nothing bothers me more than my wife saying she switched off wifi and went to cellular but didn't tell me she was having problems!

Yes. It's been about a month of terrible connectivity for all of the Dallas servers. Over 3 years with Airvpn, never an issue -- now this AVP is almost unusable. I bounced here after rolling from VPN provider to VPN provider -- and I thought I'd found home. In case some one asks: I've tried 2.16.3, 2.16.2 and older clients, this includes removing tap as well as AVP client. It's not you, it's the Dallas servers. Just use other servers for now if they aren't working. There are plenty of options and if you understand Air's explanation in the OP I hope you can see they were put in a bad position and had to rush to get some (temporary?) replacements. So, a little forgiveness is probably welcome at this point.

I've got no IP leak there.

You use TCP in Eddie on Windows too?

Use entry IP 3 or 4 in your config generator choices. P.S. tls-crypt was working prior to this update for openvpn connect on iOS.

It's only a few seconds for me anyway.

Have you tried tracing to the alternate entry IP addresses? In my experience routing can change drastically from entry IP 1 to 2 to 3 to 4. And, before you ask, that has nothing to do with AirVPN.

You've followed post 2 in this thread exactly? 1) Use tls-crypt.key 2) tls key usage mode needs to be authentication and encryption 3) auth digest algorithm needs to be sha512

This was already asked for in the last week and Clodo replied that they would add that to the API.

Yeah, I see that now. But, I know I've seen Staff comment on this topic in the past and I'm just repeating what they said to the best my memory serves me. Shrug. I'll look for the past discussion. https://airvpn.org/topic/26051-config-generator-using-deprecated-openvpn-commands/?hl=comp-lzo&do=findComment&comment=70698 That's one of the threads I was thinking of. Looks like I remembered wrong. comp-lzo no must be specified or else there might be connection failure on some devices.

You should be able to upload just the same as download if your ISP allows it. I'd use just one VPN tunnel, make sure port forwarding is working, and try that. I think the muti-wan thing confuses things in an application that requires port forwarding and uploading and keeping track of peers. I don't have a symmetric line like you but when my ISP is working properly I'm able to upload at 40mbit/s over VPN. I'm sure others can do much better.

comp-lzo is in configs because some devices don't seem to work with "comp-lzo no" in the config. But, AirVPN servers push a message that includes "comp-lzo no", which disables compression.

Of course they shouldn't be going down. However, don't be upset about the support request being closed. That's just normal. You can always reply on the same ticket if you think it'll help matters.

These Dallas servers continue to be useless. Just in the last hour I was connected to Corvus, then Monoceros, then Pictor - all of them going down forcing me to connect to a different server. Now using an Atlanta server.

Just to confirm, you have setup a port forward with 61408 assigned to you but you put in 32400 in the local port? And, in Plex remote access settings did you manually specify public port 61408 and click apply? To see this option you must click "show advanced" on the remote access page.