Floating IP not forwarding traffic

Posted April 19, 2016 7.6k views
DebianNetworkingFirewallLoad BalancingHigh Availability

I have ran into an odd issue I haven’t been able to solve when using a Floating IP. I have a Teamspeak 3 server running, binding to for each service (filemanager 30033/tcp, query 10011/tcp and voice 9987/tcp).

I can access this server when connecting to my droplets ip address directly, but not it’s Floating IP address. Other services such as ssh, ftp, http and https work as expected.


These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
3 answers

I’m encountering the issue with SSH. Anytime I try to ssh to the box using the floating ip address the attempt times out. I can successfully ssh to the non-floating IP address.

I can successfully ssh to the floating ip if I drop the firewall, so I believe the issue is somehow firewall related. I should add, I have the same exact rules in the firewall for both the floating and non-floating ip.

OK I got teamspeak working using the floating ip. Install teampeak in docker using this docker image with the volume method:
You won’t have access to the config files or database but they will be in the ts3-data volume so when there is an update you can load a new docker container with the same data volume.
docker volume create (Since docker-engine 1.9)

docker volume create –name ts3-data
docker run –name=ts3 -p 9987:9987/udp -p 30033:30033 -p 10011:10011 -v ts3-data:/home/ts3/data devalx/docker-teamspeak3:latest

  • As a side note I couldn’t get the mounted host directory option to load without having my own data files and when i tried this from a different docker image of teamspeak the floater ip didn’t work so I suspect there is something devalx changed in his image to make it work.