IPCHAINS does not do any shaping what so ever.... Might be good for future
implementations but at this moment it doesn't as it's a pure
firewall/router/whatevaelse....
There might be a possibility of running two fake devices like SL0 and SL1
(serial link like how DIALD works) and run shaper on each of those links .ie
SL0 used for telnet as a max B/W of 3KB and SL1 for everythign else has a
max bandwidth of 3KB.
The use IPchains to router forward requests through those devices depending
on the port forwarded, telnet (23) goes through SL0, etc.. etc...
Would this be a possiblity? I know it's messy but it's cheap and might even
_work_!
I tried this wort of method but with ethernet aliases like ETH0:1 and shaper
won't work with aliases... of course ( sorry, but I was desperate at the
time to a quick solution).
thanks,
George Vieira
Network Administrator
Citadel Computer Systems P/L
http://www.citadelcomputer.com.au
-----Original Message-----
From: DaZZa [mailto:[EMAIL PROTECTED]]
Sent: Thursday, 13 July 2000 8:42 PM
To: Jill Rowling
Cc: '[EMAIL PROTECTED]'
Subject: RE: [SLUG] Priority of network traffic
On Thu, 13 Jul 2000, Jill Rowling wrote:
> It occurs to me that if you run in.telnetd at a higher priority than
normal
> (when called up by inetd for example) then all the telnet sessions should
> get a better look in.
> man nice(1).
That prioritises the _process_, not the link. The link can still be
flooded regardless of the priority of the process on the remote machine.
What he needs is some form of traffic shaping. I know how to do it with
Cisco routers, but not with IPChains. :)
DaZZa
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://slug.org.au/lists/listinfo/slug
