I dunno about that. We set up a nice little ole Quake server on one side
of a Catalyst 5500 and put 6 24 port 10BT cards in it, and then stuck the
quake server on a 100BTX card, and it worked fine... we had roughly
80 machines playing quake simultaneously and there was still no lag.. but
I got reports that that Cat5500 was pretty darn hot.....
;-) The things you will do in your spare time @ a trade show are amazing.
Auf Wiedersehn,
+----Daniel "Cheez" Brown------------Global Data Systems-------+
| http://cheez.lowprofile.net | Security Advisor, Global Reach |
| cheez @
cheez .
lowprofile .
net | Computer Networking Specialist |
| cheez @
globalreach .
net | Remote Management Specialist |
| cheez @
hotmail .
com | Linux/Windows NT Specialist |
+------If at first you don't succeed, redefine success.--------+
On Thu, 30 Oct 1997, Andrew Reardon wrote:
Date: Thu, 30 Oct 1997 10:01:27 +1000
From: Andrew Reardon <areardon @
citec .
qld .
gov .
au>
To: Chris Pugrud <ChrisP @
steldyn .
com>,
"'no @
obituary .
margo .
org'" <no @
obituary .
margo .
org>,
"'ygerman @
genre .
com'" <ygerman @
genre .
com>
Cc: Firewalls Mailing list <firewalls @
GreatCircle .
COM>
Subject: Re: [Off-topic] Newbie Question - Can Quake melt your network?
Chris Pugrud wrote:
>
[Stuff about M$ Exchange snippaged]
>
> 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)
Plus SGI (need an O2 at least), OS/2, and soon DEC Alpha.
> 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.
Yes, that would certainly make an great stress test.
For extra stress, don't forget about the "bots" that are available.
These are software players written by Quake enthusiasts. The premier
bot at the moment would have to be the ReaperBot. It was written by
a guy who does router firmware, or something, and has considerable smarts
(both the author AND the bot :).
Fire up a few of these on the server, at their highest skill level,
and watch the packets fly. 32 of these guys screaming around a level
would come close to red-lining the quake engine.
If you do this on the server, just go and, as Chris says above, connect
clients to the server's game. They'll die pretty much instantly, but from
then on they can just sit there and still recieve all updates as usual
( a "dead" player is just a player who is montionless, on his back/side,
but can still move his/her head to look around, and still sees the action).
Another reason it makes for a great stress test is that, if you use the
QuakeWorld port of Quake (basically Quake tweaked for play over TCP/IP, plus
other gameplay enhancements), then the server maintains some good stats
about data transmissions, cpu usage, etc. These are available at any time
by executing the stats command. Clients can also execute the
net_stats command to display that client's internal networking counters.
Plus, clients can at any time execute the r_netgraph 1 command, and get a
real-time (!) graph of their packet loss, delta compression errors, tx/rx
rate, etc,
in a neat little display on the bottom right of their playing screen.
> I may have to go do this this weekend. See if I can melt that new Cisco
> switch...
If it don't melt, wait for Quake II. :) It promises >x (where x is a large
number much greater than 32) clients per server.
> 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
References:
|
|
