Date: Fri, 6 Jun 1997 11:55:34 +0200 (MET DST) From: Luigi Rizzo <luigi@labinfo.iet.unipi.it> To: manar@ivision.co.uk (Manar Hussain) Cc: freebsd-isp@FreeBSD.ORG Subject: Re: ETinc's Bandwidth limiter Message-ID: <199706060955.LAA01451@labinfo.iet.unipi.it> In-Reply-To: <Pine.GSO.3.93.970605115357.25125g-100000@stingray.ivision.co.uk> from "Manar Hussain" at Jun 5, 97 11:54:00 am
next in thread | previous in thread | raw e-mail | index | archive | help
> >Please try ftp.hilink.com.au:/pub/FreeBSD/bandd.tgz and let me know what > >you think. It requires FreeBSD 2.2 with IPFIREWALL IPDIVERT options. > > > >There is no documentation. > > code looks straight forward enough. It doesn't allow for burstability > though ... might not be too hard to add in and it would be nice to be using > something we have the source for rather than a commercial binary ... does bandd (and IPDIVERT) require packets to move to user space and back to the kernel ? In this case you might have quite some load at the node running bandd for your application (1Mb/s). If you are looking for sources, have a look at the dummynet stuff available from my page http://www.iet.unipi.it/~luigi/research.html As it is it works at the interface between TCP and IP, but it should be trivial to move it one layer down (ip <--> device) and add the required filtering options. Since packets do not move to user space (same as for the etinc product) you don't have a significant performance problem. Cheers Luigi -----------------------------+-------------------------------------- Luigi Rizzo | Dip. di Ingegneria dell'Informazione email: luigi@iet.unipi.it | Universita' di Pisa tel: +39-50-568533 | via Diotisalvi 2, 56126 PISA (Italy) fax: +39-50-568522 | http://www.iet.unipi.it/~luigi/ _____________________________|______________________________________
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199706060955.LAA01451>