From: moeller0 <moeller0@gmx.de>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>,
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: Re: [Make-wifi-fast] [Cerowrt-devel] [Babel-users] perverse powersave bug with sta/ap mode
Date: Thu, 28 Apr 2016 17:04:32 +0200 [thread overview]
Message-ID: <4F01E09C-FE7E-4ADA-A142-656969C1A3CC@gmx.de> (raw)
In-Reply-To: <878tzx4zno.fsf@toke.dk>
> On Apr 28, 2016, at 15:43 , Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr> writes:
>
>> For discovery, multicast is unavoidable -- there's simply no way you're
>> going to send a unicast to a node that you haven't discovered yet.
>
> Presumably the access point could transparently turn IP-level multicast
> into a unicast frame to each associated station? Not sure how that would
> work in an IBSS network, though... Does the driver (or mac80211 stack)
> maintain a list of neighbours at the mac/phy level?
I believe the openwrt developers are thinking a long similar lines, see e.g. https://lists.openwrt.org/pipermail/openwrt-devel/2015-June/033398.html
Best Regards
Sebastian
>
> -Toke
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2016-04-28 15:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 23:18 [Make-wifi-fast] " Dave Taht
2016-04-26 23:27 ` Aaron Wood
2016-04-26 23:32 ` David Lang
2016-04-28 13:10 ` dpreed
2016-04-28 13:37 ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:43 ` 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 ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Juliusz Chroboczek
2016-04-28 17:46 ` Dave Taht
2016-04-28 17:53 ` [Make-wifi-fast] [Babel-users] " Henning Rogge
2016-04-28 18:46 ` [Make-wifi-fast] Multicast IHUs Juliusz Chroboczek
2016-04-28 18:04 ` [Make-wifi-fast] Multicast IHUs [was: perverse powersave bug with sta/ap mode] Dave Taht
2016-04-28 17:28 ` [Make-wifi-fast] Layering " Juliusz Chroboczek
2016-04-28 15:04 ` moeller0 [this message]
2016-04-28 16:05 ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] perverse powersave bug with sta/ap mode Henning Rogge
2016-04-28 16:52 ` Dave Taht
2016-04-28 16:59 ` Henning Rogge
2016-04-28 18:54 ` [Make-wifi-fast] [Cerowrt-devel] [Babel-users] " Juliusz Chroboczek
2016-04-28 19:12 ` [Make-wifi-fast] [Babel-users] [Cerowrt-devel] " 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 ` [Make-wifi-fast] [Babel-users] " Juliusz Chroboczek
2016-04-28 13:32 ` Juliusz Chroboczek
2016-05-12 0:28 ` [Make-wifi-fast] " 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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F01E09C-FE7E-4ADA-A142-656969C1A3CC@gmx.de \
--to=moeller0@gmx.de \
--cc=babel-users@lists.alioth.debian.org \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=jch@pps.univ-paris-diderot.fr \
--cc=make-wifi-fast@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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