Forum

Page 2 of 2 FirstFirst 12
Results 16 to 21 of 21
  1. #16
    Join Date
    December 2004
    Location
    RF
    Posts
    3,007
    The problem is a wrong NAT configuration. On server, since all addresses are a server address.

  2. #17
    Join Date
    March 2016
    Posts
    1
    Have the same problem as the post owner. All my clients are getting server IP as their own. I know you say that the problem is wrong NAT configuration, but is there a way to go around that?

  3. #18
    Join Date
    December 2004
    Location
    RF
    Posts
    3,007
    Fix your server. This is not a TS3 question.

  4. #19
    Join Date
    February 2018
    Posts
    4

    Question Offical Docker Image: Gateway IP instead of Real Client IP displayed

    Hello,

    I migrated my teamspeak to docker. The real client ip's are not displayed anymore. Instead every client has the ip of the docker0 gateway:

    Code:
    client connected 'test'(id:4787) from 172.17.0.1:27309
    Is there any way to pass the real ip to the container?
    Last edited by dante696; February 22nd, 2018 at 11:30 AM. Reason: merged

  5. #20
    Join Date
    June 2008
    Posts
    18,260
    This is not a problem with docker (thread merged).
    Your Gateway is setup to guide clients trough 172.17.0.1 first.

    Check your router settings.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  6. #21
    Join Date
    February 2018
    Posts
    4

    Question

    Quote Originally Posted by dante696 View Post
    This is not a problem with docker (thread merged).
    Your Gateway is setup to guide clients trough 172.17.0.1 first.

    Check your router settings.
    But until I hosted my TS on my host without docker everything was fine? What do you mean by router config? I could not find any information how to configure my network properly.

    Docker Container with internal IP 172.17.0.4:

    Code:
    [email protected]:~# iptables -t nat -vnL POSTROUTING
    Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
     pkts bytes target     prot opt in     out     source               destination         
    42690 2545K MASQUERADE  all  --  *      !docker0  172.17.0.0/16        0.0.0.0/0           
       34  2004 MASQUERADE  all  --  *      eth0    10.0.0.0/8           0.0.0.0/0           
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.2           172.17.0.2           tcp dpt:49161
        0     0 MASQUERADE  udp  --  *      *       172.17.0.2           172.17.0.2           udp dpt:49160
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.2           172.17.0.2           tcp dpt:80
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.3           172.17.0.3           tcp dpt:50000
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.3           172.17.0.3           tcp dpt:8080
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.4           172.17.0.4           tcp dpt:30033
        0     0 MASQUERADE  tcp  --  *      *       172.17.0.4           172.17.0.4           tcp dpt:10011
        0     0 MASQUERADE  udp  --  *      *       172.17.0.4           172.17.0.4           udp dpt:9989
        0     0 MASQUERADE  udp  --  *      *       172.17.0.4           172.17.0.4           udp dpt:9988
        0     0 MASQUERADE  udp  --  *      *       172.17.0.4           172.17.0.4           udp dpt:9987
    74670 4348K MASQUERADE  all  --  *      *       0.0.0.0/0            0.0.0.0/0
    UPDATE:

    I could solve the problem, if I run docker with the option --net=host:

    Code:
    docker run --net=host ...
    OR enable forwarding:

    https://docs.docker.com/network/brid...-outside-world
    Last edited by Henok; February 22nd, 2018 at 08:45 PM. Reason: SOLUTION FOUND

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Server drops users if more then 12 clients connected
    By tbede in forum Server Support
    Replies: 6
    Last Post: February 6th, 2014, 09:04 PM
  2. Replies: 1
    Last Post: September 4th, 2012, 03:28 PM
  3. Skinning all clients connected to a server
    By rebeldragon611 in forum Skins / Icon & Sound Packs
    Replies: 2
    Last Post: April 9th, 2012, 09:05 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •