VOIP and sv.interfaceIP/sv.serverIP
sjdel at nycap.rr.com
sjdel at nycap.rr.com
Tue Jul 5 16:15:25 EDT 2005
Don't know if this has been addressed yet or not, if so, I'll dig some more through my list emails...
I have a server whose primary IP on my ethernet interface isn't supposed to be used for anything. I have 12
other virtual IPs defined and have our bf2 server on the first virtual interface.
as we know, in this situation, you need to have both sv.serverIP and sv.interfaceIP defined in order for the
server to bind to a specific port. Problem here is that VOIP will still bind to 0.0.0.0:55124-55125.
Anyone in a similar situation find a solution to this?
More information about the Bf1942
mailing list