[cod] And with the patch the problem with NAT is back

[Boy_One (COD System Admin)]

Yeah this is great for you, but i don't run a public server. With this you
won't show up in any ingame browser list or ASE/Gamespy. And thats just the
problem. The rule of Activision is no AUTH no listing. So this is not the
answer for me, i already know this trick, but playing alone is not so much
fun...;-)

I need a public server on the internet trough my verry fast internet line at
home, and then connect to it from my private adress space.

Regards
Quint

----- Original Message -----
From: "orr" <orr at cadetmail.uscga.edu>
To: <cod at icculus.org>
Sent: Friday, February 06, 2004 17:10
Subject: RE: [cod] And with the patch the problem with NAT is back


> whoa! that hosts thing worked!  Quint, it might work for you too.  running
> slackware 9.0, here's what I did:
>
> 1.) su over to root (duh)
> 2.) vi /etc/hosts
> 3.) edit "hosts" to contain the following two lines:
> 127.0.0.1 codauthorize.activision.com
> 127.0.0.1 codmaster.activision.com
> 4.)start the server
>
> I connected to my server successfully and then disconnected, though it
took
> longer to connect than it would have to my win2k server cuz it tried to
> authenticate (unsuccessfully!!).  But anyway, here's what the console
said:
> ---------------------
> 0 teams with 0 entities
> -----------------------------------
> Warning: cvar "g_TeamName_Allies" given initial values: "GAME_ALLIES" and
> "MPSCRIPT_AMERICAN"
> Warning: cvar "g_TeamColor_Allies" given initial values: "0.5 0.5 1" and
> ".25 .75 .25"
> Warning: cvar "g_TeamName_Axis" given initial values: "GAME_AXIS" and
> "MPSCRIPT_GERMAN"
> Warning: cvar "g_TeamColor_Axis" given initial values: "1 0.5 0.5" and ".6
> .6 .6"
> Warning: cvar "sv_hostname" given initial values: "CoDHost" and "DO NOT
> JOIN, IM DEBUGGING! =)"
> Warning: cvar "scr_allow_fg42" given initial values: "0" and "1"
> -----------------------------------
> Hitch warning: 11832 msec frame time
> Resolving codauthorize.activision.com
> codauthorize.activision.com resolved to 127.0.0.1:20500
> sending getIpAuthorize for 138.29.36.138:28960
> sending getIpAuthorize for 138.29.36.138:28960
> sending getIpAuthorize for 138.29.36.138:28960
> authorize server timed out
> SVC_DirectConnect ()
> Client 0 connecting with 0 challenge ping from 138.29.36.138:28960
> Going from CS_FREE to CS_CONNECTED for Yimboli (num 4 guid 0)
> Yimboli : dropped gamestate, resending
> SV_SendClientGameState() for Yimboli
> Going from CS_CONNECTED to CS_PRIMED for Yimboli
> Sending 7726 bytes in gamestate to client: 4
> sending getIpAuthorize for 138.29.36.138:28960
> Going from CS_PRIMED to CS_ACTIVE for Yimboli
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Yimboli: Delta request from out of date packet.
> Going to CS_ZOMBIE for
> 4: EXE_DISCONNECTED
> Going from CS_ZOMBIE to CS_FREE for
>
> Extra special thanks to Paul Bowsher for the hint, I couldn't have done it
> without ya!  If you're ever in connecticut on the weekend, i'll buy you a
> drink! (well actually you can buy it and ill reimburse since i dont turn
21
> til november =)
>
> As you can see, since I set the authorize and master sites to 127.0.0.1 in
> the hosts file, /etc/hosts, it could not authorize.  hope this helps!!!
>
> -Tim
>
>
>
> -----Original Message-----
> From: cod at kaleplek.net [mailto:cod at kaleplek.net]
> Sent: Friday, February 06, 2004 9:39 AM
> To: cod at icculus.org
> Subject: RE: [cod] And with the patch the problem with NAT is back
>
>
> Hi Tim,
>
> I don't know i'm figuring out which cvars are new in 1.2 in the hope that
> there is a setting for it, but no luck at this moment. And i don't get any
> input from this mailing list also because this is still a problem and
> nobody knows how to fix it.
>
> I saw that there is an CoD programmer here active and i'm watching every
> day now in the hope he reads my questions and answer them. But still no
> luck so i have to be patience.... :-(
>
> Greetz
> Quint
>
>
> > I have the exact same problem there, shipmate.  Except i never even got
> > it to work for 1.1 and gave up... i figured patching to 1.2 would fix
> > it. That's not the case, eh?  How do I get my LAN server to stop
> > checking for a cd key (yes, i AM flagging +set dedicated 1)
> >
> > Thx
> >
> > -Tim
> >   -----Original Message-----
> >   From: Boy_One (COD System Admin) [mailto:cod at kaleplek.net]
> >   Sent: Saturday, January 31, 2004 7:08 PM
> >   To: cod at icculus.org
> >   Subject: [cod] And with the patch the problem with NAT is back
> >
> >
> >   Hi all,
> >
> >
> >
> >   I posted this before and with your help i got it working to log on to
> > my
> > own server. But now with the patch installed the problem is back. For
> > you who doesn't know my problem a little info.
> >
> >
> >
> >   I have a server running on my linux machine at home. This machine also
> > gives me NAT to the internet. Now when i try to connect to it from
> > inside my LAN he tries to AUTH me by activision with my internal network
> > address.
> >
> >
> >
> >   Before the patch he timed out and let me in. But now with the new
> > patch it
> > is starting allover again. I know somebody said this was put on a list
> > to look at and maybe solve it. Is this done so and if the answer is yes,
> >  is there a cvar i have to set to let me connect to my server again. Or
> > is my nightmare back... :-( I hope not. Who can help me...
> >
> >
> >
> >   Regards
> >
> >   Quint
>
>
>
>
>