I’m already using Torguard for a few years (mostle OpenVPN in Docker containers).
Now I installed the Torguard client on my Debian virtual machine to use with Wireguard and qBittorent.
So I installed Torguard, installed Wireguard, set my port forward and made connection, all working fine as expected.
However when the connection is up I can no longer access (from another pc in same lan of virtual machine), the webinterface of qBittorent who resides on the same ip of the virtual machine, so ip:portnumber
When I disconnect I can connect again to it. Also I noticed in the routing table Torguard uses a hard coded 192.168.0.0 but my local range is 10.10.0.0 so could this be the cause?
Or do I need to manually alter the routing to make it work?
Question
Kopernikus 0
Hi,
I’m already using Torguard for a few years (mostle OpenVPN in Docker containers).
Now I installed the Torguard client on my Debian virtual machine to use with Wireguard and qBittorent.
So I installed Torguard, installed Wireguard, set my port forward and made connection, all working fine as expected.
However when the connection is up I can no longer access (from another pc in same lan of virtual machine), the webinterface of qBittorent who resides on the same ip of the virtual machine, so ip:portnumber
When I disconnect I can connect again to it. Also I noticed in the routing table Torguard uses a hard coded 192.168.0.0 but my local range is 10.10.0.0 so could this be the cause?
Or do I need to manually alter the routing to make it work?
Link to post
Share on other sites
2 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.