bridge was configured with "brctl" three NIC was bind to br0 imq and htb was used to control traffic. #modprobe imq numdevs=3 "htb scripts" #iptables -t mangle -A PREROUTING -i br0 -j IMQ --todev 1 #ip link set imq1 up but this can not do the traffic controling. please tell me how can i do _________________________________________________________ Do You Yahoo!? 银行巨头聚会中原 大浪淘‘金’谁将笑傲 http://sweepstakes.yahoo.com/bank_surveywave2/
On Thu, Jul 04, 2002 at 04:00:22PM +0800, hanhbnetfilter wrote:> bridge was configured with "brctl" > three NIC was bind to br0 > imq and htb was used to control traffic. > #modprobe imq numdevs=3 > "htb scripts" > #iptables -t mangle -A PREROUTING -i br0 -j IMQ > --todev 1 > #ip link set imq1 up > but this can not do the traffic controling. > please tell me how can i doiptables does not function on bridge devices - there are reasons for this, I''m seeing if I can push the right people into submitting a patch though. Regards, bert -- http://www.PowerDNS.com Versatile DNS Software & Services http://www.tk the dot in .tk http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
Hello, On Thu, 4 Jul 2002, bert hubert wrote:> iptables does not function on bridge devices - there are reasons for this, > I''m seeing if I can push the right people into submitting a patch though.Some days ago I uploaded some patches related to bridging. Of course, they are one big ugly hack but allow the bridging to be used in special "IP" mode (wrong word, of course) where the incoming traffic can be received on the slave ports, the output traffic can be sent via the master or the slave interfaces (according to the admin''s needs) and ARP is received on both the master and the slave interface to help the neighbouring code to play with such asymmetric routing. The result: full inspection of the traffic forwarded between the slave ports, broadcast forwarding, etc. http://www.linuxvirtualserver.org/~julian/#bridging> Regards, > > bertRegards -- Julian Anastasov <ja@ssi.bg>