Wallace_n_Gromit
Senior Member
That's so funny. I always wondered these last 1 1/2 years what your pic of the |> represented. It's a wizard hat on its side, OF COURSE!You should soon be able to have it, and eat it. /cryptic wizard hat off
That's so funny. I always wondered these last 1 1/2 years what your pic of the |> represented. It's a wizard hat on its side, OF COURSE!You should soon be able to have it, and eat it. /cryptic wizard hat off
Correct as is the case with the addon nowAlso just to keep everyone's expectations at a reasonable level: this is not compatible with hardware acceleration. So, forget about using Cake on your 500 Mbps connection, your CPU won't be able to keep up.
The question is: Will you have to uninstall independent script prior to firmware upgrade?
Do the settings port?
This should already work (the DSCP netfilter target is already available):If cake is coming to the webui, is there a chance of enabling skbedit so we can apply our own DSCP marking as well then?
CakeQOS - CakeQoS Help
Hey! How would I go about including docsis and ack-filter the at the same time? When I do cake-qos settings optionsup docsis ack-filter, it only applies the docsis and not the ack-filter. If I do one at a time, it removes any previous settings. I'm not sure I understand, once you ssh...www.snbforums.com
iptables -t mangle -A FORWARD -p tcp --dport 8888 -j DSCP --set-dscp 1
I forgot my password so i need to see. In stable version you can ticked show password .No, both server and clients are not revealed. Why did you ask?
@RMerlin, has alot change from using current cake-qos script compared to GUI built-in cake option? I saw this so I'm guessing the upstream is now differsev3 and besteffort on upstream compared to current script which the default was set to besterffort.Here`s a preview of the UI (I wanted to keep it simple, so only the fields related to overhead are available, and there is a preset dropdown to prefill them, just like with fq_codel:
View attachment 31455
Setting Bandwidth to "0" or "Automatic" will configure cake with bandwidth set to "unlimited". ingress-autorate was tested, and it was totally useless. Connecting to the router's WAN interface over SSH or the webui was ridiculously slow.
rc: implement Cake QoS mode for HND routers
Cake support is implemented as new qos_type of 9 (high
number was used to avoid conflicts in case Asus add more
qos types in the future). A couple of notes:
- Only supported by kernel 4.1.xx (that's HND models at this time)
- Not compatible with flow cache/runner/archer acceleration,
so currently not suitable for connections above ~350 Mbps
- In line with the original Cake design philosophy, only a limited
number of configurable settings are exposed to the user
- If user sets bandwidth to Automatic (or 0) on webui, then set
bandwidth to unlimited. ingress-autorate was tested, and
show to provide very poor performance, so it wasn't implemented
- A diffserv3 setup is used for upstream (so users of ATA/VoIP
phones with diffserv support can benefit from it), and
besteffort on downstream
- overhead (including mpu, atm and ptm settings) are supported
at the webui level
- nat mode is enabled if the router handles NAT
My understanding was that this was for egress only. Doesn't "tc filter" need to be used for ingress tagging?This should already work (the DSCP netfilter target is already available):
Code:iptables -t mangle -A FORWARD -p tcp --dport 8888 -j DSCP --set-dscp 1
It's separate.So in theory my 100/40 VDSL 2 connection should be fine with cake, and also is this a a part of adaptive QoS or seperate like traditional QoS?
Hmmm...I seem to recall the Icelandic language has a letter like that, and it's pronounced TH as in Thor, who swings a mighty mjolnir. <shrug>That's so funny. I always wondered these last 1 1/2 years what your pic of the |> represented. It's a wizard hat on its side, OF COURSE!
Which does raise a good point. Hopefully the GUI is accessible without needing to enable the global QoS slider, and hence needing to give permissions for Trend Micro. I definitely prefer having Trend Micro entirely off with permissions withdrawn.
Oh ok, sounds like it might be safe to do then. Perhaps my mistake in thinking that slider would trigger the permissions. Must also need to enable adaptive to trigger the permissions prompt.Good question. I am testing right now and although I did have to enable the slider, the option for "Withdraw" on the Admin>Privacy tab is still not available (similar to my routers with the addon only).....
No idea, I never played with that. I just saw a reference to using the DSCP target in a Cake-related thread through a quick Google search.My understanding was that this was for egress only. Doesn't "tc filter" need to be used for ingress tagging?
Oh ok, sounds like it might be safe to do then. Perhaps my mistake in thinking that slider would trigger the permissions. Must also need to enable adaptive to trigger the permissions prompt.
I loosely based my design on Lede/OpenWRT scripts such layer_cake, not on CakeQOS. I'm going with diffserv3 on the upstream because most VoIP solutions will use DSCP out of the box (both my work VoIP phone and my home ATA do). This will allow improved VoIP handling, which is more important IMHO than just trying to get the nicest latency charts off test sites.@RMerlin, has alot change from using current cake-qos script compared to GUI built-in cake option? I saw this so I'm guessing the upstream is now differsev3 and besteffort on upstream compared to current script which the default was set to besterffort.
#!/bin/sh
ULIF='eth0'
DLIF='eth0'
MIF='ifb4eth0'
ULBW='bandwidth 51200kbit'
DLBW='bandwidth 409600kbit'
OVERHEAD='overhead 38 mpu 84'
FRAMING=''
case "$1" in
start)
# Upload
tc qdisc add dev $ULIF root cake nat diffserv3 $ULBW $OVERHEAD $FRAMING 2>/dev/null
# Download
ip link add name $MIF type ifb 2>/dev/null
tc qdisc add dev $DLIF handle ffff: ingress 2>/dev/null
tc qdisc add dev $MIF root cake nat wash $DLBW besteffort $OVERHEAD $FRAMING 2>/dev/null
ip link set $MIF up 2>/dev/null
tc filter add dev $DLIF parent ffff: prio 10 matchall action mirred egress redirect dev $MIF 2>/dev/null
;;
stop)
tc qdisc del dev $ULIF root 2>/dev/null
tc qdisc del dev $DLIF ingress 2>/dev/null
tc qdisc del dev $MIF root 2>/dev/null
ip link set $MIF down 2>/dev/null
ip link del dev $MIF 2>/dev/null
;;
*)
esac
Appreciate the info. I have 100% agree. I could never quite get a steady/realiable connection with comcast and cake script hence why I was using FlexQoS. It would be good some days but not consistently.I loosely based my design on Lede/OpenWRT scripts such layer_cake, not on CakeQOS. I'm going with diffserv3 on the upstream because most VoIP solutions will use DSCP out of the box (both my work VoIP phone and my home ATA do). This will allow improved VoIP handling, which is more important IMHO than just trying to get the nicest latency charts off test sites.
This is an example of a QoS script generated by the firmware on my test setup at this time in development (things are still in flux and are not final):
Code:#!/bin/sh ULIF='eth0' DLIF='eth0' MIF='ifb4eth0' ULBW='bandwidth 51200kbit' DLBW='bandwidth 409600kbit' OVERHEAD='overhead 38 mpu 84' FRAMING='' case "$1" in start) # Upload tc qdisc add dev $ULIF root cake nat diffserv3 $ULBW $OVERHEAD $FRAMING 2>/dev/null # Download ip link add name $MIF type ifb 2>/dev/null tc qdisc add dev $DLIF handle ffff: ingress 2>/dev/null tc qdisc add dev $MIF root cake nat wash $DLBW besteffort $OVERHEAD $FRAMING 2>/dev/null ip link set $MIF up 2>/dev/null tc filter add dev $DLIF parent ffff: prio 10 matchall action mirred egress redirect dev $MIF 2>/dev/null ;; stop) tc qdisc del dev $ULIF root 2>/dev/null tc qdisc del dev $DLIF ingress 2>/dev/null tc qdisc del dev $MIF root 2>/dev/null ip link set $MIF down 2>/dev/null ip link del dev $MIF 2>/dev/null ;; *) esac
Apologies, I am only able to relay half-understood details .No idea, I never played with that. I just saw a reference to using the DSCP target in a Cake-related thread through a quick Google search.
.
Appreciate the info. I have 100% agree. I could never quite get a steady/realiable connection with comcast and cake script hence why I was using FlexQoS. It would be good some days but not consistently.
Hope to see a difference and we really do appreciat all your hardwork!
A lot of great stuff coming soon!!!!
Thanks again!
Only Adaptive QoS requires the Trend Micro engine. None of the other QoS modes do.
When I went to openwrt I looked for some information about dscp marking for incoming traffic and found it to be pretty hard work.I just saw a reference to using the DSCP target in a Cake-related thread through a quick Google search.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!