From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: "babel-users@lists.alioth.debian.org"
<babel-users@lists.alioth.debian.org>,
make-wifi-fast@lists.bufferbloat.net,
Michal Kazior <michal.kazior@tieto.com>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Babel-users] perverse powersave bug with sta/ap mode
Date: Thu, 28 Apr 2016 15:32:52 +0200 [thread overview]
Message-ID: <87r3dpyi2j.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw4v2J4yuNX8xeYwD5JGaeH3L_zYwZELrgNdZBtBco6WJQ@mail.gmail.com>
> Well, at least one ( probably several) of the devices I have in the
> new lab has *very aggressive* power save, to where babel ipv6
> multicast traffic either doesn't sync up to the AP's request for
> multicast (or the sta's), or it is merely completely suppressed by the
> stack. (or lost due to a bug!)...
Ok, that would explain why babeld is not falling over correctly -- since
Hellos are being lost by the power management algorithm, the link quality
of the redundant link is very low, so we only fall over when the currently
used link has timed out rather than when its link quality has fallen below
a given level.
I'm still thinking it over, but right now I'm thinking that I'm not going
to work around this kind of damange at the babeld level.
-- Juliusz
next prev parent reply other threads:[~2016-04-28 13:33 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:18 [Cerowrt-devel] " Dave Taht
2016-04-26 23:27 ` [Cerowrt-devel] [Make-wifi-fast] " Aaron Wood
2016-04-26 23:32 ` David Lang
2016-04-28 13:10 ` dpreed
2016-04-28 13:37 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:43 ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] " Toke Høiland-Jørgensen
2016-04-28 14:16 ` dpreed
2016-04-28 14:59 ` Juliusz Chroboczek
2016-04-28 15:44 ` Dave Taht
2016-04-28 16:09 ` Dave Taht
2016-04-28 17:10 ` [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Juliusz Chroboczek
2016-04-28 17:46 ` Dave Taht
2016-04-28 17:53 ` [Cerowrt-devel] [Babel-users] " Henning Rogge
2016-04-28 18:46 ` [Cerowrt-devel] Multicast IHUs Juliusz Chroboczek
2016-04-28 18:04 ` [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Dave Taht
2016-04-28 17:28 ` [Cerowrt-devel] Layering " Juliusz Chroboczek
2016-04-28 15:04 ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] perverse powersave bug with sta/ap mode moeller0
2016-04-28 16:05 ` [Cerowrt-devel] [Babel-users] [Make-wifi-fast] " Henning Rogge
2016-04-28 16:52 ` [Cerowrt-devel] [Make-wifi-fast] [Babel-users] " Dave Taht
2016-04-28 16:59 ` Henning Rogge
2016-04-28 18:54 ` Juliusz Chroboczek
2016-04-28 19:12 ` [Cerowrt-devel] [Babel-users] [Make-wifi-fast] " Henning Rogge
2016-04-28 19:29 ` Juliusz Chroboczek
2016-04-28 19:33 ` Henning Rogge
2016-04-28 19:55 ` Juliusz Chroboczek
2016-04-28 13:33 ` Juliusz Chroboczek
2016-04-28 13:32 ` Juliusz Chroboczek [this message]
2016-05-12 0:28 ` [Cerowrt-devel] " Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3dpyi2j.wl-jch@pps.univ-paris-diderot.fr \
--to=jch@pps.univ-paris-diderot.fr \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=michal.kazior@tieto.com \
/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