/* HINT: Search archives @ http://www.indyramp.com/masq/ before posting! */ On Thu, 20 Jan 2000, Tomas Campos wrote: > starcraft, it works just fine. When one computer on the LAN connects to > battle.net and hosts a game and then another computer on the LAN > connects to battle.net and attempts to join that same game it shows that > there is too much latency and will not permit the second computer to Hi. I just joined this list and read this message on the list archive. This is also something that I've experienced and wanted to share with you and any others what I think the problem is. First, Battle.net sets up a game by keeping track of each of the players' IP addresses and passing those addresses to each new player as he/she joins the game. Since Battle.net only knows about your external IP address, it sees both players as having the same address. When the two players try to talk to each other using that address, the IP Masquerade functions do not know what to with the packets. It may be possible for the code to be "fixed" to work with such a scenario. I've looked at the code but have a hard time following it. It is also possible for Battle.net to be fixed to work with "masqueraded" players. This could be done by Battle.net keeping track of players internal and external IP addresses and passing the internal address when two players share the same external address. -- Michael Best _______________________________________________ Masq maillist - [EMAIL PROTECTED] Admin requests can be handled at http://www.indyramp.com/masq-list/ -- THIS INCLUDES UNSUBSCRIBING! or email to [EMAIL PROTECTED] PLEASE read the HOWTO and search the archives before posting. You can start your search at http://www.indyramp.com/masq/ Please keep general linux/unix/pc/internet questions off the list.
