Multihomed machine - publishing of wrong address

[AnnihilatorSC]

I have to completely disable the other network interface in order to get the proper IP address published to the master server. -multihome option does nothing except bind the service to the address in question, but the wrong IP STILL gets published.
Is there a workaround, short of perm-disabling the interface (which is, of course, unacceptable)?

[graysky]

Hehe, I'd like to know the answer to this question too... you're telling me that all the UT3 servers are NOT behind firewall/routers at this time???

[Naked_Ape]

At this point it is not possible to host UT3 beta demo server behind NAT. It's also rather awkward putting them behind a firewall since the query ports are randomly allocated.

[graysky]

Wow, that is just totally retarded.

[gmork]

At this point it is not possible to host UT3 beta demo server behind NAT. It's also rather awkward putting them behind a firewall since the query ports are randomly allocated.

It works like a charm hosting a server behind NAT...IF you run the linux version of the server. I noticed that when I first tried the linux dedicated server. Everything worked perfekt. I just forwardad udp ports 7777-7787 to the server and voila! Players start to join almost instantly. Then I discovered the linux problem that occures after maprotation and players got kicked out. So I rebooted my testserver into XP and started playing with the windows version as server. Using same ports, same private ip etc. Not a player could join..the wrong ip was published on the master server list.

I've reported this issue to the developers...but now you know...