Squid has delay pools which will achieve what you are looking for. However I haven't looked into the possibility of using them in an account-less/password-less environment. It might work on a "per IP" basis which would allow you to allocate a particular address range via DHCP which would be bandwidth limited, and apply static IP's elsewhere.
Just a thought. Others have mentioned traffic shaping and QoS etc which operate directly on the IP stack. YMMV. Cheers, James > -----Original Message----- > From: savanna [mailto:[EMAIL PROTECTED]] > Sent: Monday, 13 January 2003 10:16 PM > To: [EMAIL PROTECTED] > Subject: [SLUG] *limiting* bandwidth? > > > I'm in an interesting situation - I actually want to slow > down my network > connection, as our users are sucking down too much stuff. Any ideas or > pointers or tools to look for? > > The situation is that I've got a Debian server connected to an ADSL > connection, with a whole lot of workstations in a 'kiosk' > situation - ie no > logons. So whilst I could make my Squid server transparent, > require passwords, > and have some sort of quota system, this wouldn't be good as > I don't want > passwords. > > What I'd like to do is limit each workstation connection > speed to say modem > speed, but not have that affect other users. And of course do > it via open > source, not using Cisco, etc. > > Ideas, anyone? > > -- > Savanna | Free as in 'free speech', > GnuPG Pub Key E40FAE08 | not 'free beer'. > -- > SLUG - Sydney Linux User's Group - http://slug.org.au/ > More Info: http://lists.slug.org.au/listinfo/slug > > -- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
