Seven months later....
The key issue was the fact that simply using the "pre-up iw dev wlan0
set 4addr on" command wasn't enough because of the race issue. Whatever
you end up doing, make sure to account for that.
Your solution sounds reasonable given the concerns you described with
proprietary drivers.
I can't think of anything else we should be concerned about right now.
Also, as an FYI, the debian wpasupplicant package finally just got
support for bridging a few weeks ago. So, if you can figure out a
solution for this, the next Debian release should natively support
wireless bridging via 4addr mode.
On 10/15/2016 02:47 PM, Santiago Garcia Mantinan wrote:
Hi!
Sorry, but I hadn't read this bugreport till today.
First of all I'd like to clarify that 4-address is not the only way to add a
wifi interface to a bridge, I have done this for years with wifi interfaces
on ap mode without using 4-address at all.
So, setting 4-address on all wifi interfaces automatically doesn't seem good
to me, so... what do you think if we add a new bridge_4addr option that lets
you specify what interfaces should be configured with 4addr? Something like:
bridge_4addr wlan0 wlan1
Does that sound ok?
Regards.
