I have a Linksys EA8300 router running OpenWrt 21.02.1.
I'm trying to connect a DHCP client interface to a VLAN ID 101 on eth1 (the internet connector at the EA8300 box). The eth1 is connected by a tagged VLAN connection to switch with a DHCP server connected to VLAN ID 101 (see network configuration below).
I tried several configuration options like the one below, but didn't succeed to get a network address from the DHCP server connected to VLAN ID 101. A similar configuration with the tagged VLAN connected to a port of the eth0 switch works fine, the DHCP client interface gets a network address from the the DHCP server.
Can someone tell me how to configure a tagged VLAN on eth1 at the Linksys EA8300 device?
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd25:562b:066a::/48'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option proto 'dhcp'
option device 'eth1.101'
config interface 'wan6'
option proto 'dhcpv6'
option device 'eth1.101'
option reqaddress 'try'
option reqprefix 'auto'
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '1 2 3 4 0'
config device
option type '8021q'
option ifname 'eth1'
option vid '101'
option name 'eth1.101'
slh
January 6, 2022, 11:37pm
2
Impacting EA8300 and apparently EA6350v3, the IPQ40xx switch in these devices seems to have a mind of its own about VLANs and configuration.
From what I've read, this is a "non-standard" switch that may require additional development work to have functional VLANs. It seems as though the two Ethernet phys are internally "wired" to VLANs off switch port 0.
These devices appear to be dual-NIC devices, which may be almost certainly are a different wrinkle than dealt with in other threads / patches…
There is a proper solution not tooo far away, but not quite available yet either.
openwrt:master
← sartura:ipq40xx-dsa
opened 05:32PM - 25 Oct 21 UTC
This PR is a WIP draft for adding a working ethernet + DSA driver along with som… e PHY SFP improvements.
Ethernet driver is an updated and fixed version of the IPQESS driver that has been in various trees.
DSA driver is based on an older qca8k driver to which IPQ40xx specific stuff was added based on even older modified qca8k that was lingering in the same trees as the IPQESS.
DSA driver itself lacks some features that newer qca8k has like VLAN offloading but that is something that I plan on adding.
The code also isn't upstream ready due to various hacks that are specific to the IPQ40xx in regards to PSGMII.
Driver combo works surprisingly well, however it has one bug that doesn't always present itself.
The issue is that PSGMII PHY-s won't calibrate on some boots, this happens really randomly.
I have only added conversion of Jalapeno board as an example, however, I will add a few more.
Note that I don't know if RGMII works properly as I don't have any board using it.
This patch series is based on the following tree:
https://github.com/sartura/linux/tree/ipq40xx/linux-v5.10.8-DSA
It can be referenced to see the actual development in individual commits as I slightly cleaned up some things when preparing for OpenWrt submission and those are not yet reflected in our public kernel tree.
I will rebase on 5.14.14 which we are using internally and publish with OpenWrt changes.
You can see that there were actually 3 working taggers added but I only included the shinfo one which has the lowest overhead.
I find the driver combo usable, but the code requires some work regarding features and a decent cleanup.
We are publishing it in hopes that by working with the community we can eventually get support for wired networking
upstream and that will complete IPQ40xx support upstream as the only major subsystem missing.
So since the driver combo has been really fixed up I think that we need to convert all of the boards to get this merged.
So, to track that let's add a checklist:
- [x] 8devices Habanero
- [x] 8devices Jalapeno
- [x] Alfa AP120C-AC
- [x] Aruba AP-303
- [ ] Aruba AP-303H
- [ ] Aruba AP-365
- [x] Asus Lyra (MAP-AC2200)
- [ ] Asus RT-AC42U
- [x] Asus RT-AC58U
- [x] AVM FRITZ!Box 4040
- [x] AVM FRITZ!Box 7530
- [x] AVM FRITZ!Repeater 1200
- [ ] AVM FRITZ!Repeater 3000
- [ ] Buffalo WTR-M2133HP
- [x] Cell C RTL30VW
- [x] Crisis Innovation Lab MeshPoint.One
- [ ] Compex WPJ419
- [x] Compex WPJ428
- [ ] devolo Magic 2 WiFi next
- [ ] D-Link DAP-2610
- [x] Edgecore ECW5211
- [ ] Edgecore OAP100
- [ ] EnGenius EAP1300
- [ ] EnGenius EAP2200
- [ ] EnGenius EMD1
- [ ] EnGenius EMR3500
- [ ] EnGenius ENS620EXT
- [ ] EZVIZ CS-W3-WD1200G
- [ ] GL.iNet GL-AP1300
- [x] GL.iNet GL-B1300
- [x] GL.iNet GL-B2200
- [ ] GL.iNet GL-S1300
- [x] Linksys EA6350
- [x] Linksys EA8300
- [x] Linksys MR8300
- [ ] Luma Home WRTQ-329ACN
- [x] Cisco Meraki MR33
- [ ] MobiPromo CM520-79F
- [ ] NETGEAR EX6100 v2
- [ ] NETGEAR EX6150 v2
- [ ] NETGEAR RBR50
- [ ] NETGEAR RBS50
- [ ] NETGEAR SRS60
- [x] NETGEAR WAC510
- [ ] OpenMesh A42
- [ ] OpenMesh A62
- [x] P&W R619AC
- [ ] Plasma Cloud PA1200
- [ ] Plasma Cloud PA2200
- [ ] Qualcomm Atheros AP-DK01.1 C1
- [ ] Qualcomm Atheros AP-DK04.1 C1
- [ ] Qxwlan E2600AC C1
- [ ] Qxwlan E2600AC C2
- [ ] Teltonika RUTX10
- [ ] Unielec U4019
- [x] ZyXEL NBG6617
- [ ] ZyXEL WRE6606
- [x] MikroTik hAP ac2
- [x] MikroTik hAP ac3
- [x] MikroTik Wireless Wire Dish LHGG-60ad
- [x] MikroTik SXTsq 5 ac
- [x] MikroTik cAP ac
- [x] ZTE MF286D
- [ ] Telco X1 Pro
Thanks @slh for the links.
I already found the IPQ40xx Switch Config Strangeness topic, but didn't understand the restrictions of this "strangeness". Moreover, from IPQ40xx: Is it possible to use vlans? I was not sure if there is a working solution for eth1.
What I can confirm, is that with OpenWrt 21.02.1 it is possible to configure VLAN on eth0/switch0. I successfully tested a configuration with 3 VLAN IDs, running untagged on 3 ports and tagged on the fourth port of switch0 in the EA8300. So I wondered, if some kind of driver level VLAN configuration would already allow to configure a VLAN on eth1.
The PR ipq40xx: introduce proper ethernet and DSA support doesn't mention the EA8300, so I'm not sure if it would address my specific problem.
IPQ40xx devices do not use DSA in 21.02 stable. However, the UCI syntax in /etc/config/network has changed from 21.02 onwards.
Best person to answer this question might be @NoTengoBattery .
You may wish to try his custom build which I recall fully supports VLANs etc.
https://forum.openwrt.org/t/optimized-build-for-ipq40xx-devices/44125
1 Like
Thanks for the links and hints.
So my summary is:
with OpenWrt 21.02, the DSA (Distributed Switch Architecture) is not implemented yet for openwrt-21.02.1-ipq40xx-generic-linksys_ea8300-squashfs-factory.bin
for switch0/eth0 in the EA8300 device, the old swconfig framework runs fine and can be used for VLAN configurations
eth1 in the EA8300 device can't be used in a VLAN configuration with OpenWrt 21.02
implementation of DSA for the EA8300 is work in progress and hopefully will be released in the near future (test builds are available)
For my EA8300 device, I will omit the usage of eth1. I tested my VLAN configuration successfully with the usage of the 4 ports of the eth0 switch.
1 Like
system
Closed
January 20, 2022, 6:38am
6
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.