On Sun, Sep 25, 2016 at 8:20 PM, Kevin Darbyshire-Bryant <ke...@darbyshire-bryant.me.uk> wrote: > Greetings! > > A while back I started on a quest to make cake 'nat' aware as the lack of > host fairness in a typical home router environment was the only thing that > prevented cake from being the ultimate qdisc in my opinion. This involves > dealing with conntrack which on egress is easy (the kernel fills in a data > structure for us), ingress is less clear. I hacked something together but > wasn't really happy with it. > > Another github user 'tegularius' presented some beautifully crafted code > that did the lookups in a much neater way. Originally it too had an > 'ingress' lookup problem. This was worked on and I hacked some conditional > 'denat' options into cake & tc. > > For your 'delight' a denat cake > https://github.com/kdarbyshirebryant/sch_cake/tree/natoptions along with a > matching tc https://github.com/kdarbyshirebryant/tc-adv/tree/denat > > Typically I use 'dual-srchost srcnat' options on the egress interface, with > 'dual-dsthost dstnat' in the ingress ifb interface. In *brief* testing, > bandwidth is shared fairly between hosts, and fairly by flow within each > host. And it's not crashed yet.
Groovy! (good morning). Is there a way to autodetect if nat is on or not? If you are bored and want to see what happens with tcp bbr, I just set up a server at: 173 dot 230 dot 156 dot 252 and I'll probably put one up in the uk as well. > Kevin > _______________________________________________ > Cake mailing list > Cake@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/cake -- Dave Täht Let's go make home routers and wifi faster! With better software! http://blog.cerowrt.org _______________________________________________ Cake mailing list Cake@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/cake