Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

VLAN order messed up on TL-WR842N-V2 and interface eth1.x won't come up.

See original GitHub issue

Hello!

Yesterday I created an LEDE image with imgbuilder for my TP-Link WR842N-V2 and the port order is totally messed up.

Here is what I found out how the ports are mapped:

 physical       swconfig       luci (*)
=======================================
     0              0           LAN4
     1              2           LAN2
     2              3           LAN1
     3              4           CPU
     4              1           LAN3
=======================================

(*) LuCI Master (git-16.339.77170-5127dd6)
    LEDE Reboot CURRENT r2400+38-a245772

As you can see, it looks like LUCI somehow reversed swconfig’s port order.

Besides that I also noticed that creating a new vlan with VID 4 will fail to create a new interface eth1.4, I had to do that manually in the config files by adding option ifname 'eth1.4' to a interface in /etc/config/network for it to show up

Issue Analytics

State:
Created 7 years ago
Comments:14 (7 by maintainers)

Top GitHub Comments

1reaction

rafwescommented, Jan 24, 2017

@cshoredaniel: I saw the patch has been integrated into LEDE. As soon as we get a release candidate of 17.01 with a clear upgrade path to the final release, I will test it. I’ll come back to you then.

0reactions

danielfdickinsoncommented, Feb 7, 2017

@rafwes Thanks for the report! You might want to discuss the vlan issue with upstream; I’ve noticed the same behaviour if one uses uci (not luci) to enable the switch but forget to enable the vlan. It probably make sense to open that as a new ‘feature request’ issue (for LuCI I mean; core thing isn’t really a bug but user error).