GL-B1300 with vlans, one of switch ports won't work

[TriplEight]

Version 22.03.5 r20134-5f15225c1e.
My br-lan bridges two switch vlans. WAN is connected to the modem.

I have set up vlans and firewalls for IoT, Guest and Normal networks.

Switch looks like this

VLAN 1: # eth0(CPU)
	vid: 1
	ports: 0t 3t 4t
VLAN 2: # wan / eth1 / port 5
	vid: 2
	ports: 0t 5
VLAN 103: # switch, left port
	vid: 103
	ports: 0t 3
VLAN 104: # switch, middle port
	vid: 104
	ports: 0t 4

With this config, a RPI with AdGuard works as a DNS. But I can't use another switch port for my desktop. Seems like no traffic leaves the port. And If I either separate switch vlans from br-lan. Or add any other interface that has something to do with the switch ports, I loose wan. It instantly looses my wire-connected DNS on RPI and practically as good as dead.

Network setup:

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 'xxx'

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

config switch_vlan
	option device 'switch0'
	option vlan '103'
	option vid '103'
	option ports '0t 3'
	option description 'lan1p3'

config switch_vlan
	option device 'switch0'
	option vlan '104'
	option vid '104'
	option ports '0t 4'
	option description 'lan2p4'

config device
	option name 'br-lan'
	option type 'bridge'
	option igmp_snooping '1'
	option acceptlocal '1'
	option ipv6 '0'
	list ports 'eth0.103'
	list ports 'eth0.104'

config interface 'lan'
	option proto 'static'
	option netmask '255.255.255.0'
	option ip6assign '60'
	option dns_metric '0'
	option ifname 'eth0.103'
	option ipaddr '192.168.2.1'
	option gateway '192.168.1.1'
	list dns '192.168.2.184'
	option device 'br-lan'

config device
	option type 'bridge'
	option name 'VLANS'
	list ports 'eth0.103'
	list ports 'VLANS.60'
	list ports 'VLANS.20'
	list ports 'VLANS.30'
	option igmp_snooping '1'
	option acceptlocal '1'
	option ipv6 '0'

config bridge-vlan
	option device 'VLANS'
	option vlan '20'
	list ports 'eth0.103:t'
	list ports 'VLANS.20:t'

config bridge-vlan
	option device 'VLANS'
	option vlan '30'
	list ports 'eth0.103:t'
	list ports 'VLANS.30:t'

config bridge-vlan
	option device 'VLANS'
	option vlan '60'
	list ports 'eth0.103:t'
	list ports 'VLANS.60:t'

config interface 'IoT'
	option proto 'static'
	option device 'VLANS.20'
	option ipaddr '192.168.20.4'
	option netmask '255.255.255.0'
	option gateway '192.168.20.1'
	option type 'bridge'

config interface 'WIFI'
	option proto 'static'
	option device 'VLANS.30'
	option ipaddr '192.168.30.4'
	option netmask '255.255.255.0'
	option gateway '192.168.30.1'

config interface 'wan'
	option proto 'static'
	option device 'eth1'
	option netmask '255.255.255.0'
	option gateway '192.168.1.1'
	option ipaddr '192.168.1.2'
	list dns '192.168.2.184'

config device
	option name 'eth1'
	option ipv6 '0'

Device wiki has a note about it, but it doesn't help:

GL.iNet GL-B1300

I've tried the suggestions from various posts, to no avail:

Trouble isolating switch ports on GL.iNet GL-B1300 [Solved]

So I just got my B1300 in today and I started playing around with it. My usual process for isolating switch ports is to create a simple vlan definition for each and then place my lan/applications on eth0.vlan_id this has worked perfectly on every LEDE device I've tried in the past. But not to much on the B1300, digging in with swconfig this device has one switch for all of it's ports and wifi interfaces, with port 0 as the cpu port. It's in the default netwok config that things get unusual. co…

GL-B1300: tagged VLAN on WAN not working

Hi, I'm trying to configure a GL-B1300 (running 21.02.3) as wireless access point. The GL-B1300 WAN port is connected to my main router. This works fine, until I try to use VLAN's on the WAN port. The goal is to have a trunk with 3 tagged VLAN's: lan (vlan 1), guest (vlan 2) and iot (vlan 3), and then bridge those to their corresponding wifi network. I started with this (working) configuration, without a vlan for the lan network: config interface 'lan' option device 'br-lan' option proto 'd…

VLAN tagging on ipq40xx (GL-B1300) no longer works

It was all working just until a few days ago in 19.07 with the switch configuration below, but now I can not connect to any LAN port with the latest build. There is this commit which might have something to do with this, but I do not know how that would have impacted things. Does anyone have any suggestions? config switch option name 'switch0' option reset '1' option enable_vlan '1' config switch_vlan option device 'switch0' option vlan '3' option vid '3' option ports '3 0t' config swi…

IPQ40xx Switch Config "Strangeness" (swconfig)

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…

VLAN Tagging for GL-B1300 - /etc/config/network configuration not propagated to internal switch

Hi all, I (new to openwrt, but a network professional) tried to use a GL-B1300 for home networking. I wanted to span more than one network internal (e.g. dmz, interal,...) and wanted to use a trunk (on port 3) up to my switch and split the networks there. After long tries I found out that neither editing /etc/config/network nor luci worked. My network file (port 3 of a GL-B1300 is the one on the opposite side of the power supply): config switch option name 'switch0' option res…

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

Continuing the discussion from Hardware advise (cheap, good support and available in Germany): @jeff how did you do it? I've been following the forum and occasionally looking at some of the threads on this issue but I couldn't find a comprehensive guide My goal is to move one of the yellow ports from the "lan" network / zone to the "guest" one; the wifi SSIDs are already split this way, but currently "guest" has no wired access. I could live with not using LUCI to achieve this goal …

[psherman]

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

[mk24]

The IPQ40xx was converted to DSA for version 23, and finally VLANs work properly. If you need tagged packets on the external ports you really need to upgrade to 23.05.2

[TriplEight]

Thanks for pointing this out, I realised I'm on 22 instead of 23! Flashing now. And also thanks for pointing to firmware selector. It would be really nice to have it linked in LuCi's footer, right near the current version or in the flash menu.
FWIW I took my image from GL-B1300 wiki page.

[psherman]

@TriplEight

I realised I'm on 22 instead of 23!

Not just on 22… you see on gl-inet’s non-standard version of OpenWrt which is massively different.

Be sure to allow the flash process to reset to defaults - do not try to keep settings or restore a backup. It will not be compatible.

@TriplEight

It would be really nice to have it linked in LuCi's footer, right near the current version or in the flash menu.

Worth adding to the feature requests section, although I’m not sure if it would be adopted.

@TriplEight

FWIW I took my image from GL-B1300 wiki page.

The oem firmware links are usually also included on the device pages for those who wish to revert back to vendor firmware. I’m guessing you grabbed that at some point, possibly by accident.