Thanks! Adding the filter to the root was the trick. From the various documentation I was reading I had the impression that the filter needed to be added to the sub-classes - 1:1 and so forth. I presume that's only appropriate when you have leaves below 1:1.
Anyhow, the trick now is figuring out how I want to configure things with two of these bridges in mind. The topology would look like this:
Switch-bridge/filter-WAN router--Remote WAN router-bridge-remote switch
Now with 1.5Mbit/s with the potential for 2mbit/s I was thinking of limiting each bridge at 1Mbit/s. I didn't want to limit at 750kbit/s because if you're doing a big file transfer, you're going to suffer and besides, the ratio of download to upload is in favour of the download The streaming audio devices are set up for 128kbit/s MPEG-layer3. So we're looking at dedicating a minimum of 150kbit/s which can double or more if I'm having congestion problems.
Now here's an interesting idea. Let me know if it's possible or not. Is it possible for me to create a bridge between the two linux boxes so it physically looks like
eth0 eth1 --WAN-- eth1 eth0
but virtually you are going
eth0 ------- eth0
The reason I ask this is so I can create an awareness between the two bridges as to how much traffic is actually going through the pipe so I may optimize it to its fullest.
I suppose that it could be done via snmp or spanning-tree?
I don't know if that will work - if you can shape on both ends just do egress shaping on the WAN facing interfaces. You'll need to back off a bit to allow for link overheads, but it will be alot nicer than doing it all from one end.
Andy. _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
