-multihome Causes Connection Problems? Bug?

Discussion in 'Monday Night Combat PC Discussion' started by Bunni, February 17, 2011.

  1. Bunni

    Bunni New Member

    Messages:
    4
    Likes Received:
    0
    I have been having trouble with multihome. I have a dedicated server with many ip's available, but one inparticular i need to bind to. With multihome, very rarely am i able to see and or join the server off the server list.

    Altering the serverinstance # yields 1 of 3 out comes:
    1) I can see the server in the server list, but cannot join (times out)
    2) I cannot see the server in the server list, but can join via favorites
    3) (super rare) works as expected.

    In all 3 i can join via console (open ip:port).

    With #1, it seems that the port (and or ip) that the server browser sees is incorrect (trying to either join the dedicated servers default IP address (NOT THE SAME IP that the server instance is bound to VIA multihome), or the wrong port). My guess would be that the server correctly binds to the assigned ip from the multihome parameter, however the ip passed to the masterserver list is the system default ip + port, or vice versa (correct port, but passing 7777 as port, instead of correct 7777+serverInstanceID)... The latter would yield a similar result to what i am encountering.



    however removing multihome, and the server works as expected (almost always shows the server in the server list and allows me to join).


    Is this a bug? Server box DOES NOT have a firewall. Or am i missing something? Also not that but incase it maybe related, i am assigning core affinities via the @start /affinity in the bat file.


    Any help or thoughts will be appreciated,
    Bunni-
  2. racquemis

    racquemis New Member

    Messages:
    289
    Likes Received:
    0
    currently multihome is not supported by uberent.its still present but it does not work properly with the instance system uberent made. known "issue"
    why don't you use serverinstance=?

Share This Page