From: Noah Causin <n0manletter@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: make-wifi-fast@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] Fwd: [PATCH net-next] bridge: multicast to unicast
Date: Wed, 4 Jan 2017 17:16:45 -0500 [thread overview]
Message-ID: <69084572-2fb9-0b13-388a-5076d31322d4@gmail.com> (raw)
In-Reply-To: <CAA93jw569scsZD_7JrdmbYGtnXW39v82PAv-J_Qn1gSr5eP5bA@mail.gmail.com>
I haven't been able to find a way to manipulate the bridge flag using a
software utility.
Maybe changing this variable could work.
/sys/class/net/br-lan/lower_wlan0/brport/multicast_to_unicast
On 1/4/2017 4:51 PM, Dave Taht wrote:
> On Wed, Jan 4, 2017 at 1:43 PM, Noah Causin <n0manletter@gmail.com> wrote:
>> I asked Felix about this, and he said that as long as the AP Interface is
>> connected to a bridge, multicast to unicast conversion is available.
>>
>> The patch notes said that it has been enabled by default in LEDE and OpenWRT
>> for about a year.
> Well, babeld is breaking on bridges at the moment, this might be why.
> Is there a way to turn it off?
>
>> On 1/3/2017 1:14 PM, Noah Causin wrote:
>>
>> I wonder if this means just adding a WiFi interface to a bridge enables this
>> functionality.
>>
>>
>> On 1/2/2017 3:42 PM, Toke Høiland-Jørgensen wrote:
>>
>> Seems LEDE has had multicast suppression for a while? :)
>>
>> -Toke
>>
>>
>>
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>>
>>
>>
>>
>> _______________________________________________
>> Make-wifi-fast mailing list
>> Make-wifi-fast@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/make-wifi-fast
>
>
prev parent reply other threads:[~2017-01-04 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 20:42 Toke Høiland-Jørgensen
2017-01-03 18:14 ` Noah Causin
2017-01-04 21:43 ` Noah Causin
2017-01-04 21:51 ` Dave Taht
2017-01-04 22:16 ` Noah Causin [this message]
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=69084572-2fb9-0b13-388a-5076d31322d4@gmail.com \
--to=n0manletter@gmail.com \
--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