[tesawh]

Thanks, what I mean is that using it as a sort of kill switch, not letting any traffic go through from qBit if accidentally opened without VPN (or VPN fails).

[tesawh]

So any way to actually bind the interface or go around the problem?

[tesawh]

My mistake, I can see the connection now (can’t edit my post though anymore, would be useful if you could edit posts for longer).

Some differences I’ve noticed, Wireguard makes a temporary connection (that it deletes) named after your config file, Wiresock makes a permanent connection named Wiresock.

As for why it doesn’t show on qBittorrent, maybe it’s because it’s registered as a LAN network or maybe because it’s permanent (that wouldn’t make sense, as others show up and even LAN shows up)?

• This reply was modified 8 months, 4 weeks ago by tesawh.
• This reply was modified 8 months, 4 weeks ago by tesawh.
• This reply was modified 8 months, 4 weeks ago by tesawh.

[tesawh]

What I mean is that it doesn’t register as a connection (named the same as the wireguard config) in the “View your active networks” page unlike vanilla wireguard or most other VPNs.

Edit: To clarify, it does make a connection, but it replaces the network you are already on, instead of making another connection alongside it.

• This reply was modified 8 months, 4 weeks ago by tesawh.

[Author]

Posts