On 25/08/2012 14:15, dan wrote:
But there must be multiple ways, using linux, (either by using virtual
interfaces and / or routing or iptables rules) such that a particular
instance of TF2 uses a NIC (real or virtual) that only has one IP
address assigned to it, so that it doesn't need the +ip parameter
setting in the first place - and such that that outbound traffic goes
via the right IP address.
Replying to myself, but the two most obvious ways of doing this might be
(a) Using LD_PRELOAD to load a bind.so that forces the IP address
(getting the address to use from a shell variable) before calling the
original library, - assuming the broken behaviour is caused by them
using 0.0.0.0
It should works if they aren't statically linked etc. Examples and code
if you google for the method.
(b) Policy routing, but it's a bit of a heady topic and seems OTT if the
bug is Valve's. I'd sooner do (a) or the original suggestion to use one
IP address and different ports instead of multiple IP addresses
(assuming that's possible in your config) and hope they fix it.
--
Dan.
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
