qbittorrent and port mapping

[ghost]

Hi,

I have the following configuration (2 different containers) with qbittorrent :

For gluten

services:
  gluetun:
    image: qmcgaw/gluetun:latest
    container_name: gluetun
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun:/dev/net/tun
    ports:
      - 8888:8888/tcp # HTTP proxy. !! I Guess I can remove this !!
      - 8388:8388/tcp # Shadowsocks  !! I Guess I can remove this !!
      - 8388:8388/udp # Shadowsocks  !! I Guess I can remove this !!
      - 8090:8090 # port for qbittorrent
      # - 6881:6881   !! Why people add this ? !!
      # - 6881:6881/udp  !! Why people add this ? !!
    volumes:
      - xxx/gluetun:/gluetun
    environment:
      - VPN_SERVICE_PROVIDER=xxx
      - VPN_TYPE=openvpn
      - OPENVPN_USER= xxx
      - OPENVPN_PASSWORD= xxx
      - SERVER_REGIONS= xxx
      - TZ=xxx
    restart: unless-stopped

For qbittorrent

services:
  torrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    network_mode: container:gluetun
    environment:
      - WEBUI_PORT=8090
      - PUID=1001
      - PGID=100
      - TZ= xx
    volumes:
      -xx:/config
      -xx:/downloads
    restart: unless-stopped

As you can see I do not specify ports for qbittorent ( 6881 for tcp and udp) but most people do (at least what I have seen).
Still (and having the default settings on qbittorent) using https://ipleak.net, I can see that qbittorrent traffic goes through my vpn provider on port 6881 (which is not open on my router and which is the default port on qbittorrent). For me this is THE expect behavior. Or ?

Best

[frepke]

Maybe you can change the network_mode for the torrent container from container:gluetun to service:gluetun and check again.

[ghost]

Hello,
and thanks. Everything works BUT I am surprised it works given my configuration.
As for your suggestion, it gives an error (as I have 2 different containers). But I guess this not the 'issue' there.
Best

[ghost]

As far as I understand :

• For gluten : only 8090 should be needed in my configuration (to access qbittorrent).
• Why do people sometimes add this ?

ports:
   - 6881:6881   !! Why people add this ? !!
   - 6881:6881/udp  !! Why people add this ? !!

Or am I wrong ?

[aounakram]

I believe if anything it is correct not to map those ports when using gluetun. I was wondering the same thing, and landed on this thread. After commenting out those ports, the issue I was having of certain torr's not getting any trackers/peers resolved itself. I think it makes sense because mapping the ports exposes them to your internal network, which is not what we want for a listening port while using a vpn. Just thought I'd share my 2 cents.

[oblivioncth]

I am also surprised to see those port mappings randomly thrown into example compose stacks with basically no comment about them. I keep trying to think of something I'm missing, but it's my understanding as well that such a mapping would make no sense as it would potentially allow the connection to bypass the VPN entirely (defeating the entire purposes) since it maps the ports out onto your LAN, an theoretically WAN if something like UPnP is enabled.