Or, C) Use PPPoE :)

PPPoE overcomes all these problems, it also ensures you remove IP traffic
from your client <-> AP wireless link (You tunnel everything over PPP).
Basically, if you use PPP you get to control the entire connection, from the
IP leasing (So the user hasn't gotta configure anything, cept press
Next->Next->Next), dns servers, and netmask. In addition you get all the
logging functionality (if you auth to a radius server). The other (and the
one I imagine you are most interested) is the ability to traffic limit.
Because all traffic *has* to go through the PPP Tunnel, your client can only
receive teh bandwidth you have designated him/her. So if one of the buggers
contracts a nasty strain of MSBLaST, and are paying for a 128/128
connection, then they will only be able to spew traffic out at 128K - no
more, because the rest will get dropped at the NOC's queue. Also, it means
clients can communicate with each other, even when Interlcient communication
is disabled - but only at the bandwidth they are paying for - So no one can
hog all the air bandwidth - Really is a fantastic System :)

Regards

Colin.

----- Original Message -----
From: "Roger Howard" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 10, 2003 5:04 AM
Subject: [smartBridges] sB Network Issue


> One of the problems I seem to be facing frequently these days is that a
> single customer can get a virus and generate tremendous amounts of
traffic,
> which brings the whole network to a crawl. Normally bandwidth shaping at
the
> NOC will limit the amount the customer can transmit, due to the
Transmission
> Control Protocol part of TCP/IP. But if it is something like the
Nachi.worm
> it is ping packets which do not have transmission control and can be
spewed
> out at tremendous rates that no bandwidth shaper can control. So what's
the
> solution to stop these slowdowns and outages caused by these viruses?
>
> A) Reduce the customer's functionality by insisting they use a router or
> firewall.
> B) Have bandwidth shaping at the CPE.
>
> Personally I prefer B.... but that seems to be expensive, usually.
> Smartbridges, it might be something you can include in your Nexus product?
>
> Thanks,
> Roger
>
> The PART-15.ORG smartBridges Discussion List
> To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe
smartBridges <yournickname>
> To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe
smartBridges)
> Archives: http://archives.part-15.org
>
>



The PART-15.ORG smartBridges Discussion List
To Join: mailto:[EMAIL PROTECTED] (in the body type subscribe smartBridges 
<yournickname>
To Remove: mailto:[EMAIL PROTECTED] (in the body type unsubscribe smartBridges)
Archives: http://archives.part-15.org  

Reply via email to