<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3243" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=563544802-12022008><FONT face="Courier New">I hated these
boxes, but they can do what you want. How they do it will depend on the
version of FortiNet they are using, but in a nutshell, it is controlled by both
the packet shaping module and the firewall module. </FONT></SPAN></DIV>
<DIV><SPAN class=563544802-12022008><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=563544802-12022008><FONT face="Courier New">You will need to
create a firewall policy for your specific machine - if possible, start by
copying the existing global policy as a starting point, otherwise, do your
best. With that new policy created, select packet shaping (I think, it
might be traffic shaping...) and make adjustments for the bandwidth (measure
your bandwidth with the system set to bypass, and then set it to a high multiple
of that).</FONT></SPAN></DIV>
<DIV><SPAN class=563544802-12022008><FONT
face="Courier New"></FONT></SPAN> </DIV>
<DIV><SPAN class=563544802-12022008><FONT face="Courier New">Good luck (you will
need it!)</FONT></SPAN></DIV>
<DIV><FONT face="Courier New"></FONT> </DIV><FONT size=2><FONT
face="Courier New">
<DIV>
<HR>
</DIV>
<DIV>Steven Santos<BR>Director, Simply Circus, Inc.<BR>Email:
Steven@SimplyCircus.com<BR> Mail: 14 Pierrepont
Road<BR> Newton, MA 02462<BR>Phone:
617-527-0667<BR> Web: <A
href="http://www.simplycircus.com/">www.SimplyCircus.com</A> </DIV>
<DIV></FONT> </FONT></DIV>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> k12osn-bounces@redhat.com
[mailto:k12osn-bounces@redhat.com]<B>On Behalf Of </B>Todd
O'Bryan<BR><B>Sent:</B> Friday, February 08, 2008 7:24 PM<BR><B>To:</B>
Support list for open source software in schools.<BR><B>Subject:</B> [K12OSN]
Experience with a thin client server connection
gettingthrottled?<BR><BR></FONT></DIV>My district has over 90,000 students and
I have the only thin client lab. In my lab we're having a big problem with
network connectivity as connections get lost pretty often, especially when
lots of users are surfing. The network guy came out and saw how bad the
connectivity was when we tried to connect to internet sites like Google,
Yahoo, and CNN. We then tried surfing within the district and discovered there
were no problems. He set us to bypass the filter box, a FortiNet appliance
that filters the whole district, and we had no problems on the internet, so
it's apparently the filter that's slowing things down. Unfortunately, for
obvious reasons, we can't run without a filter. For political reasons too
complicated to go into, we also can't set up an alternate filtering system for
just my lab.<BR><BR>I suspect that other users don't see this problem because
the filter sees an unreasonable amount of traffic coming from what it thinks
is a single computer and throttles the connection. (We also have the remnants
of a November virus outbreak on the network that is flooding everything with
stray packets, so the filter could be busier than it should be. They're still
working on cleaning that up.)<BR><BR>Does anyone have experience with this
kind of thing, with either FortiNet or another filter appliance, where thin
client labs see a performance degradation compared to single-user systems? If
so, did you have any luck solving
it?<BR><BR>Thanks,<BR>Todd<BR></BLOCKQUOTE></BODY></HTML>