heavy packet loss with tunneled teamspeak instance #920

Closed
opened 2026-04-05 18:00:28 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @julius-gmeinder on 9/15/2025

a few days ago i migrated from npm to pangolin (v1.9.4) and im experiencing heavy packet loss when connected to the teamspeak instance in my homelab

connection info when connected via tunnel
Image

now to make sure teamspeak itself is not the cause here, i setup a seperate firewall rule and dns record to connect to the teamspeak without routing and tunneling, which resolves the packet loss entirely.
Image

steps to reproduce

1. docker teamspeak instance on an external site connected via newt (v1.4.4)

services:
  teamspeak:
    container_name: teamspeak
    image: teamspeak
    restart: always
    ports:
      - 9987:9987/udp
      - 10011:10011
      - 30033:30033
    environment:
      TS3SERVER_DB_PLUGIN: ts3db_mariadb
      TS3SERVER_DB_SQLCREATEPATH: create_mariadb
      TS3SERVER_DB_HOST: ***
      TS3SERVER_DB_USER: ***
      TS3SERVER_DB_PASSWORD: ***
      TS3SERVER_DB_NAME: ***
      TS3SERVER_DB_WAITUNTILREADY: 30
      TS3SERVER_LICENSE: accept

2.

  • create TCP/UDP resource for port 9987/udp pointing to the external teamspeak instance, in my case
site: homelab, ip/hostname: 192.168.0.4, port: 9987
  • update traefik_config.yml entrypoints
udp-9987: # teamspeak
    address: ":9987/udp"
  • update gerbils ports in docker-compose.yaml
- 9987:9987/udp # teamspeak
  • open VPS ports (hetzner in my case)

3. connect to teamspeak server via the TeamSpeak client

any help appreciated, im fine with my current bandaid solution, but for completions sake and learning i would still like to know what could be causing this to happen

*Originally created by @julius-gmeinder on 9/15/2025* a few days ago i migrated from npm to pangolin (v1.9.4) and im experiencing heavy packet loss when connected to the teamspeak instance in my homelab connection info when connected via tunnel <img width="179" height="221" alt="Image" src="https://github.com/user-attachments/assets/f39e2efc-85eb-4ae1-8d55-1fcb64584caf" /> now to make sure teamspeak itself is not the cause here, i setup a seperate firewall rule and dns record to connect to the teamspeak without routing and tunneling, which resolves the packet loss entirely. <img width="180" height="218" alt="Image" src="https://github.com/user-attachments/assets/753af0a2-eed3-41fe-b874-1c4bdfdb9954" /> # steps to reproduce ### 1. docker teamspeak instance on an external site connected via newt (v1.4.4) ``` services: teamspeak: container_name: teamspeak image: teamspeak restart: always ports: - 9987:9987/udp - 10011:10011 - 30033:30033 environment: TS3SERVER_DB_PLUGIN: ts3db_mariadb TS3SERVER_DB_SQLCREATEPATH: create_mariadb TS3SERVER_DB_HOST: *** TS3SERVER_DB_USER: *** TS3SERVER_DB_PASSWORD: *** TS3SERVER_DB_NAME: *** TS3SERVER_DB_WAITUNTILREADY: 30 TS3SERVER_LICENSE: accept ``` ### 2. - create TCP/UDP resource for port 9987/udp pointing to the external teamspeak instance, in my case ``` site: homelab, ip/hostname: 192.168.0.4, port: 9987 ``` - update traefik_config.yml entrypoints ``` udp-9987: # teamspeak address: ":9987/udp" ``` - update gerbils ports in docker-compose.yaml ``` - 9987:9987/udp # teamspeak ``` - open VPS ports (hetzner in my case) ### 3. connect to teamspeak server via the TeamSpeak client any help appreciated, im fine with my current bandaid solution, but for completions sake and learning i would still like to know what could be causing this to happen
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/pangolin#920