My first guess would be vlans being a problem. I know at least for
class based queuing disciplines on vlans, you have to take care to
define filters that funnel traffic through a class by selecting
802.1q traffic on the real interface, not the vlan interface.
I know traffic shaping does
not be held long
enough in the tbf and had to be droppd, correct?
Thank you,
sting
--
Bryan Schenker
Director
ResTech Services
www.restechservices.net
608-663-3868
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi
list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
--
Bryan Schenker
Director
ResTech Services
www.restechservices.net
608-663-3868
___
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin
To limit bandwidth to your 192.168.10.11 host, you need to be rate
limiting on the eth0 interface not the eth1 interface if I understand
how your router is plugged in.
tc limits bandwidth leaving an interface. So right now as the rules
are written, you are limiting to 500kbit the
