[cod] More Browser List pains

Sat Apr 3 08:53:20 EST 2004

That seems much more plausible to me than suspecting a network
issue. Packet problems, whether fragmented or just lost, would be
much more random than we are seeing.

> What I think is happening is that the server is timing out.  It does
> it
> randomly.  There is never the correct amount of servers in the list
> because
> it just drops them.  It starts to load, hangs. Times out.  And drops
> the
> rest.  It is not a network problem, it is a database problem.
> However IW
> doesn't see it.
>
>
> ----------------------------------
> Waiting on the pier 'till Charon comes....
> -----Original Message-----
> From: theo [mailto:theo at dsl-only.net]
> Sent: Friday, April 02, 2004 7:35 PM
> To: cod at icculus.org
> Subject: RE: [cod] More Browser List pains
>
> What are the odds then that I am missing the same packets every
> time, the
> packet(s) containing the info with my server listing? That seems
> very
> suspect.
>
> -----Original Message-----
> From: Bryan Kuhn [mailto:bryan at infinityward.com]
> Sent: Friday, April 02, 2004 11:25 AM
> To: cod at icculus.org
> Subject: Re: [cod] More Browser List pains
>
> It doesn't fragment packets, it just sends about 30 separate packets
> so you
> might happen to miss one.
>
> Friday, April 2, 2004, 11:21:37 AM, you wrote:
>> It is probably because the Master Server sends fragmented packets
>> and
> your
>> firewall blocks them and times out downloading the list.  IW has
> stated that
>> this will be fixed in 1.4 which will be released sometime between
>> now
> and
>> the next millennium.
>
>> John Kennington
>> Assistant Director - Operations
>> BuzzCard Center
>> Georgia Institute of Technology
>> 350 Ferst Dr. NW
>> Houston Bookstore Mall
>> Atlanta, GA  30332
>> 404-385-2961
>> 678-283-3385 Cell
>> 404-894-2049 FAX
>> http://www.buzzcard.gatech.edu/
>> BuzzCard FAQs:  http://www.buzzcard.gatech.edu/faqs/index.htm
>> -----Original Message-----
>> From: theo [mailto:theo at dsl-only.net]
>> Sent: Friday, April 02, 2004 2:16 PM
>> To: cod at icculus.org
>> Subject: RE: [cod] More Browser List pains
>
>> http://63.105.18.229/images/cod.JPG
>
>> Bah! I know most 'serious' players use ASE or GS, but there are
>> thousands of others that don't, like me :) Besides, it *should be
> there,
>> so I want to figure out why its not.
>
>> kp
>
>> -----Original Message-----
>> From: Bryan Kuhn [mailto:bryan at infinityward.com]
>> Sent: Friday, April 02, 2004 10:53 AM
>> To: cod at icculus.org
>> Subject: Re: [cod] More Browser List pains
>
>> shows for me
>> http://inherent.infinityward.com/files/shot0001.jpg
>
>
>> Friday, April 2, 2004, 10:41:31 AM, you wrote:
>>> Locally there is nothing to stop it, there is only the most
>> rudimentary
>>> of firewalls. The network admin said he can help me on Monday
>>> though
>> he
>>> has made no changes to the firewall policy. He will see if there
>>> are
>> any
>>> packets being dropped. This is from the availability page:
>>>
>>
> http://inherent.infinityward.com/index.php?ip=216.183.109.45&port=20110
>
>>> If this server is showing in anyone else's list I'd like to know.
>>> The
>>> server name is 'Linux-fixed PDX.LLC'
>
>>> kp
>
>>> -----Original Message-----
>>> From: Bryan Kuhn [mailto:bryan at infinityward.com]
>>> Sent: Thursday, April 01, 2004 11:47 PM
>>> To: cod at icculus.org
>>> Subject: Re: [cod] More Browser List pains
>
>>> There are no know listing bugs, and you no longer have to shut
>>> your
>>> server down for awhile with 1.3. Do you have firewall logs?
>
>>> Thursday, April 1, 2004, 11:29:57 PM, you wrote:
>>>> I have no browser list either. What a load of crap. I'm glad
>>>> there
> is
>>> a
>>>> Linux server, but this is almost more trouble than its worth. It
>>>> was
>>>> never a problem. All necessary ports are open. Stopped my server
>>>> for
>>>> four hours and restarted. IP=216.183.109.45:20110 I'm about
>>>> ready to
>>>> just close down the damn thing. That whole problem with the
>>>> weapons
>>> was
>>>> a total joke, how much testing was done there? I'm sorry, but
>>> validation
>>>> is where it's at and that was a joke. Bryan and all, I applaud
>>>> your
>>>> efforts, really- but how much work do we need to do?
>>>> kp
>
>
>
>>>> ---
>>>> Outgoing mail is certified Virus Free.
>>>> Checked by AVG anti-virus system (http://www.grisoft.com).
>>>> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>
>>> ---
>>> Incoming mail is certified Virus Free.
>>> Checked by AVG anti-virus system (http://www.grisoft.com).
>>> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>>> ---
>>> Outgoing mail is certified Virus Free.
>>> Checked by AVG anti-virus system (http://www.grisoft.com).
>>> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>
>> ---
>> Incoming mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>> ---
>> Outgoing mail is certified Virus Free.
>> Checked by AVG anti-virus system (http://www.grisoft.com).
>> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.638 / Virus Database: 409 - Release Date: 3/21/2004
>
>
>