Greetings, > I have an openwrt firmware installed in my router and I want to configure a > Home and a Guest interface. > So I have two internal interfaces(home,guest) and the external(eth1). First I > have to send all traffic from the two internal interfaces to external(eth1) so > that I can use one qdisc with classes which can borrow rate from each other. > Subsequently, I want to use the Tc-prio tool to apply priority queuing and then > I also want to limit the rate of the external qdisc(eth1), so I use tbf > scheduler ,as shown below. It is very important for my project to define home > and guest queues in bytes and not in packets so I want to use BFIFO in my 3 > prioritized auto created classes and not pfifo_Fast and ifconfig method. So > when I add the 3 last lines of code the two internal interfaces do not have > network access, so I suppose that the iptables commands doesn't work any more. > Is it possible for you to point the problem here? > [snip] > tc qdisc add dev $IF parent 2:1 handle 10 bfifo limit 60 > tc qdisc add dev $IF parent 2:2 handle 20 bfifo limit 60 > tc qdisc add dev $IF parent 2:3 handle 30 bfifo limit 60 I have not tried your configuration. I observe that a bfifo limit of 60 is extremely low. I'm uncertain of the correctness of my suspicion, but I think that 60 bytes may be too small to allow any packet into the transmit queue. I would think that the FIFO would not accept a packet larger than 60 bytes. That would cause bfifo to drop most of your packets when trying to enqueue them, no? Perhaps you could set the value to 1600 or 2000 (MTU + something) and try again? It is unclear what resource in particular you are trying to conserve with the choice for bfifo. I observe only that bfifo has no sense of time, so I find it a strange way to apply limiting. (Other qdiscs like codel, fq_codel and htb include time as a component of their scheduling....) Anyway, good luck, -Martin -- Martin A. Brown http://linux-ip.net/ -- To unsubscribe from this list: send the line "unsubscribe lartc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
