SV: [bf1942] Christmas build.

thµnder thunder at momsquad.net
Thu Dec 26 15:39:43 EST 2002


Thnx i can see it now in gamebrowser
Allthough it shows gamespy: trying to bind to 192.168.1.101, port 23000. now

-----Ursprungligt meddelande-----
Från: Kevin J. Anderson [mailto:lestat at counter-strike.net] 
Skickat: Thursday, December 26, 2002 21:34
Till: bf1942 at icculus.org
Ämne: RE: [bf1942] Christmas build.

plug your internal ip into the ServerSettings.con and it will take care of
it.

->-----Original Message-----
->From: thµnder [mailto:thunder at momsquad.net]
->Sent: Thursday, December 26, 2002 3:28 PM
->To: bf1942 at icculus.org
->Subject: SV: [bf1942] Christmas build.
->
->
->Same here "gamespy: trying to bind to 255.255.255.255, port 23000"
->Im running from behind firewall/NAT and my local ip is 192.168.1.101
->All other betas worked fine, no troubles of any similar kind
->
->Running on slack 8.1
->
->
->-----Ursprungligt meddelande-----
->Från: Pimp Jr. (Niels van Rooij) [mailto:pimpjr at planetpacs.com]
->Skickat: Thursday, December 26, 2002 12:52
->Till: bf1942 at icculus.org
->Ämne: Re: [bf1942] Christmas build.
->
->When starting now I see the following message:
->
->gamespy: trying to bind to 255.255.255.255, port 23000.
->
->The server no longer shows up in ASE. When I add the server
->manually in ASE
->it shows up as unavailable (ping 9999). I can't find it in the in-game
->browser either - not much of an improvement for me unfortunately. I can't
->test it with gamespy because I refuse to install it ;) I can
->connect to the
->server however.
->
->(Running Debian 3.0 btw)
->
->Niels
->
->> This one should fix GameSpy binding to 0.0.0.0 instead of the correct
->> network interface, though, so if this has been a showstopper,
->please test
->> again.
->




More information about the Bf1942 mailing list