Search the Community
Showing results for tags 'viscosity'.
Found 12 results
-
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): [ #256464 ] -- 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): [ #256465 ] -- 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): [ #256466 ] -- 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. As a result, the CPU usage on my Macbook is going crazy (process for Viscosity uses >100% CPU) and the fan is becoming noisy. While I know that I can mute log outputs, I'd like to know why these warnings are thrown. Any input would be appreciated!
-
I use Viscosity to connect to another OpenVPN server without issues, but when I import the .ovpn file for AirVPN and start browsing, the IP I'm connecting from shows my local IP, not the VPN. Occasionally it will switch, but most of the time I'm not actually routing traffic through the VPN as far as I can tell. Is there a config I'm missing or something?
-
Hello! I've been using the program Visocsity for Mac for quite awhile and I was just curious what settings/scripts you use to keep your conection to AirVPN secure. I just wanted to see if there is anything new I could take advantage of. There was a forum post made by another Air user about this topic 3 years ago. I thought this would be a good update and be useful to others who use Viscosity. Thanks! S.O.A.
-
Hi, I keep getting pretty regular server timeouts and disconnects, sometimes multiple times per day, sometimes the connection seems stable for days. At first I thought it would occur only on some servers (specific locations), but this does not seem to be the case. I've had these issues now in Ukraine, Romania, Sweden, Netherlands, ... (these are the locations I used most). Also using UDP or TCP does not seem to make a difference. My VPN Client is Viscosity running on OS X 10.9.5. The log - which is identical with every disconnect - looks like this (disconnect on Zaurak): Mar 30 18:43:29: [server] Inactivity timeout (--ping-restart), restartingMar 30 18:43:29: SIGUSR1[soft,ping-restart] received, process restartingMar 30 18:43:29: UDPv4 link local: [undef]Mar 30 18:43:29: UDPv4 link remote: [AF_INET]82.118.16.175:443Mar 30 18:43:36: [server] Peer Connection Initiated with [AF_INET]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!
-
I wonder if implemented correctly the reneg-sec n command in Viscosity. See screenshot. P.S.: I would like to reduce the time of re-keying for 30 minutes. I'm getting login normally on the server AirVPN. But I don't know if this line of code in the correct location. I'd appreciate it if you can help me! =)
-
Hello I a new user and would like to know how to set up an SSH tunnel with OpenVPN in my Mac with Viscosity App. I generated these files and imported them all to the Viscosity: https://cl.ly/aeTZ/Captura_de_Tela_2015-04-14_as_18.17.12.png [Or attached file!] I can connect via UDP-443 _ but I can't connect through SSH _-53. What am I doing wrong? I think I'm connected with OpenVPN but without the SSH tunnel. How should I do?
-
Hello, Below are two scripts, one for Viscosity for Mac, and the other for Windows that you can implement into Viscosity to close any program you specify upon VPN disconnection. They are very easy to implement. It should take you no longer than 30 seconds. The 5 step instruction process is included in the link. I hope this helps you out! Link for Mac: https://torguard.net/blog/how-to-setup-a-vpn-kill-switch-on-mac-with-torguard/ Link for Windows: https://torguard.net/blog/how-to-setup-vpn-kill-switch-in-windows-with-torguard/ SIDE NOTE-For Windows that don't use Viscosity there is another VPN killswitch that is free and works with every VPN. It is called VPNCheck.
-
All: My TunnelBlick client is not starting properly, and I cannot import the .ovpn or .tblk files into TunnelBlick. So, I have resorted to using Viscosity. The problem with Viscosity is that it is not updating my /etc/resolv.conf once the VPN client takes over. Does anyone use Viscosity out there? Is airdns.org acceptable to use for all my AirVPN connections?
-
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. This works ONLY for Viscosity users and ONLY if you have ANY firewall (in my case I'm using GData Internet Security 2015). 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. In short: We simply block ALL traffic on our others network adapters and just allow Viscosity (and the network adapters of viscosity). Step by step: 1. Create a new rule set called AirVPN or whatever else. 2. We need a to create only a few custom rules in our rule set 3. We need to allow the Openvpn.exe inside of the Viscosity folder. I recommend using the assistant of GData. 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. 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. 3d) At the end we block ALL other traffic 4. As previously told Viscosity creates network adapters. So we just need to apply this rule set to our local network adapter only. 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. But we can reconnect with Viscosity to our AirVPN servers. So we made sure that all traffic is going through our VPN tunnel. This works with all firewalls that support these steps and its very easy to set up. Feedback is appreciated.
-
In the last week or two I am experiencing problems in connecting to airvpn. I have been using viscosity without problems but It stopped connecting. I tried with tunnelblick and I receive the same error : Tunnelblick was unable to start OpenVPN to connect AirVPN_Europe_UDP-443. For details, see the log in the VPN Details… window Contents of the openvpnstart log: *Tunnelblick: openvpnstart log: Tunnelblick: Loading tun-signed.kext Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8). Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8). Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8). Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8). Tunnelblick: stderr from kextload: /Applications/Tunnelblick.app/Contents/Resources/tun-signed.kext failed to load - (libkern/kext) kext (kmod) start/stop routine failed; check the system/kernel logs for errors or try kextutil(8). Tunnelblick: Unable to load net.tunnelblick.tun and/or net.tunnelblick.tap kexts in 5 tries. Status = 71