[cod] Local client auth via NAT ( possible solution )

[Boy_One (COD System Admin)]

Hi there all,



Thanks for all the mail about this topic, it pushed me in a couple of
directions who where looking fine in theory, but still no luck.

Here a little update. I tried to install a proxy or portfwd or like below
yet no luck, i found out something else with this debugging, Steve was right
all along, it is the client who gives the ip-adres, only when i go through
nat it is transferred to the external ip. So it looks like that the server
has to translate/spoof the private address to a public address. Does anyone
know a tool who can do this or is Activision in this mailing group and can
answer this question???? It would help because i'm spending more time to get
myself on the gameserver rather than to having fun of it...:-(



Another solution for me is that my internal address is not checked at all by
activision auth, but just accepted... (and yes i have a legal cd-key)



Please Please help me out with this problem.... I can't believe that Mohaa
and other Server are working fine and only Call of Duty has this problem.



Thanks for all the help so far.



Regards

Quint





----- Original Message -----
From: "Steven Hartland" <killing at barrysworld.com>
To: <cod at icculus.org>
Sent: Thursday, December 18, 2003 12:17
Subject: [cod] Local client auth via NAT ( possible solution )


> Had a flash of insperation this morning I think the following might just
> work.
>
> If we have this picture:
> NAT box: internal 10.10.10.1, external 1.1.1.1
> Server: internal 10.10.10.2
> Client: internal 10.10.10.3
>
> If we change this to:
> NAT box: internal 10.10.10.1, external 1.1.1.1
> Server: internal 10.10.10.2, fake 1.1.1.2 (alias)
> Client: internal 10.10.10.3, fake 1.1.1.1 (alias)
>
> And then force the client to connect to the server on 1.1.1.2 the ip
reported
> in the packet sent to the master will be the ip of the NAT (1.1.1.1) and
hence
> if port forwarding is setup correctly the auth packet will be forwarded
> to the client on 10.10.10.3 and it will all just work.
>
> Adding the 1.1.1.X aliases to the internal machines wont affect
conectivity
> as they have no routes to the outside world so all external connectivity
> will be done via the NAT'ed addresses.
>
> I cant test this here as I dont have NAT but Im pretty confident it will
work.
>
>     Steve / K
>