Mmmh, given the massive difference between shaper speed and true link speed I would recommend to use the following /etc/config/sqm
:
config queue 'eth1'
option ingress_ecn 'ECN'
option egress_ecn 'ECN'
option itarget 'auto'
option etarget 'auto'
option verbosity '5'
option qdisc 'cake'
option script 'piece_of_cake.qos'
option qdisc_advanced '1'
option squash_dscp '0'
option squash_ingress '1'
option qdisc_really_really_advanced '1'
option eqdisc_opts 'nat dual-srchost'
option linklayer 'ethernet'
option linklayer_advanced '1'
option tcMTU '2047'
option tcTSIZE '128'
option linklayer_adaptation_mechanism 'default'
option debug_logging '1'
option iqdisc_opts 'nat dual-dsthost ingress'
option interface 'pppoe-wan'
option tcMPU '84'
option enabled '1'
option overhead '42'
option download '45000'
option upload '15000'
The overhead/tcMPU settings are relevant if lots of small packets (like TCP-ACKs) are being sent and if the shaper rate is close to the true bottleneck/link speed; so in your current case this is mostly cosmetic but prepares your sqm configuration for operating closer to the true limit.
The nat dual-xxxhost
settings configure cake for per-internal-IP isolation which in theory should do the right thing except in your case with dscord and gforce now on the same computer will not exchange much...
Regarding the fact that the issue still is there, it would be good to check whether the router's CPU is maxed out while playing and using discord. The quick and dirty way of doing that on your single core (on a multicore router you would need htop and adjust its configuration) router is:
- log into the router via SSH
- `top -d 1'
- start playing/discording
- Calculate 100- %-idle as an indicator for the CPU load. As an example without load:
Mem: 75760K used, 44728K free, 33160K shrd, 0K buff, 47456K cached
CPU: 0% usr 2% sys 0% nic 95% idle 0% io 0% irq 0% sirq
Load average: 0.00 0.00 0.00 2/88 18544
so the CPU load would be 100-95 = 5%
, the device is not doing anything
with a speedtest:
Mem: 76296K used, 44192K free, 33160K shrd, 0K buff, 47660K cached
CPU: 1% usr 6% sys 4% nic 33% idle 0% io 0% irq 54% sirq
Load average: 0.18 0.06 0.01 2/87 18595
so the CPU load would be 100-33 = 67%
, which is a lot, given that this is a dual core router 67% actually means one core is maxed out ('50%' of total while the second core was at '17%' of total).
- use CTRL-c to end top (or press q to ed htop)
If the load gets into the 90-100% during your gaming when the issue occur, this would indicate the router already being overloaded (leaving the option to reduce the shaper rates even further or get a beefier router). The first option however is likely to run into the issue that gforce now requires 15 Mbps for 720, but already >= 25 Mbps for 1920 (and more for higher spatial and temporal resolutions).