One is the engine (the code part of the firmware), the other are the signature definition files, which get updated over the Internet.
Thanks for getting back. I did a factory reset and saw the same result.
Adaptive qos is giving me a headache. The trend micro engine used to recognize & give priority to my favorite game, unfortionately that has all changed. When I first saw it i thought it might have been the culprit.
Guess I'll get to work adding jrfresh's scrips.
are you sure black ops 3 uses port 3074, and not port 27017 unless that was a change to only the pc version, cause ifine warfare uses annother ports in the 27000 range but that might just be pc only. I can pull the other port number if need be for game rules.
Xbox One System NAT port 3074 tcp&udp
Black Ops3 was port 3074 for open NAT
Infinite Warfare Xbox port to get open NAT 3076
Open NAT can connect to all players, moderate can connect to open & moderate, & strict can connect only to open NAT players. Knowing that, I would imagine the game traffic is going to those ports.
As you can see, in the pic, UpNp also forwards a few external ports in the 3000's to 3076 internal. These upnp port maps show up in system logs when I end up being host for a pub.
View attachment 10082
I can think of a couple ways that might work to test & make sure.
- A switch that allows for more detailed traffic monitoring. I think my cheap Netgear might work ....or set up a pic as a network bridge
Id like to try it adding rules for those as a start. I should be able to tell if it worked by looking at the qos stats page. What would the mask be for ports 3074-3076?
i checked again you right ever cod except black ops 3 uses 3074, they changed it in a patch but it might be pc only.Xbox One System NAT port 3074 tcp&udp
Black Ops3 was port 3074 for open NAT
Infinite Warfare Xbox port to get open NAT 3076
Open NAT can connect to all players, moderate can connect to open & moderate, & strict can connect only to open NAT players. Knowing that, I would imagine the game traffic is going to those ports.
As you can see, in the pic, UpNp also forwards a few external ports in the 3000's to 3076 internal. These upnp port maps show up in system logs when I end up being host for a pub.
View attachment 10082
I can think of a couple ways that might work to test & make sure.
- A switch that allows for more detailed traffic monitoring. I think my cheap Netgear might work ....or set up a pic as a network bridge
Id like to try it adding rules for those as a start. I should be able to tell if it worked by looking at the qos stats page. What would the mask be for ports 3074-3076?
How would one go about changing the quantum, every time I see the system log I get a headache I understand if it's not an issue, I do vaguely remember reading something about it can be but I can't remember, also what is quantum for, other than a kernel error.I stand firm by the notion that Comcast customers do not have to account for WAN packet overhead. This is pre-modem overhead.
I am pretty sure that Comcast customers are bandwidth limited on modem egress traffic not modem ingress traffic, which is where the overhead is present.
Since Comcast limits at the modem, not before the modem, I do not think it is necessary to account for WAN overhead. Your ISP may vary. I just set rates under my advertised speeds until bufferbloat dropped.
The non-work-converving is a normal message.
I also have seen quantum message as well, but not recently.
Either way, I did not change the quantum value from the one that ASUS supplied, so I guess its normal aswell.
What do you mean you are only getting 20mbps/150mbps? Also you should set your QOS limits to like 80-95% of your max, not your max
How would one go about changing the quantum, every time I see the system log I get a headache I understand if it's not an issue, I do vaguely remember reading something about it can be but I can't remember, also what is quantum for, other than a kernel error.
tc class show dev eth0
I was messing with pfSense for a while and HFSC is the best QoS method they have over there and everyone is begging for fq_codel there. https://forum.pfsense.org/index.php?topic=87931.0Thanks for that explanation it makes sense now, I wonder if there's a way to get the script to automatically calculate r2q based on input of bandwidth values, I wonder if this is still an issue on the HFSC algorithm, shame we don't have it available as an option to see if it is better than HTB or doesn't have the same issues.
I've been reading the beast combination is FQ-Codel +HSFC, as in HSFC as packet scheduler and FQ-Codel as QOS discipline, read some ddwrt people saying that combo is amazing.I was messing with pfSense for a while and HFSC is the best QoS method they have over there and everyone is begging for fq_codel there. https://forum.pfsense.org/index.php?topic=87931.0
I guess fq_codel is the bee's knees as far as performance goes in QoS. I think this is something that would have to be fixed by ASUS rather than patched in a script. It is not breaking anything but I think it could be causing slight delays probably in milliseconds since it is not optimized. it's just more of an annoyance than anything. I like clean logs.
I've been reading the beast combination is FQ-Codel +HSFC, as in HSFC as packet scheduler and FQ-Codel as QOS discipline, read some ddwrt people saying that combo is amazing.
Though I have to agree with you it should be up to asus to implement it, but they will only do it if they get a lot of requests, to do so.
If the r2q was auto calculated we wouldn't see any of the r2q errors in the logs and it hope fully would become more accurate.
I'm aware of cake, but apparently the current kernels are too old to support it RMerlin told me, or the full feature set of FQ-Codel sadly I wish asus would just port it since qos is closed source. Id love to have it if its possible.Cake is another one. It is built off fq_codel supposed to be an improvement of it. https://www.bufferbloat.net/projects/attachments/150817135028_cake-
battlemesh-v8.pdf
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!