Jump to content
TorGuard

Search the Community

Showing results for tags 'disconnect'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The Lounge
    • TorGuard News
    • Introductions
    • General Stuff
    • Member Tutorials
    • TorGuard Reviews
  • TorGuard Software Releases
    • Network Status
    • TorGuard Client Releases
    • Android Client Releases
    • iOS App Releases
    • Chrome Extension Releases
    • Firefox Extension Releases
  • TorGuard VPN Support
    • VPN Questions and General Support
    • VPN Windows Support
    • VPN Mac Support
    • VPN Linux Support
    • VPN Router Support
    • iOS VPN Support
    • Android VPN Support
  • TorGuard Proxy Support
    • Proxy Questions and General Support
    • Firefox Extension Support
    • Chrome Extension Support

Found 5 results

  1. So I attach a laptop at work to Xfinity's hotspots (mainly to browse outside of my job's network) and use the TorGuard client to further protect what I'm doing. The signal from the hotspot is really strong and whenever I don't use TG's VPN, it's remains solid throughout the day. If I connect to a VPN, it'll generally disconnect after 10-15 minutes, sometimes quicker, sometimes longer. I know it's doing it since I have app kill enabled for the browser, just in case. I read in Xfinity's forums that they block VPN's on the public wifi's (I don't seem to have the same problem at home - at least not as much). Are there specific settings that I should be using to get around these constant disconnects? I read that setting TorGuard to TCP:80 will do the trick and I'm trying it, but thought I would reach out to see if anyone else is having problems or has specific answers. Thanks!
  2. I have been testing the new Seamless reconnect feature of TorGuard Windows client v0.3.78 and I am having a weird issue. I usually connect to the internet in my Windows 10 laptop via USB tethering my cellular network. Most of the times the network is stable. In the previous version, TorGuard v0.3.77, sometimes I randomly got disconnected and reconnected(most probably due to poor network reception?). The reconnect was automatic, I didn't have to do anything. But With the new Seamless reconnect feature in v0.3.78 the reconnect doesn't happen when the network comes back and a popup appears saying reconnect failed. I tested the theory by switching mobile data on/off. On the Standard Seamless reconnect, the network will automatically reconnect. But with the New Seamless reconnect, I get the popup as seen in the attached image when I switch back the network ON.
  3. Hi! I have just started using Torguard VPN and proxy. While setting up the VPN, I noticed this admonition: "always disconnect before closing down the software or shutting down your computer." (Found here, under "Linux" and "Windows" tabs alike: https://torguard.net/gettingstartedvpn.php ) This warning seems important since it is set in bold. But it is ill-explained. Why must I disconnect from Torguard before shutting down my computer? What happens if I shut down my computer without disconnecting from Torguard? Thanks in advance!
  4. On one of my devices I've been getting the following error all day long when I connect to torguard: "Blocking DNS Failed!" The connection is then dropped. This device has connected without issue in the past, and other devices are connecting as normal on the same network. I didn't change anything in the settings. Any suggestions? Edit: This problem seems to have been fixed by updating torguard. The auto-updater didn't show a new version until today.
  5. This hack will create PF firewall rules on mac that will only allow in/out traffic to single IP (TG's VPN server in this case). When disconnect happens, you won't be able to surf, and only pinging that IP works. 1) Open Temrinal and type this
 sudo nano /etc/pf.conf Enter your admin password after that, and PF file will open 2) Scroll to the bottom, and add the following at the bottom --------- block out on en0 from 192.168.0.0/16 to any block out on en3 from 192.168.0.0/16 to any pass out quick on en0 from 192.168.0.0/16 to 178.162.216.8 pass out quick on en3 from 192.168.0.0/16 to 178.162.216.8 pass out quick on utun0 from any to any --------- These rules will block traffic on ethernet and on wifi, unless that traffic is going towards 178.162.216.8 (IP of TG's for example) or unless VPN is connected (last line), then traffic is allowed. Here utun0 is name of our virtual VPN adapter, and en0 and en3 are names of ethernet and wifi. You can find out those names by running “ifconfig†in terminal.
 3) Enable PF, by running in termial: sudo pfctl -e 4) Load the rules sudo pfctl -f /etc/pf.conf Now if VPN gets disconnected, you won't have access to internet, not counting the IP address specified before 5) To regain Internet access, disable PF in terminal sudo pfctl -d
×