Interface names when putting 802.1q VLAN on top of bonding configuration
Mike Bernardo
mike at aion.cx
Mon May 31 12:45:10 PDT 2021
One more question, now I'm trying to put a bridge on top of each of these vlan* interfaces so that I can map those to a few physical interfaces. I also need several vlans to map to one of the interfaces (tagged).. not sure how to do that yet either. Any suggestions with this config? When I apply it, I lose network access.
It looks wrong that after applying the below config, that br-bv10 is now a master for vlan10 at bonding-lanxge
69: vlan10 at bonding-lanxge: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-bv10 state UP group default qlen 1000
Also, is there any way to not need 'option ipaddr 127.0.0.2' in the lanxge interface?
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdb9:bf48:0362::/48'
config interface lanxge
option proto 'bonding'
option auto '1'
option bonding_policy '802.3ad'
option link_monitoring 'mii'
option slaves 'eth4 eth5'
option lacp_rate 'fast'
option miimon '100'
option use_carrier 1
option xmit_hash_policy 'layer3+4'
option force_link '1'
option ipaddr 127.0.0.2
config device
option type 8021q
option ifname bonding-lanxge
option vid 10
option name vlan10
config interface vlan10
option ifname vlan10
option proto static
option ipaddr 172.20.32.250
option netmask 255.255.255.0
config device
option type 8021q
option ifname bonding-lanxge
option vid 20
option name vlan20
config interface vlan20
option ifname vlan20
option proto static
option ipaddr 172.20.34.2
option netmask 255.255.255.128
config device
option type 8021q
option ifname bonding-lanxge
option vid 21
option name vlan21
config interface vlan21
option ifname vlan21
option proto static
option ipaddr 172.20.35.3
option netmask 255.255.255.240
config device
option type 8021q
option ifname bonding-lanxge
option vid 30
option name vlan30
config interface vlan30
option ifname vlan30
option proto static
option ipaddr 172.20.34.130
option netmask 255.255.255.128
config interface 'wan'
option ifname 'eth0.0'
option proto 'dhcp'
config interface bv10
option type 'bridge'
option ifname vlan10
option auto '1'
option force_link '1'
config interface bv20
option type 'bridge'
option ifname vlan20
option auto '1'
option force_link '1'
config interface bv21
option type 'bridge'
option ifname vlan21
option auto '1'
option force_link '1'
config interface bv30
option type 'bridge'
option ifname vlan30
option auto '1'
option force_link '1'
> On 2021/05/28, at 10:52:25 CDT (-05:00), Mike Bernardo <mike at aion.cx> wrote:
>
> Ah thanks! This worked great. I swear I tried something nearly identical before that broke everything.
>
> Mike
>
>> On 2021/05/28, at 02:34:44 CDT (-05:00), Jo-Philipp Wich <jo at mein.io> wrote:
>>
>> Hi,
>>
>> the following should do what you want.
>>
>> config device
>> option type 8021q
>> option ifname bonding-lan
>> option vid 20
>> option name vlan20
>>
>> config interface vlan20
>> option ifname vlan20
>> option proto static
>> option ipaddr 172.20.34.2
>> option netmask 255.255.255.128
>>
>>
>> ~ Jo
>>
>> _______________________________________________
>> openwrt-devel mailing list
>> openwrt-devel at lists.openwrt.org
>> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
>
>
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel at lists.openwrt.org
> https://lists.openwrt.org/mailman/listinfo/openwrt-devel
More information about the openwrt-devel
mailing list