IP Address Conflict? (TF2)

[MysticGuitar]

Background: I have five IP addresses which have all already been added to the dedicated server, and the IP addresses can be used and 'selected' when creating a new TF2 server.
However, people are unable to connect to the server, and the server does not appear in the master list.
(mind you, people appear to be able to connect when they join it through their favorites list, but not via direct IP or friend invitations)

This is what the 'status' command generates;

Quote:] status
hostname: [HIDDEN]
version : 1.2.1.9/22 4993 secure
udp/ip : xx.xx.xxx.139:27015 (public ip: xx.xx.xxx.138)
account : logged in
map : ctf_2fort at: 0 x, 0 y, 0 z
players : 1 (24 max)

It appears as though the server is automatically using the main IP address that was originally associated with the box, rather than the IP assigned to the actual server.

How do I fix that?


It's a dedicated box running Linux CentOS 32 bit, and all ports have been forwarded through iptables.

Speedy help is greatly appreciated.


Thanks.


Server specs;

OS - Centos 32 bit
Processor - Duel Intel Xeon 3Ghz
RAM - 8 GB
Game - Team Fortress 2

(I apologize if this was crudely formatted. I've been awake all night)

[kossolax]

I've same problem, I'm using ip failover. This came since 03th july update.

the server is bound to this ip, but the public is not.

In server log, I've got random IP usage (once the failover, once not): http://pastebin.com/raw.php?i=GDpk4Yar

As temp fix, I've routed UDP from eth0 to eth0:0 using iptables.
And it connection info is displayed correctly

EDIT:
Here is iptables rules:

Code:

echo "1" > /proc/sys/net/ipv4/ip_forward
iptables -P FORWARD ACCEPT

iptables -A PREROUTING -t nat -d IP_FROM -p udp --dport 27015 -j DNAT --to-destination IP_TO:27015
iptables -t nat -A POSTROUTING -d IP_TO -p udp --dport 27015 -j SNAT --to IP_FROM

Good luck