[cod] 1.2a patch and connection timeout

[Harry Rietberg]

I enabled developer-mode and noticed this in the console when someone 
couldn't connect:

sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287
sending getIpAuthorize for 153.116.48.34:-14287

Perhaps this will help?

Grtz,

Blutch


Harry Rietberg wrote:
> I have the same problem. After playing a whole day without any 
> problems suddenly players can't connect anymore...
> This is what I try to fix it:
> - restart COD2 server
> - reboot Linux server
> - disable firewall
> - disable/enable Punkbuster
> - /reconnect command in console
> Nothing, players still getting connection timeouts... I gave up... and 
> then... the next day players can connect again!?
>
> Ryan if you need more information let me know....
>
> Grtz,
>
> Blutch
>
> Ryan C. Gordon wrote:
>>
>>> Ryan can you common on this???
>>
>> This has been reported, but we don't have a reliable reproduction 
>> case in-house:
>>
>>   http://bugzilla.icculus.org/show_bug.cgi?id=2655
>>
>> If it was totally working and then for no apparent reason stopped 
>> working, that suggests there's a piece of code that doesn't 
>> gracefully handle not being able to talk to the master server, but I 
>> don't know.
>>
>> I'll almost certainly need to ssh into someone's server to poke 
>> around to fix this one.
>>
>> --ryan.
>>
>>
>
>