[cod] Waiting for CDKey Authentication [EXE_AWATINGCDKEYAUTH] never stop

[Daniel Rudolph]

Steven Hartland schrieb:

> That's NOT a solution as it will just mean ur server gets banned from the
> master lists ( no authing server ).
> 
> I suggest someone seeing the problem gets out tcpdump and does a
> full trace. 
You read the part that it is only a problem for me but not for the must 
users ?

 >I must be something to do with either:
> 1. DNS
> 2. routing
> 3. ip config

Well here we go.

1.
 >dig codauthorize.activision.com
; <<>> DiG 9.2.1 <<>> codauthorize.activision.com
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17491
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;codauthorize.activision.com.   IN      A

;; ANSWER SECTION:
codauthorize.activision.com. 895 IN     CNAME   cod01.activision.com.
cod01.activision.com.   894     IN      A       63.146.124.59

I see that my windows machine also requests the ips for cod02 .... but 
the linux server dont do (saw it in tcpdump for windows)

2. routing
the servers i want to join dont have an special setup and well i setup 
them myself *G*


pure server setup
 >ip route
62.4.70.0/24 dev eth0  proto kernel  scope link  src 62.4.70.138
default via 62.4.70.129 dev eth0

Well you dont want to see my server config here. As i said 2 external 
ips Snat,...

You can see in tcpdump and cod log that all should be fine.

important part for cod:

codauthorize.activision.com resolved to 63.146.124.59:20500
sending getIpAuthorize for 141.30.225.46:28960
SV packet 24.10.47.97:28960 : getinfo
SV packet 80.36.58.80:28960 : getinfo
SV packet 63.146.124.59:20500 : ipAuthorize
SV packet 141.30.225.46:28960 : getchallenge
sending getIpAuthorize for 141.30.225.46:28960

and so on never finish.
and 141.30.225.46 is my external ip. My internal is different but SNAT 
is working so it shows the correct ip. So i can show you also on tcpdump.

Remote Interface:
 >tcpdump -i eth0 -n udp
tcpdump: listening on eth0
Nov 26 19:20:27 server kernel: device eth0 entered promiscuous mode
19:20:35.001242 141.30.225.46.4264 > 62.4.70.138.8890:  udp 15
19:20:35.024954 62.4.70.138.8890 > 141.30.225.46.4264:  udp 931 (DF)
19:20:42.508549 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:42.785138 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)
19:20:45.979213 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:46.205737 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)
19:20:48.987663 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:49.226714 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)
19:20:51.996920 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:52.246421 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)
19:20:55.007768 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:55.226436 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)
19:20:58.007020 141.30.225.46.28960 > 62.4.70.138.8890:  udp 16
19:20:58.226875 62.4.70.138.8890 > 141.30.225.46.28960:  udp 13 (DF)

local interface:
19:22:02.199781 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:02.199853 172.16.16.13.28960 > 62.4.70.138.8890:  udp 16
19:22:02.457465 62.4.70.138.8890 > 172.16.16.13.28960:  udp 13 (DF)
19:22:02.459092 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:03.765581 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:03.765655 172.16.16.13.28960 > 62.4.70.138.8890:  udp 16
19:22:03.977695 62.4.70.138.8890 > 172.16.16.13.28960:  udp 13 (DF)
19:22:03.989001 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:06.775410 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:06.775483 172.16.16.13.28960 > 62.4.70.138.8890:  udp 16
19:22:06.998592 62.4.70.138.8890 > 172.16.16.13.28960:  udp 13 (DF)
19:22:06.999796 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:09.774657 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:09.774731 172.16.16.13.28960 > 62.4.70.138.8890:  udp 16
19:22:09.978957 62.4.70.138.8890 > 172.16.16.13.28960:  udp 13 (DF)
19:22:09.987296 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38
19:22:12.785555 172.16.16.13.28960 > 63.146.124.59.20500:  udp 38

(you can also see the dns requests here)

19:23:31.470200 172.16.16.13.4288 > 172.16.16.1.53:  915+ A? 
au2cod2.activision.com. (40)
19:23:31.471053 172.16.16.1.53 > 172.16.16.13.4288:  915 NXDomain 0/1/0 
(88) (DF)
19:23:31.473558 172.16.16.13.4288 > 172.16.16.1.53:  916+[|domain]
19:23:31.474316 172.16.16.1.53 > 172.16.16.13.4288:  916 NXDomain* 0/1/0 
(136) (DF)
19:23:31.486447 172.16.16.13.4288 > 172.16.16.1.53:  917+[|domain]
19:23:31.487175 172.16.16.1.53 > 172.16.16.13.4288:  917 NXDomain 0/1/0 
(112) (DF)
19:23:31.492556 172.16.16.13.4289 > 172.16.16.1.53:  918+ A? 
au2cod3.activision.com. (40)
19:23:31.493344 172.16.16.1.53 > 172.16.16.13.4289:  918 NXDomain 0/1/0 
(88) (DF)
19:23:31.496242 172.16.16.13.4289 > 172.16.16.1.53:  919+[|domain]
19:23:31.496994 172.16.16.1.53 > 172.16.16.13.4289:  919 NXDomain* 0/1/0 
(136) (DF)
19:23:31.498958 172.16.16.13.4289 > 172.16.16.1.53:  920+[|domain]
19:23:31.499685 172.16.16.1.53 > 172.16.16.13.4289:  920 NXDomain 0/1/0 
(112) (DF)
19:23:31.506072 172.16.16.13.4290 > 172.16.16.1.53:  921+ A? 
au2cod4.activision.com. (40)
19:23:31.506866 172.16.16.1.53 > 172.16.16.13.4290:  921 NXDomain 0/1/0 
(88) (DF)
19:23:31.508868 172.16.16.13.4290 > 172.16.16.1.53:  922+[|domain]
19:23:31.509619 172.16.16.1.53 > 172.16.16.13.4290:  922 NXDomain* 0/1/0 
(136) (DF)
19:23:31.512808 172.16.16.13.4290 > 172.16.16.1.53:  923+[|domain]
19:23:31.513534 172.16.16.1.53 > 172.16.16.13.4290:  923 NXDomain 0/1/0 
(112) (DF)
19:23:31.520490 172.16.16.13.4291 > 172.16.16.1.53:  924+ A? 
au2cod5.activision.com. (40)
19:23:31.521279 172.16.16.1.53 > 172.16.16.13.4291:  924 NXDomain 0/1/0 
(88) (DF)
19:23:31.523297 172.16.16.13.4291 > 172.16.16.1.53:  925+[|domain]
19:23:31.524050 172.16.16.1.53 > 172.16.16.13.4291:  925 NXDomain* 0/1/0 
(136) (DF)
19:23:31.527341 172.16.16.13.4291 > 172.16.16.1.53:  926+[|domain]
19:23:31.528066 172.16.16.1.53 > 172.16.16.13.4291:  926 NXDomain 0/1/0 
(112) (DF)
19:23:31.531185 172.16.16.13.28960 > 63.146.124.59.28960:  udp 34
19:23:31.534562 172.16.16.13.4292 > 172.16.16.1.53:  927+ A? 
codmotd.activision.com. (40)
19:23:31.535399 172.16.16.1.53 > 172.16.16.13.4292:  927 NXDomain 0/1/0 
(88) (DF)
19:23:31.538693 172.16.16.13.4292 > 172.16.16.1.53:  928+[|domain]
19:23:31.539446 172.16.16.1.53 > 172.16.16.13.4292:  928 NXDomain* 0/1/0 
(136) (DF)
19:23:31.542288 172.16.16.13.4292 > 172.16.16.1.53:  929+[|domain]
19:23:31.543013 172.16.16.1.53 > 172.16.16.13.4292:  929 NXDomain 0/1/0 
(112) (DF)



3. Routing
well i think its visible that it is ok

>     Steve / K
Daniel