Hi Kevin,
Impressive! I had a look at your_layer_cake.qos, and with half the brain at my
disposal currently, I am confused. I had thought the idea is to set dscp marks
on internal hosts or the LAN interface ofva router and copy those to incoming
packets of the same flow, but you seem to set dscps in ingress. What am missing?
I ask because I fully bought your cool-aid ;) I want a "mode" for sqm scripts
where easy to set and control egress dscp from internal hosts is also used for
ingress packets of the same flows. I also bought your argument to preferably
only do that once per flow hook line and sinker.
AFAICT this is one feature that would solve a lot of issues regarding dscps in
home networks. Especially in the light of how easy it turned out to dscp mark
packets on windows10, and a lot of the potential dscp users come from the
gaming crowd and need something that works on Windows. Sidenote, I really like
how easy win10 makes it to dscp marks all egress packets of a given binary, I
wish I knew a similarly straightforward way to do this in Linux and macosx....
Thanks for this cool feature....
On March 20, 2019 9:25:31 AM GMT+01:00, Kevin Darbyshire-Bryant
<ke...@darbyshire-bryant.me.uk> wrote:
>
>
>> On 20 Mar 2019, at 03:31, Ryan Mounce <r...@mounce.com.au> wrote:
>>
>> On Wed, 20 Mar 2019 at 07:57, Kevin Darbyshire-Bryant
>> <ke...@darbyshire-bryant.me.uk> wrote:
>>>
>>>
>>>
>>>> On 19 Mar 2019, at 21:24, Ryan Mounce <r...@mounce.com.au> wrote:
>>>>
>>>> Hi Kevin,
>>>>
>>>> I've finally applied your patches, compiled, and flashed on my
>router.
>>>> Could you share your tc filter action for conndscp to get me
>started?
>>>
>>> Ahh! Ooops yes knew I forgot something - here’s my hacked up
>sqm-scripts/my_layer_cake.qos
>>
>> Okay... I've just spent far longer than I'd like to admit relearning
>> the basics of tc filter in order to minify my scripts, but everything
>> is working now. See attached for my usage. I'm back to using the
>> Turris Omnia which has more than enough grunt to handle my 100/40
>> link, so I haven't put much thought into optimisation.
>>
>> The only gotcha I ran into with your patch is the explanation
>>
>>> MODE get (typically ingress) set (typically egress)
>>
>> This is backwards, but it's confusing anyway. 'get' also sets bits in
>> the connmark while 'set' also gets bits from the connmark.
>
>Dammit! And yes it shows how confusing and how easy it is to get
>confused with the get/set terminology.
>
>>
>> I'd suggest changing 'get' to 'save', and 'set' to 'restore'.
>> <ryans-cake.txt>
>
>Fortunately the patch was sent as an RFC to netdev and I’m sure they’ll
>have other things to fix/clarify at the same time.
>
>Thanks for putting your router/s in the testing firing line. So that’s
>at least two of us doing fun DSCP shenanigans on our routers :-)
>
>
>
>Cheers,
>
>Kevin D-B
>
>gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
>
>_______________________________________________
>Cake mailing list
>Cake@lists.bufferbloat.net
>https://lists.bufferbloat.net/listinfo/cake
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Cake mailing list
Cake@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cake
