This should only be difficult if your policy is based upon a allow all and
deny few perspective, if the reverse is the case; deny all, allow few,
then unless the quake ports match something else specificully allowed you
have no real problems other then folks trying to setup an internal quake
server on the inside <smile>.
Thanks,
Ron DuFresne
On Fri, 9 Jun 2000, Tony Driscoll wrote:
> Hi all,
> As a roundabout from yesterday's thread regarding Quake Arena: anyone know of a
>decent way to PREVENT internal users from connecting to public Quake Arena servers
>using ACL's or otherwise? I know little about the game itself other than the fact
>that consultants shouldn't be using our T3 for head-to-head play with their virtual
>buddies on the weekends! :-)
> It appears that the server port number can be random like most things from what I've
>been reading making it possibly more challenging to lock down outgoing traffic?
>
>
> TIA
> Tony Driscoll
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
***testing, only testing, and damn good at it too!***
OK, so you're a Ph.D. Just don't touch anything.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
