Date: Sat, 2 Apr 2005 12:34:03 +0000 From: Marcin Jessa <lists@yazzy.org> To: Sten Daniel =?ISO-8859-1?Q?S=F8rsdal?= <lists@wm-access.no> Cc: freebsd-isp@freebsd.org Subject: Re: radius client parameters Message-ID: <20050402123403.493da87a.lists@yazzy.org> In-Reply-To: <424D206A.4050007@wm-access.no> References: <200503311104.57782.bikrant_ml@wlink.com.np> <05af01c535b8$b4a51720$42764eca@ilo.skyinet.net> <20050331130213.656c4b88@dev.lan.Awfulhak.org> <20050331154150.05ccb738.lists@yazzy.org> <424D206A.4050007@wm-access.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 01 Apr 2005 12:20:26 +0200 Sten Daniel S=F8rsdal <lists@wm-access.no> wrote: =20 > Why cant you use the sh scripts i wrote It's an ugly hack.=20 With it you have no way to access the userdatabase in the radius server and= set queuing based on the info in it. AFAIR user and bandwith info is stored in flat text files and parsed by the= shell scripts. One can ofcourse code something to make your life easier, e.g a parser conn= ecting to a database and then altering the ALTQ/DUMMYNET rules based on the= info fetched from it, just as the shell scripts do. =20 > Hacking in tx/rx data rate limitation would mean adding queueing to ppp, > which IMHO would be cool but unnecessary. Especially with ALTQ and > Dummynet around. RouterOS ppp only adds dynamic queues (somewhat like > ALTQ) so they do not have queueing inside ppp. I bet Star-OS does the sam= e. >=20 > Perhaps someone would be generous with their time and adds fine-grained > /dev/altq locking support enabling the altq command line utility. >=20 I think my solution described above should be able to fix the obsticles. =20 Regards, M. Jessa http://www.yazzy.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050402123403.493da87a.lists>