brcm47xx: don't create named switch_vlan sections
It doesn't seem to be used anywhere, it's incompatible with other targets and can be confusing. People may think they need to update section name every time they change VLAN ID (well, even I was doing that). Signed-off-by: Rafał Miłecki <zajec5@gmail.com> SVN-Revision: 41835
This commit is contained in:
parent
009e36806b
commit
7a3b3b9d73
1 changed files with 0 additions and 2 deletions
|
@ -218,11 +218,9 @@ start() {
|
||||||
[ -n "$cfg" ] && uci rename network.$cfg=eth0
|
[ -n "$cfg" ] && uci rename network.$cfg=eth0
|
||||||
[ -n "$vlan1ports" ] && {
|
[ -n "$vlan1ports" ] && {
|
||||||
cfg=`ucidef_add_switch_vlan "$switchname" 1 "$vlan1ports"`
|
cfg=`ucidef_add_switch_vlan "$switchname" 1 "$vlan1ports"`
|
||||||
[ -n "$cfg" ] && uci rename network.$cfg=eth0_1
|
|
||||||
}
|
}
|
||||||
[ -n "$vlan2ports" ] && {
|
[ -n "$vlan2ports" ] && {
|
||||||
cfg=`ucidef_add_switch_vlan "$switchname" 2 "$vlan2ports"`
|
cfg=`ucidef_add_switch_vlan "$switchname" 2 "$vlan2ports"`
|
||||||
[ -n "$cfg" ] && uci rename network.$cfg=eth0_2
|
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue