This works with all firewalls that support these steps and its very easy to set up. So we made sure that all traffic is going through our VPN tunnel. But we can reconnect with Viscosity to our AirVPN servers. As soon as Viscosity has lost the connection, we are no longer be able to connect to the internet because our local network has been blocked. So we just need to apply this rule set to our local network adapter only.

As previously told Viscosity creates network adapters.

3d) At the end we block ALL other traffic 4. We allow in/out connections to 95.211.138.143 and to 212.117.180.25 3c) Next we allow connections to the AIRVPN server(s) in this case I'm allowing connections to the AirVPN Switzerland server //Edit: This doesn't seem to be necessary at all. 3a) We need to allow in/out connections to our homework by allowing connections from 192.168.0.0 to 192.168.255.255 3b) We need to allow in/out connections to AirVPN in general, because GData has no kind of collection we must create for every IP a rule. I recommend using the assistant of GData. We need to allow the Openvpn.exe inside of the Viscosity folder. We need a to create only a few custom rules in our rule set 3. Create a new rule set called AirVPN or whatever else. In short: We simply block ALL traffic on our others network adapters and just allow Viscosity (and the network adapters of viscosity). Why only for Viscosity? Because Viscosity makes it very easy for us by creating network adapters and I had trouble applying the Comodo guide to GData Firewall. This works ONLY for Viscosity users and ONLY if you have ANY firewall (in my case I'm using GData Internet Security 2015). This tutorial is about blocking ALL traffic outside of the VPN connection which reveal your real IP address and also work as DNS Leak Fix. The log - which is identical with every disconnect - looks like this (disconnect on Zaurak): Mar 30 18:43:29: Inactivity timeout (-ping-restart), restartingMar 30 18:43:29: SIGUSR1 received, process restartingMar 30 18:43:29: UDPv4 link local: Mar 30 18:43:29: UDPv4 link remote: 82.118.16.175:443Mar 30 18:43:36: Peer Connection Initiated with 82.118.16.175:443Mar 30 18:43:38: Preserving previous TUN/TAP instance: tun0Mar 30 18:43:38: Initialization Sequence Completed Any help would be appreciated!

My VPN Client is Viscosity running on OS X 10.9.5. Also using UDP or TCP does not seem to make a difference. I've had these issues now in Ukraine, Romania, Sweden, Netherlands. At first I thought it would occur only on some servers (specific locations), but this does not seem to be the case. Hi, I keep getting pretty regular server timeouts and disconnects, sometimes multiple times per day, sometimes the connection seems stable for days. While I know that I can mute log outputs, I'd like to know why these warnings are thrown. As a result, the CPU usage on my Macbook is going crazy (process for Viscosity uses >100% CPU) and the fan is becoming noisy. Hi, while using P2P traffic, my VPN-client (I am using Viscosity on OS X) is hammered with (literally!) hundreds of thousands of log entries like this: May 16 13:54:33: Authenticate/Decrypt packet error: bad packet ID (may be a replay): - see the man page entry for -no-replay and -replay-window for more info or silence this warning with -mute-replay-warnings May 16 13:54:33: Authenticate/Decrypt packet error: bad packet ID (may be a replay): - see the man page entry for -no-replay and -replay-window for more info or silence this warning with -mute-replay-warnings May 16 13:54:33: Authenticate/Decrypt packet error: bad packet ID (may be a replay): - see the man page entry for -no-replay and -replay-window for more (.) I cannot remember 100%, but I'm pretty sure this was with UDP-Connections only and regardless of the server geo-location.

Viscosity vpn failed to create adapter.