Hello,

I have been trying out ROS 6 (rc13) on some of our routers, and i have noted that the way queues work have changed for double qos. It seems that rate limiting with simple queues is no where near as stable as rate limiting with queue tree in the older versions of ROS.

This week we have just installed ROS 6 at a new site, and our first 4 customers at the new site have connected. We have a good point to point link that pushes 80Mb/s to the site (tested with iPerf) so there is no way the bottle neck is on out back haul.

We limit a customer to say 20Mb/s downstream with simple queues but struggle to get 15Mb/s.

As an experiment tonight, i saw a customer pulling a large download so i decided to remove the simple queue that was rate limiting that customer. Immediately the throughput climbed upto around 40Mb/s to the customer, so the point to point link and the point to multi point access to the customer is good. Only simple queues seem to be slowing things up for our customers.

Any thoughts?

Use k insted of M to speed limit.

I will give it a go, and feed back some results.

Interested to see your results.

Sorry, there may not be a topic. But I would like to know how to adapt this one example shaper of 5 to version 6? From version 6 is no global-in and global-out, and there's only global:

/ip firewall mangle
add action=mark-packet chain=prerouting comment="Pam_Unlim_500_x2 SRC" disabled=no \
new-packet-mark=Pam_Unlim_500_x2-OUT passthrough=yes src-address-list=Pam_Unlim_500_x2
add action=mark-packet chain=postrouting comment="Pam_Unlim_500_x2 DST" disabled=no \
dst-address-list=Pam_Unlim_500_x2 new-packet-mark=Pam_Unlim_500_x2-IN passthrough=yes

/queue type
add kind=pcq name=Pam_Unlim_500_x2-IN pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=\
10s pcq-classifier=dst-address pcq-dst-address-mask=32 \
pcq-dst-address6-mask=64 pcq-limit=50 pcq-rate=512k pcq-src-address-mask=\
32 pcq-src-address6-mask=64 pcq-total-limit=2000
add kind=pcq name=Pam_Unlim_500_x2-OUT pcq-burst-rate=0 pcq-burst-threshold=0 pcq-burst-time=\
10s pcq-classifier=src-address pcq-dst-address-mask=32 \
pcq-dst-address6-mask=64 pcq-limit=50 pcq-rate=512k pcq-src-address-mask=\
32 pcq-src-address6-mask=64 pcq-total-limit=2000

/queue tree
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=0 name=Pam_Unlim_500_x2-IN packet-mark=Pam_Unlim_500_x2-IN parent=global-out priority=1 \
queue=Pam_Unlim_500_x2-IN
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=0 name=Pam_Unlim_500_x2-OUT packet-mark=Pam_Unlim_500_x2-OUT parent=global-in priority=1 \
queue=Pam_Unlim_500_x2-OUT

Wrote here is the rule:

/queue tree
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=0 name=Pam_Unlim_500_x2-IN packet-mark=Pam_Unlim_500_x2-IN parent=Local priority=1 \
queue=Pam_Unlim_500_x2-IN
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=no limit-at=0 \
max-limit=0 name=Pam_Unlim_500_x2-OUT packet-mark=Pam_Unlim_500_x2-OUT parent=Internet priority=1 \
queue=Pam_Unlim_500_x2-OUT

Where Local - this is a local interface.
Intenet - the interface looking into a global network.
Outgoing restriction works, Incoming restriction does not work.

I have a similar issue with ROS 6.3. Did you find any solution?

I have a similar issue with ROS 6.3. Did you find any solution?

Solution is to change queue type from default-small to default. Or create a new pfifo queue with a larger buffer(>50packets).