From: Y <intruder_tkyf@yahoo.fr>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] cake + ipv6
Date: Tue, 18 Aug 2020 23:17:14 +0900 [thread overview]
Message-ID: <20200818231714.3d77fbd0@raspberrypi> (raw)
In-Reply-To: <CAJZMiucBwtZANNzrjRHRqEvV2exTNJ+pL26hq8TPcBxR_n=Jeg@mail.gmail.com>
Hi.
Did you try to use dual-src(dst)host option?
This is my setting.
pi@raspberrypi:~ $ tc -s qdisc show dev eth0 qdisc cake 8021: root
refcnt 2 bandwidth 831Kbit besteffort dual-srchost nonat nowash
ack-filter split-gso rtt 100.0ms atm overhead 10
pi@raspberrypi:~ $ tc -s qdisc show dev ifb4eth0 qdisc cake 8022: root
refcnt 2 bandwidth 10833Kbit besteffort dual-dsthost nonat wash
ack-filter split-gso rtt 100.0ms atm overhead 10
On Mon, 17 Aug 2020 21:52:43 -0400
Daniel Sterling <sterling.daniel@gmail.com> wrote:
> As you know, I'm here cuz I have an xbox and y'all created cake, which
> I am eternally grateful for, since it makes latency go away.
>
> But I've recently hit an interesting issue --
>
> Microsoft (and/or akamai, or whatever) has recently started pushing
> updates to the xbox via ipv6 instead of v4.
>
> As I'm sure you know ipv6 addresses are essentially random on the
> internal LAN as compared to v4 -- a box can grab as many v6 addresses
> as it wants, and I don't believe my linux router can really know which
> box is using which address, can it?
>
> Which means... ipv6 breaks cake's flow isolation.
>
> Cake can't throttle all those xbox downloads correctly cuz it doesn't
> know they're all going to/from that one device.
>
> So I suppose this may be similar to the "bittorrent" problem -- which,
> is there a general solution for that problem?
>
> In my case the xbox grabs more than its share of bandwidth, which
> means other bulk streaming -- that is to say, youtube and netflix :)
> -- stops working well
>
> I can think of one general solution -- run more wires to more devices,
> and give devices their own VLAN, and tag / prioritize / deprioritize
> specific traffic that way...
>
> But.. are there better / more general solutions?
>
> Thanks,
> Dan
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
next prev parent reply other threads:[~2020-08-18 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 1:52 Daniel Sterling
2020-08-18 2:28 ` Jonathan Morton
2020-08-18 2:54 ` Kenneth Porter
[not found] ` <D7DF629BCBA6767D1E78A973@172.27.17.193>
2020-08-18 3:44 ` Daniel Sterling
2020-08-18 4:15 ` Jonathan Morton
2020-08-18 6:41 ` Sebastian Moeller
2020-08-18 14:17 ` Y [this message]
2020-08-18 21:55 ` Michael Richardson
2020-09-23 17:36 ` Daniel Sterling
2020-09-23 18:13 ` Jonathan Morton
2020-09-24 1:07 ` Daniel Sterling
2020-09-28 6:22 ` Daniel Sterling
2020-09-28 15:14 ` Toke Høiland-Jørgensen
2020-10-01 5:09 ` Daniel Sterling
2020-10-01 11:59 ` Toke Høiland-Jørgensen
2020-11-18 0:00 ` [Bloat] openwrt e1000e (was: Re: cake + ipv6) Daniel Sterling
2020-11-20 23:25 ` [Bloat] finally got the proper cake experience (was: Re: openwrt e1000e (was: Re: cake + ipv6)) Daniel Sterling
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200818231714.3d77fbd0@raspberrypi \
--to=intruder_tkyf@yahoo.fr \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox