Hello.
Just wondered if I needed to do anything more to get this submitted into
the openwrt code?
Is there something wrong with my patch? (My corresponding LuCI patches
seems to be in a similar state -
https://lists.subsignal.org/pipermail/luci/2014-September/001570.html)
Any feedback appreciated.
Thanks
Jon
On 28/09/14 13:37, Jon Agland wrote:
VLAN bridge naming is inconsistent when using LuCI and trying to do
dynamic VLANs with OpenWRT (hostapd).
hostapd tries to use brvlanyyy but LuCI only creates br-vlanyyy (when
you use vlanyyy and select bridge)
This minor patch resolves this issue, so that you can use Dynamic VLAN
support with VLAN Naming disabled. I've also just submitted a patch
for LuCI to support dynamic VLANs -
https://lists.subsignal.org/pipermail/luci/2014-September/001570.html
This needs to be applied to
trunk/package/network/services/hostapd/files/netifd.sh
Signed-off-by: Jon Agland <j...@sftwales.com>
--- src/netifd.sh 2014-09-28 13:18:54.246081887 +0100
+++ vlan/netifd.sh 2014-09-28 13:20:30.114085964 +0100
@@ -262,6 +262,11 @@
[ -n "$vlan_tagged_interface" ] && \
append bss_conf
"vlan_tagged_interface=$vlan_tagged_interface" "$N"
}
+
+ if [ "$dynamic_vlan" -gt 0 ] && [
"$vlan_naming" -eq 0 ]; then
+ append bss_conf "vlan_bridge=br-vlan"
"$N"
+ fi
+
;;
wep)
local wep_keyidx=0
---
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
