Jump to content
TorGuard

kurisu

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

1 Neutral

About kurisu

  • Rank
    Member
  1. Using the TorGuard VPN-provided DNS servers, occasionally I have lookup failures. Today I noticed all of FiiO's web sites failing to resolve: fiio.net fiio.com fiio.me Although their site loaded fine when accessed by its IP. The usual web-based down detectors also showed the web sites were up. I've had this before on one of my domains - nameserver failures until I did an nslookup, at which point it started resolving in a browser. However this didn't work for the fiio domains: And so on. In verbose mode: Same with secondary server, Timeouts across the board. If I specify a different nameserver, all these domains resolve instantly. However I want to keep my DNS traffic on-net while using a VPN but these timeouts obviously cause problems Are you aware of any issues with DNS @Support?
  2. Agreed. I hunted around for a while until I found a server in my preferred region with decent throughput, then set up port forwards manually. I'd be happy for the option of a longer connection setup time but dynamically created port forwards. As it is, if my chosen server is heavily loaded, I stay on it (increasing the problem of load) - because manually creating port forwards on another server is quite long-winded. 'Camping' port forward allocations on multiple servers, so I can hop around depending on load, is something I've not done because I think it's antisocial. The port forwarding features and design needs a bit of TLC
  3. Been a good few years since I last used slsk! However Soulseek shouldn't do anything a torrent client wouldn't do, so if you're VPNing your entire connection I imagine you'll be fine. If you have slsk open across a reconnect, it may advertise your ISP IP if you initially connect during that time, but if you enable the connectivity lockdown / kill switch when disconnected from VPN, you should be fine. Run CurPorts or NetworkTrafficView from Nirsoft.net and see what it's connecting out on to both UDP and TCP, and what interfaces it's binding to. Disable IPv6 if required, that should be it.
  4. kurisu

    Torguard "wait"

    I saw your original post - what was the fix?
  5. Oh dear, that's not good. Have you tried live chat support applet on each web site / forum page? I'd imagine if you can provide proof of email account access or ID then there's no reason why they shouldn't let you back in. You've run into the same problem I had once with Google Authenticator. Ditch it and use Authy - you can have it back up to the cloud and sync across multiple devices. It's not perfect, but it's far better than Google Authenticator. Another alternative is Microsoft Authenticator.
  6. Not a premium network customer on TG as they have no premium servers in my country. However I've experienced similar; on my gigabit symmetric line I can easily achieve >600 Mbit in both directions using any NordVPN Manchester VPN server, no tweaks to adapters required. Some servers give even faster speeds. TorGuard seems to have some catching up to do with their competitors in this regard.
  7. DEFINITELY more servers in the North of the UK are required. Some in Ireland, some in Manchester, some in Edinburgh as well as the existing London servers. My peering to anything connected via LINX Manchester (including things further north of that) is radically better than the speeds to London, by a factor of 4 or 5. I'd also appreciate a more diverse number of servers in the UK as the existing servers I think are becoming more contended. M247 and UKFast would be excellent first choices for Manchester based servers.
  8. kurisu

    Starts fast, then slows to a crawl

    It may be. ISPs usually possess equipment which enables them to analyse what protocols and types of traffic are travelling over your connection, and keep count of the cumulative throughput. It may be that your ISP has a Fair Usage Policy regarding the total amount of bandwidth you're permitted to use at maximum speed before your speed is reduced. In the UK Virgin Media (the cable ISP) did this for many years using the Cisco Subscriber Traffic Management (STM) system, and many customers who used to be heavier users were quickly reduced to a quarter of their speeds for hours. With other ISPs, they can choose to more gradually restrict the amount of throughput achievable on a connection. Other ISPs can do this entirely dynamically dependent on network contention. However, that's a worst-case scenario. It may be that your ethernet adapter is either misconfigured or running older drivers. Failing that, it may be the Netgear router. You're running the latest TorGuard client? What settings are you using to connect in the TorGuard client? Have you ever altered any of the network adapter advanced settings, either on your ethernet adapter or the TorGuard VPN adapter? What model is the router? Some are not always able to cope with sustained VPN traffic throughput at higher speeds. Are you running any QoS on the router? Have you upgraded or downgraded the router firmware recently?
  9. kurisu

    Starts fast, then slows to a crawl

    What router are you using? Not all are 100% happy with sustained VPN traffic for a prolonged period. Sounds nuts but it's true. Aside from that, checked your network settings are all kosher? What are you using, wifi or ethernet? Have you tried connecting on different protocols in the client? Initial fast speed then gradual slowdown is sometimes a symptom of ISP traffic shaping.
  10. Yep, already enabled - didn't seem to stop the OS attempting to route DNS via the physical interface while its metric (previously manually set due to my local network configuration) was lower than the VPN adapter. Setting the ethernet interface's metric slightly higher, then manually setting the TorGuard TAP adapter to a lower value instantly solved the problem. Appears to be a bug in TG's implementation.
  11. Surprisingly I found this discussed elsewhere - some AirVPN users were having the same problem. Turns out, DNS queries were still try to go out direct through my ethernet adapter, despite being connected to the VPN. I have a manual interface metric set on my ethernet adapter as I also have wifi on this device which I occasionally use (normally it's completely disconnected from a network). As soon as I set the interface metric slightly higher than the TorGuard VPN TAP adapter (in each adapter's IPv4 settings) DNS queries while VPNed began to respond instantly. https://airvpn.org/topic/20812-very-very-slow-dns-lookup/ discusses this and provides the steps to fix. This may be a bug in how TorGuard implements the TAP adapter? NordVPN connections don't have this problem. I've also noticed I can still connect to my machine directly via its ISP IP address and a predefined port forward when connected over TorGuard, whereas when connected via NordVPN, it stops responding to WAN requests on its ISP IP entirely.
  12. kurisu

    Weird Geolocation Issues

    Probably numerous factors - whether they've reallocated any IPs from blocks they control, whether those servers are new acquisitions and the previous holder of the IP was in those countries, or whether the public geoip databases have updated yet. I've not had any wrong country geolocations on UK servers I've tried so far, but I've not tried many in the US.
  13. kurisu

    Port Forward doubt

    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.
  14. I've been experimenting since setting up my TG account. Something that's puzzling me is that, whatever DNS setting I choose (pushed DNS, VPN DNS, Google, OpenDNS, CloudFlare...), initial DNS resolution for domains is really slow after the VPN comes up. I mean, 10-15 seconds slow. Once it's resolved once, it's fine - but until then, wow, it's so slow. So as you can imagine, loading pretty much any web site takes a lot longer than it should with all the queries for various domains and third-party hosted content. Disconnect from the VPN and - hey presto - DNS is instantaneous again. I also have a NordVPN account. DNS resolution through their network (using their own DNS solution) was always as fast as my ISP's (and 1.1.1.1). On my Android device however, DNS resolution is normal - as it is direct. Is this a quirk of TorGuard's design of their VPN client, is it an oddity of Windows 10 - which is perhaps peculiar to just my computer? - or has anyone else experienced this and identified a reason for it happening?
  15. kurisu

    OpenVPN servers available report

    Agreed, this would be a very useful feature, in the client and/or online. I can't find a list of utilisation for each individual search in a pool, only the static list of server addresses by country.
×