Opened 3 years ago

Last modified 3 years ago

#18261 new defect

TL-WR1043ND v1 - VLAN is broken when only assigned to tagged ports.

Reported by: alejandro_liu@… Owned by: developers
Priority: normal Milestone:
Component: kernel Version: Barrier Breaker 14.07
Keywords: Cc:


I am enclosing two files, "network.good" which contains a good working "/etc/config/network" file. And "network.bad", which contains a faulty configuration.

I have two vlans, VLAN3 and VLAN4.

VLAN3 is configured on ports: 0t 2 3 4 5t
VLAN4 is configured on ports: 0t 1t 5t

In this set-up, VLAN4 does not work.

If on the other hand, I configure VLAN4 on ports: 0t 1 5t

So that it is untagged on port 1, it works.

Attachments (2)

network.bad (835 bytes) - added by anonymous 3 years ago.
/etc/config/network - broken config
network.good (834 bytes) - added by alejandro_liu@… 3 years ago.
/etc/config/network - working config

Download all attachments as: .zip

Change History (5)

Changed 3 years ago by anonymous

/etc/config/network - broken config

Changed 3 years ago by alejandro_liu@…

/etc/config/network - working config

comment:1 Changed 3 years ago by alejandro_liu@…

I would like to add more details on this.

I am using a TL-WR1043ND v1. On port 0 I connect to another router. I had VLAN3 and VLAN4 running on it (both tagged). That did not work. I was not able to ping from the other router the TL-WR1043ND VLAN4 address.

So what I did is added VLAN4 to port 1 (untagged), removing VLAN3 for port 1, and that made VLAN4 working again. The TL-WR1043ND, would answer to pings.

If I on the other hand, went and make port 1 tagged, then that made VLAN4 stop working. Pings are ignored.

In all this, the other router configuration did not change at all. The only thing that changes is port 1 tagged/untagged status. If port 1 is tagged, VLAN4 does not work. If port 1 is untagged, VLAN4 works.

Looks like VLAN configuration only gets apply for VLANs that have untagged ports. If all the ports on that VLAN are tagged, it does not work.

I had a similar configuration with Backfire (10.03/10.03.1) which would work. Starting with Attitude Adjustment (12.09) it seem to have stopped working.

comment:2 Changed 3 years ago by alejandro_liu@…

Looking at /ticket/18242.html, the workaround for this is to set "enable_vlan4k" to 1.

This used to work properly with Backfire (with vlan4k = 0).

comment:3 Changed 3 years ago by anonymous

See #18242.

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.