Jump to content
TorGuard

Leaderboard


Popular Content

Showing content with the highest reputation since 03/21/2019 in all areas

  1. 1 point
    Hi Mike I would highly suggest you contact our support desk https://torguard.net/submitticket.php Maybe we can log in and have a look at what's going on. Regards
  2. 1 point
    Hi, did you upgrade from a much older build by chance? Can I ask that you do the following so we can make sure you start fresh? 1) Go to more settings --> general tab --> click "restore defaults" and then hit save (if you can't do this move to the next step) 2) Delete the Torguard app from the applications folder and empty your trash 3) Remove this folder: /users/user/Library/Application Support/VPNetworkLLC/TorGuard 4) Flush DNS >> https://torguard.net/knowledgebase.php?action=displayarticle&catid=71&id=227 5) Reboot 6) Reinstall TG Client latest version here https://torguard.net/downloads.php Let me know how you go.
  3. 1 point
    Was looking to find the best balanced settings for Torguard providing the most security with only a reasonable hit to throughput but could not find much details online. I decided to run some throughput tests on a few combinations of settings to determine the best option. The tests were done using speedtest.net using the same fixed remote server for all tests. In Torguard using the pin feature, I also fixed the VPN server IP for all tests. Throughput obviously varied based on server/ISP load but not by much. Also any test combinations where the numbers seemed to not make sense, I verified by doing the test again. Fixed Variables - Software Version - v3.90.0 - Used OpenVPN. I did test with OpenConnect with not much difference in speed and from the research so far OpenVPN is a more secure reliable option as of now. - Used UDP. TCP was about 40% slower than UDP and for general PC use losing a few packets has almost no noticeable effect. - Port - 1195 (SHA 256) - All other settings excluding the configuration changes listed below in the test were at default values. - Tests were done in order of security level (low to high) starting with Torguard completely disabled. Test Results Encryption Network Settings DL (Mbps) Loss Torguard Disabled Torguard Disabled 193 0% AES-128-CBC Default 164 15% AES-128-GCM Default 166 16% AES-256-CBC Default 160 20% AES-256-GCM Default 155 24% AES-256-CBC Block Outside DNS = On Name Server = None 163 19% AES-256-GCM Block Outside DNS = On Name Server = None 176 10% AES-256-CBC Block Outside DNS = On Name Server = VPN DNS 161 18% AES-256-GCM Block Outside DNS = On Name Server = VPN DNS 175 11% AES-256-CBC Block Outside DNS = On Name Server = Google 163 17% AES-256-GCM Block Outside DNS = On Name Server = Google 163 18% AES-256-CBC Block Outside DNS = Off Name Server = VPN DNS 164 18% AES-256-GCM Block Outside DNS = Off Name Server = VPN DNS 164 18% Summary -Using AES-256 vs AES-128 showed minor drop in throughput. -Adding the extra layers of security under DNS to prevent DNS resolve leaks had no negative impact on throughput. -Surprisingly after multiple repeat tests AES GCM (more secure) seems to provide better results using some of the DNS settings. Again there are obviously alot of other variables that would have impacted some of the results so they cannot be 100% accurate. It is also a limited test only taking 2 servers in to account but it does give a decent general idea as to what the best balanced options would be. Based on this test, the last configuration (in green) is the most secure option with a low amount of loss in throughput. Hope this helps any questions or corrections let me know.
  4. 1 point
    Interim further testing indicates you need to connect to your chosen VPN server on port 1912 for port forwarding to work - despite being able to choose from all connecting ports (1194, 1195 etc) for establishing your VPN on the port forwarding setup form. Obviously you can choose any unused port to forward. Don't forget you'll likely need to forward the same port as both TCP and UDP for torrenting.
  5. 1 point
    I had some issues earlier but support live chat helped me out. The app installed with some default settings which may not be optimal for port forwarding, not sure. Support recommended these changes: I was already connecting with OpenVPN over UDP but with a stronger cipher and a different port. I didn't modify my TorGuard DNS settings (just using DHCP and VPN-pushed once connected, instead of Google for everything). I did however uncheck 'Seamless Reconnect' (what does that do?) and I also checked WebRTC Leak Prevent. IPv6 Leak Prevent was already checked. I'd already added my desired VPN IP as a custom server in the TG app preferences, be sure to do that. If you want to test, you can connect to a country server and 'pin' its IP (click the pushpin next to the public IP once connected, then use that for your port forward request - set up a custom server if all works after a reconnect.) I also deleted and remade my port forward request in the control panel. Mine was a combined TCP and UDP one, I remade it for port 1912 on my chosen VPN IP. I'd already tried port 1194 and 1195 without success. Not entirely sure what made it work in the end - I should do more testing in future to figure it out. I guess support recommend I use a simpler cipher to avoid any session setup problems, I wouldn't have thought that would make a difference. I would be interested to see if port forwards only work if they are requested, and you connect, via port 1912.
×