[mohaa] Copy out of the COD mailing group...
Steven Hartland
killing at barrysworld.com
Mon Dec 15 14:45:37 EST 2003
As explained on the cod list there is nothing that can be done to fix this short of a fix
for the client / server. The only other solution is to get a none nated server or to
someone how proxy your connection to the server so that its ip appears
as your external address.
Steve / K
----- Original Message -----
From: Mohaa Admin
To: mohaa at icculus.org
Sent: 13 December 2003 17:24
Subject: [mohaa] Copy out of the COD mailing group...
All, Have to ask Ryan something, but don't know if he is in the COD mailing group. Can you help????
Ryan here my problem i posted in the COD mailing group
---------------------------------- cut -----------------------------------
Hi there all,
I have a simple question. I have a Mohaa Breaktrough server running on my linux box, this server is showing up in gamespy ASE and in the game.
Now i want to run a COD server on the same machine, after i put it up and try to connect from my lan machine to the server i get awaiting cd key authorization. I read on www.codadmin.com that you have to put a redirect in your host file like this
10.5.1.2 codauthorize.activision.com
After i did this it worked like a charm but i am not showing up in either ASE or Gamespy or inside the game. Now i read on this forum that when you block this Actvision is blocking you on gamespy etc. So i removed it and i can see that i get more connections now in my logfile
SV packet 212.4.59.227:28960 : getinfo
SV packet 217.187.228.176:28960 : getinfo
SV packet 66.171.20.41:28960 : getinfo
SV packet 81.50.168.236:28960 : getinfo
SV packet 213.7.84.188:28960 : getinfo
SV packet 80.130.183.223:28960 : getinfo
SV packet 62.15.142.49:6956 : getinfo
SV packet 62.181.213.155:28960 : getinfo
SV packet 194.255.159.186:-496 : getinfo
SV packet 67.163.174.179:28960 : getinfo
SV packet 80.142.139.40:14529 : getinfo
SV packet 213.89.220.43:-1909 : getinfo
SV packet 80.135.182.47:28960 : getinfo
SV packet 81.189.29.89:28960 : getinfo
And it goes on and on. When i put the block again i only see this 1 or 2 times in 15 minutes.
I also see that the logfile is saying
sending getIpAuthorize for 10.5.1.123:28960
I understand that this won't work becuase this is a private range and Activision can't registrate my CDKEY.
So now my problem.
If i put in the block a can play on my server from the lan, if i remove it i see the CD KEY string.
Please can anybody help me with this?????
Regards
Quint
---------------------------------------------------------------------------------------------
And here the answer of me
All,
--------------------------------------------- cut ---------------------------------------------------
Thanks for al the answers, i thought so that this would be the problem, i only hoped it was easy to fix... Dammed...... Ok let's hope that this will be fixed....;-)
But the about mohaa the AUTH is there because when you have an illegal cd`-key you can't play on my server. So i know there is an AUTH. But i think it works different to the one in COD.
He maybe this would be a solution for the COD AUTH. Ryan if you are also in the mailing group can you answer this and give us a little push in the right direction????
Just to be sure i post this one also in the mohaa mailing group. Ryan if you are in both just give the answer here please???
Gr.
Quint
----- Original Message -----
From: Steven Hartland
To: cod at icculus.org
Sent: Friday, December 12, 2003 18:52
Subject: Re: [cod] Problem with Dedicate COD and lan connection
I dont think you quite follow the problem here Jim its not that the server or the client cant
see the auth server its that when the client connects to the LOCAL server it connects
using its LOCAL address. Now when the server auths the client it sends the details of
the client off to the auth server including the LOCAL client address. Part of the auth
process is the auth server will try to contact the client directly since the address for
the client sent to the auth server from the game server is a LOCAL address this
step fails and the client authentication times out. As I said the only solution to this
would be to have some sort of configuration option in the client that enabled
it to communicate its REMOTE address to the server, that or change how the auth
process works.
Steve
----- Original Message -----
From: James Landi
To: cod at icculus.org
Sent: 12 December 2003 17:34
Subject: RE: [cod] Problem with Dedicate COD and lan connection
Make sure that the box can communicate back to Activision's server(s) via ports 20510, 20500 and the game port of 28960. All ports must be open so you can authenticate your server, report its status to the master server and accept clients to play the game. This is how you show up in the game browser
By blocking the authentication url your not going to show up on any server list and only should be used when playing via private LAN.
IW stated anyone blocking or redirecting this authentication url, will result in your server not being listed on the master server thus you will not show up in any game browser.
Hope this helps
-Jim
Owner Codadmin.com
--------------------------------------------------------------------------
From: Steven Hartland [mailto:killing at barrysworld.com]
Sent: Friday, December 12, 2003 12:25 PM
To: cod at icculus.org
Subject: Re: [cod] Problem with Dedicate COD and lan connection
That's the problem you cant fix it and have it report to the master. The client would need
to be patched to make this work. MOHAA works as it doesn't have authentication.
Steve / K
----- Original Message -----
From: COD System Admin
To: cod at icculus.org
Sent: 12 December 2003 17:01
Subject: Re: [cod] Problem with Dedicate COD and lan connection
Steven,
A question who is them??? i own my own server this server is also my firewall and nat translator. And what do you mean by NAT'ed config option on the client??? Don't you mean my iptables rules???
Please help me because Mohaa works, and this is authenticating me also on EA.....
Regards
Quint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/mohaa/attachments/20031215/dd8d0f26/attachment.htm>
More information about the Mohaa
mailing list