go558a83nk

yep, in settings change protocol to TCP 443 and it should work just fine.

hotspot shield VPN probably uses L2TP, not openvpn. Thus no need for it to install the TAP driver, which is necessary for openvpn. anyway, the airvpn client will certainly have logs which will help us figure out the problem.

Woah, dude. This is your own opinion, I see that, but Posteo encrypts your CardDAV/CalDAV information with your AES-encrypted password and your whole mail account with your own PGP key and all this is just "mid-level" for you? Just because you can't use a few characters in your password? no kidding. just make the password longer if concerned about the lack of some characters possible. with 2 factor authentication I just don't see the problem.

I didn't know Air had servers in a global layer datacenter.

The reason it keeps happening even after updating Eddie is because it's not Eddie that's the problem. Read this thread again, especially the posts from Staff.

nice! what is your setup? Gigabit line and a Macbook Pro (Late 2013). Using Eddie? What changes from the default setup, if any?

nice! what is your setup?

The 3 Dallas servers in the same IP pool are down for maintenance. Could I hope that their IP address is being changed? So far those servers have been "blocked" more than usual in my experience with them.

network lock only affects the device on which Eddie (AirVPN client) is running, preventing that device from making connections to the internet outside the VPN tunnel. By default it should allow local network traffic. Either way, it doesn't affect other devices. if you're having other problems it's coincidental and caused by something else.

what does AirVPN have to do with your xbox?

The point staff made to the OP was that the version of openssl the OP claimed Eddie was using were never used by Eddie, at least in the changelog to which staff pasted the link. I'm assuming the OP meant 1.0.2c, not 1.0.3c. So, the only way the OP could be using openssl 1.0.2c was if he/she installed it separately from Eddie.

today there was/is a large DNS problem that affected a large portion of the United States and some of Europe because of a DDOS attack on the Dyn company. Perhaps that is the problem you're experiencing?

I'm not sure about what dd-wrt needs (I've worked with Merlin Asus) for security in combination with port forwarding. However, this pattern is all I ever needed iptables -I FORWARD -i tun0 -p udp -d 192.168.1.5 --dport 20176 -j ACCEPT iptables -I FORWARD -i tun0 -p tcp -d 192.168.1.5 --dport 20176 -j ACCEPT iptables -t nat -I PREROUTING -i tun0 -p tcp --dport 20176 -j DNAT --to-destination 192.168.1.5 iptables -t nat -I PREROUTING -i tun0 -p udp --dport 20176 -j DNAT --to-destination 192.168.1.5 Now, I'm confused about your setup. Did you create a forwarded port with AirVPN with a different internal port than external port? If so, you'll use that internal port in your iptable rules

your router will show your WAN IP, as you've read. That's the IP address that your ISP assigns you. web sites will report the IP address of the AirVPN server. check ipleak.net (an AirVPN site) to make sure everything is working properly.

I'm using the AirVPN client, so I removed the forwarding on my router. Still no change. From my PC I can connect to the server using 10.4.72.46:8096, or 192.168.X.X:8096 removing the port forwards on your router wasn't expected to fix the problem. it's a security fix. if the internal port you've assigned on your forwarded ports match what emby is looking for you should get a green light. have you tried restarting emby?

are you running the openvpn client on your router? if not, no need to forward ports on the router.

unless a server is under super high load nothing about the server itself will change your "ping". ping is a measure of the latency between you and the server. I'm sure you realize there's a lot of internet between you and the server that can change. best practice is to get an idea of the usual route between you and the server and see if that changes from time to time.

this question is asked often. yes, you can. but, you will see a significant performance degradation. or you could just configure pfsense to route different LAN devices to different VPN gateways.

killswitch? I guess that's the network lock but if you're getting DNS leaks it sounds like you're not using it. your picture doesn't seem to have uploaded properly or something.

not what I'm talking about. I figured you were adding some extra options in the openvpn config. I guess not.

what are your config options? I'm thinking some of your options are helping you here.

the line 20161016 22:41:37 TLS: Initial packet from [AF_INET]109.232.227.137:443 sid=54298f20 09cbdd38 is only the beginning of a connection negotiation. The management lines are basically the router showing that it's checking on itself/on the openvpn client. The log you pasted is only showing 3 seconds of time from the initial packet line to where you stopped it. What happens after that? You'll need to show the full log of an actual completed connection (it'll say "initialization sequence completed") and logs of what happens at disconnects.

IPs you want outside the VPN make an outbound NAT rule that allows those IPs out the WAN interface. The rule must be above the rule that forces all else through the VPN. Make corresponding LAN firewall rules that allow those IPs out the WAN gateway (advanced options > gateway in the rule settings), again placed above the rule that routes the rest through the VPN.

you must be mistaken. Air has used a different exit IP from the entry IP for years (I think) now.

Everybody surveils. But people only complain about the USA. I guess they expect such from Russia and China? By the way, if you believe some people, Ukraine is likely under heavy USA surveillance as a sort of cold war with Russia.