go558a83nk

seems to update automatically (via repo) on Mint 18.1 and run just fine.

Wow, you're right, once uTP is disabled, the connection icon stays yellow when the client is set to listen on unforwarded ports. I tested several times with different torrents, trackers, and ports, and as long as I kept uTP off, the connection status never went green. Once I turned uTP on the status icon would eventually go green, usually within a few seconds.
 
I don't know much about uTP or what it does. A quick search tells me it's kind of a QoS protocol for torrents. So what would that have to do with allowing connections through an unforwarded port (if that's even what it's doing)?
 
In any case, thank you for the help!

Dude that router can't handle the VPN encryption, which could be why there are no options for it. It's an old wireless G from like, 10+ years ago. I had DD-WRT running on a Netgear N900 and it still didn't have enough power so I had to get a mini-pc and put PFSENSE on it. 
 
There's no need to be all snippy about it...
 
That being said, I didn't know much of anything about networking until I started messing around with Air and router firmwares. Just keep at it and you'll get it. It took me 6 months to setup PFSENSE lol

Hello!

Today we're starting AirVPN seventh birthday celebrations!
 
From a two servers service located in one single tiny country providing a handful of Mbit/s, the baby has grown up to a wide infrastructure in 18 countries in three continents, providing now 197000 Mbit/s to tens of thousands people around the world.
 
2017 is an important year, not only because not all VPN services have flourished or even survived for seven years, but also because 2017 is the year we planned to enhance the growing child with full IPv6 support as well as tls-crypt obfuscation. Software related development will be powered up, with some very exciting news you will get in the next months.
 
If you're curious to know something about a series of fortunate events which gave birth to AirVPN, have a look here:
https://airvpn.org/aboutus

To worthily celebrate Air's seventh birthday, we're glad to inform you that starting from now we will offer a 25% discount on all plans. Hurry up, celebrations as well as this special offer will end on June the 6th, 23:59:59 UTC!

Kind regards and datalove
AirVPN Staff

I use merlin on my ac87u router, works great.  I'm not sure about using client 5, I always use client 1 as it uses the core not used by the system, so gives you more speed.  My max is only 5MB/s anyway, and I get that easily, core using maybe 50%.  As for port forwards, here is my firewall-start script in /jffs/scripts/ for torrent and plex for reference, adjust accordingly.  https://ptpb.pw/MoAG

What about Los Angeles servers?

I just recently started using AirVPN and absolutely love it. The privacy and security is practically unmatched and the obfuscation is great. Eddie is a great client with my only complaint being the time it takes to connect. I get my full 100 MB/s download speeds and couldn't be happier. I also really enjoy the extra features like port forwarding and all of the many devices supported.

I have just done some testing, here are the results. As pointed out by go558a83nk, an mssfix value of 1442 is perfect: problematic websites like aliexpress load perfectly fine, and P2P doesn't seem affected. Also, I don't get any warning from OpenVPN.
 
I also fixed my iptables settings, somehow it was limiting my P2P ports. I though the firewall was bypassed by the VPN, I guess I have much more to learn about this
 
Anyway, the issue is now solved, thank you very much for your help and patience!
 
Edit: I have just seen your reply. The ISP router is very far from my PC, but the mssfix 1442 did the trick anyway. It's amazing what a small number difference can do!

UDP packets are sent/received easier in a loaded network.
 
mssfix and MTU aren't the same thing.  Read up on it.  Adjusting MTU has to be done on both server and client to have an effect.  Adjusting mssfix on the client is the way to go to help with MTU problems.  Default mssfix for openvpn is 1450.  You might start with just 1442 and work your way lower to find what works best.

I would Recommend an PFSense Build on ideally AES-NI Hardware, but you can use older Hardware if Required.


I wouldn't recommend Purchasing any of there Products as a "Consumer" user, you will be forking out more than you actually need for Half Decent Hardware.
 
 
My Build:
 
Asrock ITX with an AMD A4-APU5000 (With AES NI Support)
4GB of RAM
40GB HDD
1U PSU
1U Case


My Total Spendage was about 200ish Quid with the 1U Case being costly.


Hope this helps (welcome to PM me if you require Support)

From their wordpress site
 
Seems legit

Fixed this after 2 days of restless nights.
 
I will post for the sake of some others if they ever had trouble with this.
 
Up until several days ago. I had working port forwards on my network. Originally I had port 61477 with local port 32400 (for plex) and 61466 with local port 443 (for owncloud).
 
I used merlinwrt RT-87N with setting IP tables as follows.
 

iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --match multiport --dports 61466,61477 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --match multiport --dports 61466,61477 -j ACCEPT   iptables -t nat -I PREROUTING -i tun12 -p tcp --match multiport --dports 61466,61477 -j DNAT --to-destination 192.168.2.140 iptables -t nat -I PREROUTING -i tun12 -p udp --match multiport --dports 61466,61477 -j DNAT --to-destination 192.168.2.140
 
Suddenly it breaks on me with no knowledge of what happens. So I tinkered with the router, IPtables, trials and errors, only to figure out that I need to forward it properly.
 
End result, this is what I did
 
AirVPN Port and Local port I made the same, 61466 and 61466, 61477 and 61477.
 
Changed the IPtables in for the router manually via ssh with this code
 

iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 9958 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 9958 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 9958 -j DNAT --to-destination 192.168.2.140 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 9958 -j DNAT --to-destination 192.168.2.140   iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 61477 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 61477 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 61477 -j DNAT --to-destination 192.168.2.140:32400 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 61477 -j DNAT --to-destination 192.168.2.140:32400   iptables -I FORWARD -i tun12 -p udp -d 192.168.2.140 --dport 61466 -j ACCEPT iptables -I FORWARD -i tun12 -p tcp -d 192.168.2.140 --dport 61466 -j ACCEPT iptables -t nat -I PREROUTING -i tun12 -p tcp --dport 61466 -j DNAT --to-destination 192.168.2.140:443 iptables -t nat -I PREROUTING -i tun12 -p udp --dport 61466 -j DNAT --to-destination 192.168.2.140:443
 
On the prerouting IPtables I added port number which is to point to local port, so it becomes like this.
 

 
Anyway, I don't know if this is correct, but this works for me. All ports opened and I can access plex and nextcloud mainly from work.
 
Hopefully this will help some others who own Asus router and port forwarding AirVPN.
 
Regards
 

are you using squid?

What device is running the openvpn client?
 
If you're using the Eddie (AirVPN) software on a PC then you're correct in your assessment that you do not need to forward ports in any way on your router if you're wanting to access services through the VPN tunnel.  And to access those services you'd go via the exit IP of the VPN server to which you're connected. But, if you're connecting with Eddie yet still want to access services on your router NOT via the VPN tunnel then you'll need to figure that out on your own.  As that has nothing to do with AirVPN that would be off topic for this forum. If your router is running the openvpn client then you will need to forward ports on the router using iptables as you have read.  Whether or not you can access services on the router through the VPN tunnel it's creating is unknown to me.  I've read of another user having trouble doing so.  But, forwarding ports to other devices on your LAN is common practice.  It's accessing the router itself that may be a problem.

Its all good and everything to, as PIA says, "fight for and defend" privacy and the sort. However, when money is involved and you have paying customers and are a business there is the business to take care of also. Running around trying to look important by throwing money at and supporting every privacy crusade that comes along, then changing things suddenly on a whim and not paying attention and lying to, and mistreating and not taking care of, and not suitably communicating with, customers is simply a bad and very poorly run business no matter how much PIA claims to be such defenders of "privacy" and supporters of this or that.
 
A few old sayings come to mind in context with PIA - Caveat emptor, "...a fool and his money are soon parted", and "...all that glitters is not gold"

yep, but that's not the real issue. What people over there are mostly upset about at this point is:
 
 
1. There was no warning of this major change, then PIA lied about it and has of yet still failed to tell people what is happening.
 
 
2. PIA claimed one of the companies being used to do this change was a wholly owned subsidiary of PIA but that company was really surprised to hear this and has no knowledge of now suddenly being owned by PIA
 
 
3. PIA customer and service support is basically non-existent at this point.
 
 
4. PIA is using a fake company which claims to be incorporated to which the new IP address are registered. But, there is no such incorporated company. Then PIA claimed this company was a wholly owned subsidiary of PIA and that's not true either and that fake company is owned by someone else. PIA also claimed one of the other companies involved was a wholly owned subsidiary of PIA, that turned out not to be true either.
 
5. Long time outstanding issues have been ignored, such as technical and security vulnerabilities PIA knows about but has blatantly said they refuse to fix them but still admits their product causes the issue.
 
 
6. Support issues reported many times to PIA through their customer support. Customer support replies and says their engineers or developers said they could find no issue. It turns out that the engineers and developers were never told of the issues and customer support just wanted the people reporting them to go away so they lied.
 
 
There are many other things as well.
 
That's why this is suddenly exploding like it is, and started doing so when this change came about without warning before it happened. It was just another in a long line of things that PIA has failed on, it just finally boiled over and people are pissed.
 

I didn't know it until earlier this morning the guy blasting PIA in that thread posted in link in the post above works for our company. I heard some of our guys talking about a test they did this past weekend involving the PIA VPN while they were at an ISP conducting some compliance testing of the ISP network, that's when I found out who the guy is. Looked at the info from the test, the issue with PIA is not good at all and more extensive than he lets on in that outlined in scant detail here > Test
 
Soooo.. glad my subscription ends with them in about a week. Their customer and tech support has really dropped into the pits.

Yes I know its about PIA, but this is the off topic forum anyway and i've been following a few PIA users over at PIA who are absolutely fed up with the way PIA treats customers. I though this thread was pretty good, although confusing at times, but this one post in the thread just really stuck out for me as i am also still a PIA customer (I use AirVPN too) with my PIA subscription to expire next week and can vouch for the validity of the information in this post > 
WARNING - PIA DATA CENTERS ODD IP CHANGES  so I thought someone else might enjoy it too if they were past or present PIA customers and encountered the PIA BS. He is really raking PIA over the coals as are others in that thread.

Hello!

We're very glad to inform you that a new 1 Gbit/s server located in Singapore is available: Triangulum.
 
The AirVPN client will show automatically the new server, If you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The servers accept connections on ports 53, 80, 443, 1194, 2018 UDP and TCP.

Just like every other Air server, Triangulum supports OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.

Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

works for me and I think most people.  else there would be a lot more complaints about it.

Hello!

We're very glad to inform you that a new 1 Gbit/s server located in the United States is available: Aquila. It is located in Fremont, California.
 
The AirVPN client will show automatically the new server, If you use the OpenVPN client you can generate all the files to access them through our configuration/certificates/key generator (menu "Client Area"->"Config generator").

The servers accept connections on ports 53, 80, 443, 1194, 2018 UDP and TCP.

Just like every other Air server, Aquila supports OpenVPN over SSL and OpenVPN over SSH.

As usual no traffic limits, no logs, no discrimination on protocols and hardened security against various attacks with separate entry and exit-IP addresses.

Do not hesitate to contact us for any information or issue.

Kind regards and datalove
AirVPN Team

If anyone is interested, here is what is in that "telemetry" and what is being "collected". MS released this recently in response to concerns about this "telemetry" thing.
 
 
Windows 10, version 1703 basic level Windows diagnostic events and fields
 
 
The original article pointing to this appeared at Ars Technica recently > Microsoft opens up on Windows telemetry, tells us most of what data it collects
 
"Microsoft has published the full range of data that Windows 10 version 1703, the Creators Update, will collect in its default "basic" telemetry setting. The company has also provided details on the kinds of information that can be captured in the optional "full" telemetry setting."
 

Well, I already found my solution in another Form discussion:  
I clicked on this AIRVPN link:   https://airvpn.org/topic/18555-is-a-website-blocked-then-check-this-guide-first-feedback-appreciated/?p=44507
and entered "www.youtube.com" in the search field.  Waited a few seconds and then refreshed.  It showed me which servers were currently unable to access YouTube so I simply switched to another AIRVPN server that had YouTube access.  Problem solved.

Or, you could pay for a year without waiting for a sale and support them in a way they deserve to be supported. Their service is superior than many other VPN services out there, and costs less. Many fail to realize this, until they to comparisons on multiple services, like I have. AirVPN is simply the best in all aspects, in my book. Support them, and give them what they deserve. 

Likes:
It's the only VPN that worked out of the box with my Plex server, other VPNs required a workaround to make Plex accessible remotely.
 
Dislikes:
waiting for an AirVPN silly sale day so I can sign up for a year.