<div dir="ltr"><div><br></div>(Re-submitting as I needed to subscribe first... )<br><br>Thnx for the info. I presume I should then submit my request for proposal within this mailing list? If so here is a bit more details surrounding my use case:<br><div><div class="gmail_quote"><div dir="ltr"><div><div><div><div><br>It all started with this really well made documentation that I wished to impleted (dynamic vlan over wifi):<br><a href="https://wiki.openwrt.org/doc/howto/wireless.security.8021x" target="_blank">https://wiki.openwrt.org/doc/howto/wireless.security.8021x</a><br><br>The issue I have is that we must provide a brige name suffix for this to work. I was hoping that instead it could be possible to provide a list of bridge names instead.<br>Option could be either using a different parameter or something else?<br>1- if there is a single parameter to vlan_bridge use it as a suffix<br>or<br>2- if there are many parameter use the list of bridge names<br>This could also be implemented differently or using a new parameter, what ever fits best (if any).<br><br></div><div>The underlying issue is that otherwise renaming all bridge to br-vlanX totally removes the clarity of the various naming of each interfaces and moves the configuration even farther from out of the box.<br><br></div><div>In my case I have 4 vlans whereas I would pass 3 of them as follow (if feature ever added):<br></div></div></div></div></div><div dir="ltr"><div><div><div><div>option vlan_bridge 'br-lan' 'br-media' 'br-guest'<br></div><div><br></div></div></div></div></div><div dir="ltr"><div><div><div>To put more context to it here is an extract of the documentation:<br>...First, we must name our interfaces in <code>/etc/config/network</code> based on their VLAN such as <code>vlan1</code> and <code>vlan3</code>. This causes OpenWRT to name the bridges it creates <code>br-vlan1</code> and <code>br-vlan3</code>. Second, we set the <code>vlan_bridge</code> option in <code>/etc/config/wireless</code> to "br-vlan" and the <code>vlan_naming</code>
option to "0" what this does is tell hostapd to create bridges using
the br-vlanY naming convention (where Y is the VLAN number)....<br><br></div>I'm sure there are more to it which may block such a request but I tought it was worth asking.<br><br></div>Thnx in advance!<br><br></div>- vin</div><div dir="ltr"><br><div><div><div><div><div><div><div><br><div class="gmail_quote"><div dir="ltr">Le lun. 11 janv. 2016 à 07:06, OpenWrt <<a href="mailto:openwrt-devel@lists.openwrt.org" target="_blank">openwrt-devel@lists.openwrt.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">#21573: hostapd: Full Dynamic VLAN support - vlan_bridge name list<br>
-----------------------+--------------------------------<br>
Reporter: th0ma7 | Owner: developers<br>
Type: defect | Status: closed<br>
Priority: normal | Milestone:<br>
Component: packages | Version: Chaos Calmer 15.05<br>
Resolution: fixed | Keywords:<br>
-----------------------+--------------------------------<br>
Changes (by jow):<br>
<br>
* status: new => closed<br>
* resolution: => fixed<br>
<br>
<br>
Comment:<br>
<br>
This is not valid uci:<br>
<br>
`option 'vlan_bridge' 'br-lan' 'br-media' 'br-guest'`<br>
<br>
Also, I see no indication that vanilla hostapd.conf allows multiple vlan<br>
bridges either and finally this ticket is a feature request and not a bug.<br>
<br>
Please send a *clear* and *detailed* proposal to the development list<br>
outlining your wanted change.<br>
Explain how the resulting hostapd.conf must be generated and how an<br>
example (uci) configuration would look like.<br>
<br>
Alternatively send your proposal in the form of a patch. Please do not<br>
open a ticket unless there is an actual bug or regression.<br>
<br>
--<br>
Ticket URL: <<a href="https://dev.openwrt.org/ticket/21573#comment:2" rel="noreferrer" target="_blank">https://dev.openwrt.org/ticket/21573#comment:2</a>><br>
OpenWrt <<a href="http://openwrt.org" rel="noreferrer" target="_blank">http://openwrt.org</a>><br>
Opensource Wireless Router Technology<br>
</blockquote></div></div></div></div></div></div></div></div></div></div></div></div>