Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net,
	"babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	"cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode]
Date: Thu, 28 Apr 2016 19:10:49 +0200	[thread overview]
Message-ID: <7ibn4t3bhi.wl-jch@pps.univ-paris-diderot.fr> (raw)
In-Reply-To: <CAA93jw7TX-k+QTJj+WkfSOA9ddzrTHNPE=2DkMDaW+ZhOXLx2A@mail.gmail.com>

> 1) Well, I have suggested that IHU messages actually be unicast rather
> than bundled with the hello.

Yes, you have suggested that before.  I answered I would implement that if
somebody volunteered to do an experimental evaluation.  Nobody volunteered.

> That would help somewhat in this case.

That's my intuition too, but I've learned to be wary of my intuitions.
Doing wireless stuff without careful evaluation is not something I'll do
again.

> 2) A protocol that needs "always listening" capability could signal
> the underlying stack to "make sure" these packets hit the air, and one
> that also wants "please be lossy" capabl
> I leave the actual implementation of that request to the fantasies of
> the authors - a new dscp codepoint or three?
> /me ducks

No need to duck, Dave, it's very similar to what was done with UDP-Lite,
where the use of a specific value in the protocol field signals the link
layer not to discard corrupted frames.  I've never seen it in the wild,
I wonder why.

> 4) And ya know - it might merely be a (sadly common) bug. Everybody's
> supposed to wake up for the multicast beacons and get a notification
> there's more data to come.

Yes, it's obviously a bug.  Just like you, I'm not suprised -- ad-hoc mode
and power save is the kind of thing that's never tested.  I suggest you
disable power saving on all your nodes and be done with it.

-- Juliusz

  parent reply	other threads:[~2016-04-28 17:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 23:18 [Cerowrt-devel] perverse powersave bug with sta/ap mode 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               ` Juliusz Chroboczek [this message]
2016-04-28 17:46                 ` [Cerowrt-devel] Multicast IHUs [was: perverse powersave bug with sta/ap mode] 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 ` [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
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=7ibn4t3bhi.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 \
    /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