All,
Chris is correct, the bandwidth is "backwards" for asymmetrical. The
engineers are trying to redesign that to work better.
This other issue, which appears to imply that the throttling does not work
properly, I have forwarded to engineering with a tracker to have them look
into.
I do know that in previous versions of our software this feature worked!
Kevin
-----Original Message-----
From: karlnet-bounces@WISPNotes.com
[mailto:karlnet-bounces@WISPNotes.com]On Behalf Of Chris Conn
Sent: Thursday, April 10, 2003 8:06 AM
To: Karlnet Mailing List
Subject: Re: [Karlnet] limiting bandwidth
Norm Young wrote:
> I've never been able to get that to work. In practice, what I've seen is
> that in setting the speed on the two interfaces for say, an asymmetrical
> connection like 256/128kbps, results in both interfaces set to 128k.
Thus,
> so far, what I've seen is that you can bw limit with Karlnet, but only as
> long as you want symmetrical. For anything else, I use Mikrotik.
>
> Norm
Hello,
This is close to what I have observed. However, I have found that if you
set
the Ethernet to a lower rate than the 802.11b interface, you will in effect
be
asymmetrical, however in the wrong direction for most "desired" asymmetrical
applications.
Note that throughput-limiting methods are quite difficult to implement
without
causing packet (and therefore application) loss. The fact you can limit
inbound traffic with Turbocell is the difficult part of the process. I
sincerely hope that someday the issue will be addressed to resolve the
upstream
limitation methods, which in theory are less difficult to implement.
Chris
_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet
|