I am having quite some difficulty in getting VLANs to work on IPQ4019 based custom hardware. Please note that this hardware uses a QCA8072 Dual Port transceiver connected via PSGMII to IPQ4019. I am unable to get even basic VLAN support working with this device. To start with I would expect that the following config would result in a workable network:
config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
config switch_vlan
option device 'switch0'
option vlan '1'
option ports '0t 4'
option vid '1'
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 'fd2a:618b:4b4b::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth1.1'
option ip6assign '60'
option proto 'dhcp'
If I change the ifname for lan to eth1 (rather than eth1.1), this will work. This whole situation makes no sense to me. I would really like to hear any ideas there might be on this.
Thanks for reading
slh
March 21, 2022, 10:49pm
2
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
- [ ] Asus Lyra (MAP-AC2200)
- [ ] Asus RT-AC42U
- [x] Asus RT-AC58U
- [x] AVM FRITZ!Box 4040
- [x] AVM FRITZ!Box 7530
- [ ] AVM FRITZ!Repeater 1200
- [ ] AVM FRITZ!Repeater 3000
- [ ] Buffalo WTR-M2133HP
- [ ] Cell C RTL30VW
- [ ] Crisis Innovation Lab MeshPoint.One
- [ ] Compex WPJ419
- [x] Compex WPJ428
- [ ] devolo Magic 2 WiFi next
- [ ] D-Link DAP-2610
- [ ] 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
- [ ] GL.iNet GL-B2200
- [ ] GL.iNet GL-S1300
- [x] Linksys EA6350
- [ ] Linksys EA8300
- [ ] 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
- [ ] NETGEAR WAC510
- [ ] OpenMesh A42
- [ ] OpenMesh A62
- [ ] 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
- [ ] MikroTik Wireless Wire Dish LHGG-60ad
- [x] MikroTik SXTsq 5 ac
- [ ] MikroTik cAP ac
- [ ] ZTE MF286D
- [ ] Telco X1 Pro
That should solve it properly.
Thanks for the suggestion! I will certainly look into it but does this imply there is a known reason why the old (non DSA) method for VLAN implementation should fail in this situation?
Also please note that the current development for this hardware is being done in 19.07.
slh
March 22, 2022, 4:02am
4
…it's complicated. The hardware is special, the driver is quirky - trying to hide the switch and the fact that there is only a single CPU port (faking a second and hardcoding a special VLAN config, making real VLANs on top difficult and slow)
The enduser howto would be
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…
But there are very detailed explanations here in past forum threads, but the solution to all this is the pending DSA driver replacing all that.
The link to "IPQ40xx Switch Config Strangeness" gave me the answers I was looking for. Thanks for posting, not sure how I missed that in my previous search.
system
Closed
April 1, 2022, 3:44pm
6
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.