Jump to content
TorGuard

legitsu

Members
  • Content count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About legitsu

  • Rank
    Newbie
  1. this was promised in a post several months ago and still hasn't made its way in we need command line options for the following connect <user> >password> <server> <ip> <port> disconnect quit(safe) settings
  2. TorGuard Client v0.3.74

    good the clean up loop issue was annoying as I manage tg with a autohotkey script and the client lacks any command line options for disconnect /connect or quit so i am forced to kill or force start the process really really need command like options
  3. its a on-going issue with the client qbt implemented a fix that reduces the occurrence its because of how the tap adapter handles ip assignment when the vpn isn't connected the tap adapter doesn't have a address if a torrent client is started before the vpn is up and the address isn't set or there is a route change mid interface detection it stalls most torrent clients only do interface/ip detection on startup if the detection routine is run the client doesn't get a address and the client stalls bottom line tap adapter needs to have a fixxed static ip and then the vpn ip pushed when the bridge is esablished (not possible with vanilla builds of tap a custom build will be required) it could be fixed with some janky scripts by re-connecting the vpn or resetting the interface without disconnecting the bridge but since there are not any command line options this isn't possible
  4. How to connect / disconnect via script?

    REALLY need this implemented need command line options for connect/disconnect,protocol server ect if this isn't implemented by the time my bill cycle is up i am changing providers its a must have for management scripts not everybody wants there vpns to run all the time
  5. sry for the late reply apparently the board doesn't send emails yes the issue 'should' be mostly resolved with the newest qbt however i suggest supporting windows 10's native vpn management which is getting some improvements with the fall creators updates as well as making sure the interface is always up regardless of weather or not its connected
  6. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/0. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP_SSL/0. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/4242. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/0. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/4242. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/4242. Reason: The requested address is not valid in its context. 8/28/2017 11:39 PM - qBittorrent failed listening on interface 10.65.197.219 port: TCP/4242. Reason: The requested address is not valid in its context. it looks like it might be qbits fault its not waiting for the vpn to accually be up and then not recovering it would be possible to implement a vpn client work around by keeping the address state even when disconnected
  7. @Support confirmed here as well: also causes torguard to spit a 'problem setting up connection' when qbittorrent is started at the same time as the client (which I do with a autohotkey script that waits for qbittorrent.exe and then starts the vpn client) I opened a issue on the qbits git but I am not hopeful as binding to tap usually either works or doesn't
×