go558a83nk

OK, I'm sure others have already done this but I figured out how to use Plex's system with pool 2 and that is by putting the "https://pool 2 external IP:external port" into the custom server access url option in the network settings for the plex server.

Please advise how we should handle using pool 2 for Plex? Plex will always report to its system that the server isn't remotely accessible because it's testing to the pool 1 entry IP. But using yougetsignal to the pool 2 entry IP or the internal port tester ports are open, all is good. How can we get Plex to propagate in its system the proper entry IP when using pool 2?

that was actually me that said to change the local port ;)

Local port needs to be 32400 in this case. should work then.

Are there humans anywhere else?

How do you make your download speed visible at the top user speed on that section? I couldn't find and answer to that anywhere. Reaching speeds well above anyone there, but still not on that list for some reason. That's an average speed over several minutes. So doing a speed test with ookla, for example, won't be reflected there.

I know that I can use 1500 MTU on my ISP, so 1400 Wireguard MTU will work the best for my connection If 1500 byte is possible with your ISP then 1420 for wireguard should work fine. In pfsense I use 1420 for MTU and MSS, and with that TCP connections though the tunnel are capped at 1380 bytes.

The highest MTU that doesn't have problems should be the fastest. Going to 1320 or even 1280 is basically a way to make sure wireguard works for everybody. But many people will have no problem using one even as high as 1420.

From logs posted above Eddie attempts to connect to 217.138.195.21 but gets no response. This does seem to be a correct AirVPN IP address so DNS doesn't seem poisoned. Rather it does look like ISPs are preventing connection to that IP address. I do wonder if TCP, rather than UDP, would work.

AirVPN doesn't use username and password. They use a certificate and key.

actually that log is them trying UDP entry 3 and then TCP and SSH and SSL. none of them worked. so, yes, chances are some software is blocking the connection.

Eddie is getting no response from the servers. Do you live in a nation that blocks VPNs? I think you'll need to try TCP. Go into settings > protocols. Uncheck automatic. Choose openvpn TCP any port and entry IP 3 or 4. If that doesn't work, you'll have to try SSL or SSH.

I've yet to have an ISP that supports IPv6 besides mobile data.

Can we still expect a new server soon? The 25th came and went.

Wireguard in Eddie? Or wireguard the app? Wireguard in Eddie

make sure to try wireguard if you haven't already

it wasn't me but that's really nice of somebody!

The phoenix location is definitely spoofed. You can check the m247 site to see their list (or a map) of their actual locations. The Phoenix location as it is adds bandwidth but not route diversity since it's likely found by the same route as the LA location. Something better may be out there but maybe not. https://m247.com/eu/data-center-locations/

I don't blame you for wanting to use wireguard especially on a router but openvpn using tls-crypt does connect easily from Egypt.

have you confirmed it also announces the specified IP address to DHT peers or only tracker based peers?

Thank you, this answers the question that had been rolling around in my head. I do think it would be good to allow users to pick the exit IP for each connection VPN connection.

I currently have need to be able to connect to the same server and get the same exit IP address for both connections. I'm not using port forwarding. With this new system is it possible that one of the two connections will get a different exit IP?

So is it working? The other thing that often breaks port forwarding on pfsense is if there are any rules in the openvpn or wireguard "group" firewall rules since those group rules override individual interface rules.

I'm confused because you said "it is down a lot of time". But not enough for you to break the contract legally?

You only need the first port forward rule, for your AirVPN interface, assuming that's the interface/gateway that the transmission device is allowed to use in policy routing. So, delete the one you made for your WAN. The only mistake I see is setting filter rule association to pass. You need to set that to "create new associated filter rule" and save. That'll create the necessary firewall rule. Of course, make sure transmission is listening at 192.168.3.102:19151 when you test to see if the port is open.