frequent reconnects with gluetun

[balkie31 0]

Ive been using gluetun along with slskd anf qbittorrent.  The connection works for a few days or so and then ill end up getting a new ip.  Since im using forwarded ports, ill need to restart slskd and qbit to rebind them and get the ports showing as open again for the containers.  Is this normal?  Or are there some settings im missing?    Sorry for thr formatting, i just cant get it to work out on mobile

qmcgaw/gluetun:v3
        container_name: gluetun                                  cap_add:
           - NET_ADMIN                                                  devices:                                                                   - /dev/net/tun:/dev/net/tun                           volumes:                                                                  - /mnt/Media2/Docker/Configs/gluetun:/gluetun/                           
          ports:                                                                        - 8114:8000                                                          - 8115:8115                                                          - 18678:18678                                                    - 18678:18678/udp                                            - 3050:5030                                                          - 3150:5031
              - 30050:50300                                                    - 3040:9765
              - 9091:9091                                                          - 34014:34014
              - 34014:34014/udp                                            - 14499:14499                                                    - 14499:14499/udp                                         environment:                                                          - VPN_SERVICE_PROVIDER=airvpn                - VPN_TYPE=wireguard                                    - WIREGUARD_PRIVATE_KEY=xxxxxxx       
              - WIREGUARD_PRESHARED_KEY=xxxxxxx                    - WIREGUARD_ADDRESSES=xxxxxxx                              - SERVER_COUNTRIES=United States                                                         
              - FIREWALL_VPN_INPUT_PORTS=18678,14499
              - HEALTH_RESTART_VPN=on                          - HTTPPROXY=on
              - FIREWALL_OUTBOUND_PERMITTED_IPS=0.0.0.0/0                                 - DNS_KEEP_NAMESERVER=off
               - FIREWALL_DEBUG=on                                     - WIREGUARD_MTU=1420                                 - FIREWALL_OUTBOUND_SUBNETS=192.168.68.0/24
               - UPDATER_PERIOD=24h                             healthcheck:
             test: ["CMD", "/gluetun-entrypoint", "healthcheck"]                         
             interval: 30s                                                         timeout: 10s                                                       retries: 3                                                               start_period: 60s
    sysctls:                                                                      - net.ipv4.conf.all.src_valid_mark=1
          - net.ipv6.conf.all.disable_ipv6=1              restart: unless-stopped:

Edited ... by balkie31

[Staff 10511]

@balkie31

Hello!

For residential broadband (DSL / cable / FTTH), DHCP lease times are most commonly:
~12–24 hours (very common baseline)
~1–3 days  (slightly less common)
Occasionally up to ~7 days (less common, but happens)

This aligns with general network guidance where stable networks use 1–7 day leases. Therefore, it is normal that you may need a re-connection every few days. You can consider to tell GlueTun to re-connect always to the same server, by setting the proper environment variable. You would be sure that your system would appear on the Internet always with the same IP address (the exit-IP address of the VPN server); on the other hand, if the specific VPN server goes down, GlueTun will be unable to re-connect as long as that server does not come up again. In any case, you may always need to re-start the torrent software as GlueTun will bring the virtual network interface down and up again.

Kind regards