Microsoft, in one of their recent ad campaigns suggested that using one
of their server products ( I think Exchange, but I can't find the ad at
the moment) would reduce stress and allow the network administrator to
have more time to play Quake without interruption.
Obviously Microsoft feels that playing quake is good for the long term
sanity and health of your administrator and consequentially your
network. You just need to show this ad to your boss and they should
understand that Microsoft recommends that network administrators not be
deprived of quake time and that should clear it for you. If you boss
does not believe Microsoft then it is time for them to attend another
Microsoft Customer Re-Education Session.
In vague seriousness, given Quake's amazing abilities to hog processor
and bandwidth, it can be a good stress test on a network. Start up a
quakeworld server on that big manly server of yours (it runs on NT, 95,
Sun, and Linux to date - unfortunately single threaded though) and go
start clients on high end machines across your network (up to 32 clients
per server). Nobody actually needs to play Quake (so there is little
danger that somebody may have fun on the job) for it to start sucking
down all available resources.
I may have to go do this this weekend. See if I can melt that new Cisco
switch...
Chris
--- For your convenience this message is fully buzzword compliant
>-----Original Message-----
>From: citecajr @
citec .
qld .
gov .
au [SMTP:citecajr @
citec .
qld .
gov .
au]
>Sent: Tuesday, October 28, 1997 4:30 PM
>To: no @
obituary .
margo .
org
>Cc: Firewalls Mailing list
>Subject: Re: Newbie Question
>
>
>Quake's network engine uses UDP.
>Many firewalls block UDP altogether.
>Those that don't block it often don't allow the packets to
>flow thru anyway - the firewall processes them (eg DNS queries),
>and discards them.
>
>As for the rest of the question... I am actually having
>difficulty convincing management the working during Quake-time
>is a good idea :))
>
>>
>> It does not make sense that someone would block the quake server port
>> unless they are doing it on purpose. Quake uses ports above 1024 which are
>> not firewalled usually, as that they are used by web browsers and ftp
>> clients. Quake servers run on port 27500. Although, that port can be
>> changed. Some run on 27666 or something else in the 27xxx range. I do not
>> see how they can block all of these ports and still allow web browsing and
>> File transfers on the internet with out problems. I would check to make
>> sure they allow internet connections from your desktop period.
>>
>>
>> Natambu Obleton
>> Email:no @
margo .
org
>> WWW:www.margo.org
>>
>> On Tue, 28 Oct 1997 ygerman @
genre .
com wrote:
>>
>> >
>> > The Firewall works with services and ports. More then likely Quake server
>> > works on a port that is not defined by the firewall administrator. There
>>is
>> > no way to get around it from your work location accept by convincing your
>> > firewall administrator that playing Quake during working hours is a good
>> > thing [a bit of sarcasm there].
>> >
>> >
>> > From: XXxFeaRxXx @
aol .
com
>> >
>> > hi, im a new subscriber and i have a few simple questions...first, how is
>> > it
>> > that a firewall can stop you from connecting to a Quake server and
>> > ..say...a
>> > microsoft ils
>> > server but nothing else...and why would one do this...and is there any
>>way
>> > around it? Any input would be helpful. :)
>> >
>
>_________________________________________________________________
>Andrew Reardon Phone: 61 07 3227 6970
>UNIX Support Specialist Fax: 61 07 3227 2132
>CITEC, Brisbane Qld Oz areardon @
citec .
qld .
gov .
au
Follow-Ups:
|
|
