IPQ40xx Switch Config "Strangeness" (swconfig)

[rvl]

I have a GL-S1300 and had the same question as @JFlo. After mucking around all morning wondering why my vlan id=2 setting was not working for WAN, I found this thread.

I am using OpenWrt SNAPSHOT, r14966-7330348f2d (Linux 5.4.75), and for this version it's possible to reassign the internal vlan id used for the virtual wan interface. I changed it from 2 to 3 with sysctl:

# /etc/sysctl.conf

# Use vlan id=3 for virtual wan interface hack.
net.edma.default_group2_vlan_tag=3
net.edma.default_wan_tag=3

Then I set up my switch like this (port 0 is cpu and port 5 is wan):

# /etc/config/network

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

# this vlan is used internally by the driver for lan
config switch_vlan
        option device 'switch0'
        option vlan '1'
        option vid '1'
        option ports '0t 1 2 3 4'

# this vlan is the one my isp requires for pppoe
config switch_vlan
        option device 'switch0'
        option vlan '2'
        option vid '2'
        option ports '0t 5t'

# this vlan is used internally by the driver for wan
config switch_vlan
        option device 'switch0'
        option vlan '3'
        option vid '3'
        option ports '0t 5'

Thanks!

[JFlo]

I tested the vlan tag 2 with the current stable release 19.07.5.
Now it's possible to use vlan 2 together with the wan port, but the performance is only about 65% of the stock Asus firmware.

[sgw]

A "for me too" posting from me as I was directed here from my thread

D-Link DAP 2160: vlans and wifi ... (newbie)

I am trying to set up a Wifi AP on a Dlink DAP-2160. My customer installed http://downloads.openwrt.org/snapshots/targets/ipq40xx/generic/openwrt-ipq40xx-generic-dlink_dap-2610-squashfs-factory.bin and we want to have: WebGUI (Luci) in VLAN20 (eth0.20) 2 Wifi-ESSIDs in separate VLANs 110 and 111 With much googling and fiddling I achieved point 1 ... and I could ping all the VLANs gateways on the shell. Fine. I have to add that initially there was no "Network-Switch" menu point from the st…

The hardware is a D-Link DAP-2610 (got it wrong in the initial posting over there) and I would like to ask what I can try to make VLANs work with that hardware.

[Gingernut]

Checkout this link:

[solved] VLANs on ipq40xx alternative config (for Fritzbox 4040)

At least in my experience, LuCI just doesn't "understand" the IPQ40xx switch and its driver. I don't know if the EA6350v3 is a dual-interface or single-interface device. My experience is with the EA8300 which presents eth0 and eth1 both. The guiding principles I use are based on looking at the code and coming to the conclusions that VLAN 1 and VLAN 2 are "special" -- avoid them The "Internet" port is "hard wired" to eth1 by the driver The "Ethernet" ports are "hard wired" to eth0 by the driv…

[sgw]

Thanks, will do.
In the meantime I made progress and got 3 VLANs working, I assume.
Right now I am waiting for the (remote) tester of the Wifis bridged to the interfaces.
I can't test that myself as I am a few hundred kms away from that hardware (yeah, that makes configuration extra fun).
In a few hours I should know more.

[the4anoni]

Hi
Any progress on this?
I can't got working WAN VLAN 35 on my GL-B1300, on pure OpenWRT.
It works fine on GL.iNet QSDK pure OpenWRT.

[Gingernut]

Follow and read what I linked in my reply a few posts up.

[the4anoni]

If I will setup VLAN like this can I enter PPPoE settings via Luci?

[Gingernut]

Yes.

You’ll only be creating a VLAN on the WAN port.

[the4anoni]

Didn't worked for me.
I tried this on latest openwrt.org snapshot and eko.one.pl latest build.
I put in /etc/config/network this:

config switch
option name 'switch0'
option reset '1'
option enable_vlan '1'
Was already there.

Next I tried to run PPPoE session on both: eth0.35 and eth1.35, none of them worked.

[Leo-PL]

Interestingly enough, I found those options on kernel 4.14 on my Meraki MR33 as well, on 19.07 build.

[Flole]

Were you able to get 2 VLANs working with that?

[Leo-PL]

Haven't tried yet so far, but will surely do in future.

[Flole]

Just use latest snapshot, it seems to be working properly with that.

[Leo-PL]

I will, though I wonder which commit did fix this, is it cdc8d4b46f08: ("ipq40xx: revert usage of VLAN S-TAG") or something else. It seems that on MR33, which has one port, tagging has chance to work because it behaves as if it were a "LAN" port, but for WAN this would not work as in #69.

[Flole]

If you ask me then it's probably this one: https://github.com/openwrt/openwrt/commit/2e6c236abd0bebe82bf9020941f34344acb3ae1f

[ReDaLeRt]

Would you consider merging these patches in the upstream Openwrt?

[NoTengoBattery]

Oh well, I wish but those patches left out a lot of devices in 02_network. I removed those devices since I have no way to test them. That's why I slowly add them to my custom build upon a requester willing to test them there.

[anon_openwrt]

I'm working with an EA8300 and trying to get the WAN port set up as my VLAN trunk. The WAN port does not show up in the switch section of LuCI: is it still OK to tag '5t' in switch_vlan and bridge eth1 (presumably the edma VLAN'd WAN port), without getting my config borked by LuCI/uci? I'm using VLAN 2 tags successfully on the LAN ports so that is in opposition to some of the information in this thread (possibly this has changed recently in 21.02). Perhaps other things have also recently changed? How does this "double VLAN" shenanigans impact performance on the eth1 WAN (port 5) -- maybe I should just avoid it altogether, at least as a trunk (but it's blue! )?

Here is my trunk'd VLAN on port 1 using VLAN 2 on ports 2/3, no issues:

[PolynomialDivision]

I opened now again a bug report:
https://bugs.openwrt.org/index.php?do=details&task_id=4066