tesawh

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Can’t see WinsockUI interface in qBittorrent #13296
    tesawh
    Participant

      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).

      in reply to: Can’t see WinsockUI interface in qBittorrent #13294
      tesawh
      Participant

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

        in reply to: Can’t see WinsockUI interface in qBittorrent #13285
        tesawh
        Participant

          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 1 year, 4 months ago by tesawh.
          • This reply was modified 1 year, 4 months ago by tesawh.
          • This reply was modified 1 year, 4 months ago by tesawh.
          in reply to: Can’t see WinsockUI interface in qBittorrent #13282
          tesawh
          Participant

            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 1 year, 4 months ago by tesawh.
          Viewing 4 posts - 1 through 4 (of 4 total)