From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 023073B25D; Thu, 28 Apr 2016 09:43:30 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1461851004; bh=KeoS83Zr3gZNVWDQ2RkgtD6oXtWjHtusJLH+lfdopv4=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=YZNtVB8oryAjv/xxb1aChgGyIgbomzGBVmgcivuyrV7rAI9jq7c25CDzoWNlL+hmP nYInBUjZDR7wjAfKEKv206b+Y/QEhlpUcDuazPC8InMgOMym4kMW0wEKI7wbue1J5/ xJaPZwwJEcQuNIpFCg9S4sP0isrl7B0z/DYt2yDU= Sender: toke@toke.dk Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id D3118C40154; Thu, 28 Apr 2016 15:43:23 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Juliusz Chroboczek Cc: dpreed@reed.com, make-wifi-fast@lists.bufferbloat.net, "babel-users\@lists.alioth.debian.org" , "cerowrt-devel\@lists.bufferbloat.net" References: <1461849006.60252745@apps.rackspace.com> <87oa8tyhug.wl-jch@pps.univ-paris-diderot.fr> Date: Thu, 28 Apr 2016 15:43:23 +0200 In-Reply-To: <87oa8tyhug.wl-jch@pps.univ-paris-diderot.fr> (Juliusz Chroboczek's message of "Thu, 28 Apr 2016 15:37:43 +0200") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <878tzx4zno.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Make-wifi-fast] [Babel-users] perverse powersave bug with sta/ap mode X-BeenThere: make-wifi-fast@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Apr 2016 13:43:31 -0000 Juliusz Chroboczek 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? -Toke