I have a GL-MT6000 and I’ve been trying for 3 days to get VLAN trunking working using WAN port to an upstream managed switch. Currently I cannot even get the WAN port to get link to the upstream switch port. The primary resources I have been using are the OpenWRT wiki and various reddit subs. I had this working about a year ago and the resource I found most helpful was the following video from YT/OneMarcFifty:
however there are a number of comments in that video suggesting changes in recent versions of OpenWRT have invalidated the information in the video.
Anyone have an opinion as to the best resources for correctly configuring VLAN trunking?
What I recall is that that video was a bit outdated on even my last iteration that resulted in a successful deploy. I have yet to go through it again to see where it may be further out-dated.
Perhaps I need to start my own YT channel. It seems like Zero Mark Fifty – or whatever he called himself – has moved on.
It’s a side topic but I hard disagree. In doing this troubleshooting I have found lots of incorrect or ambiguously written advice. That video is perhaps the single most well-done bit of collateral I have found on the topic even if it is out-dated now.
There are many working examples of VLANs (even on your specific device) using DSA syntax on the forum. Search for those and/or ask specific questions to address where you are stuck - we can help you reach your goal.
And yet every time, people who watches these videos come here, with error prone configs and lots of questions and half baked answers.
For how long do we have now video education content? And for how long do we (as in human mankind) write down knowledge for async distribution?
Maybe its not obvious for you: But many people have NO intention watching a video if they had the same content in text form. Because then you can skip, fast read, use strg+f or / and so on.
You can just COPY text and point out extact positions you want to discuss...
Sure you are free to disagree, but you might should consider these hints.
And yet that video was the LEAST WRONG of any bit of collateral I have found.
You are wrapped around the axle on the method of delivery and not the quality of the content. Delivery mechanism is a DISTANT 2nd. And, fwiw, you can download transcripts from YouTube if you like. In fact, I do that and RAG it into an LLM quite frequently.
Dude! Its linux! We have IAC/CAC since literally forever!
Build your config, or generate them from templates, place them into an image-builder and get you complete firmware within 1 minute! Just flash and boot. Ready.
(And no, just forget about ansible. You don't need it for these deployments. You can generate config files from template with other tools too. Just generate the template and push them to the device. If this does not convince you, then maybe the fact that most of plastic routers can not handle a full python environment plus other unnecessary shizzle on their tiny rom.)
Just have a list of configs you have touched outside of git, and then use rsync/scp to transfer them?!
Have fun.
PS: I -- somehow -- find it funny, that you just become an expert in the topic within 10 minutes. How can you be sure, it is correct with what you have ended up?!?
PPS: You also have not described a single time WHAT excellently gave you confusion. And just in case you took the time to read the wiki, to point out whats wrong with current docs...
Lol. Bro, I have been doing config mgmt since the days where CFEngine was the only x-platform option and was considered alien technology. LuCI is pretty decent but there are situations where iterative adjustments with VCS and some pre-validation would be better UX.
I never claimed to be an expert. But I now know how to VLAN trunk the WAN port of an MT6000 specifically. Some of that comes down to the specifics of the hardware in the MT6000. So I can fill that specific gap in what is documented/not documented. A large part of that could probably be generalized to other kit. Hopefully.
The mt6000 is very popular and a whole variety of configs should be easily discovered on the forum. Feel free to write a wiki article if you think you can synthesize a good explanation.
Not sure if you figured out and things are working for you. The deal with Vlans is that everyone (every video out there) is trying to showing something that is outdate or ust plain wrong. I had my strugles with vlans on openwrt, but my main problem was following others and making the same mistakes. Openwrt is very flexible - Linux as a whole is - but that is the beaty of it.
coming back to help you with the vlans, plug in your system to one of the Ethernet ports, make sure that on is dedicated just to access your router (management port)
If you need assistance I can help you with pictures and videos. Ping me if you feel I can help.
It took me a bit to figure things out. But once you get it working is pretty cool.
Our experiences overlap. If I get some time to put together a guide I intend to these two things at least:
Make it very clear that it is for the GLI MT6000 only. Understanding the internal switches of each devices, in my experience, seems to be one of the most crucial aspects of getting the trunking to work as expected.
Post it here for review. I have probably 10-20 projects going at any one time and so I am not, specifically, an OpenWRT expert nor am I likely to be ever. So feedback will be important.
I am in the same boat! I have the setup mostly working, but still see issues. I've been through many (outdated) variant from forums/blogs/videos that claim to be the way to do it but only partially work and my network is still functional but still broken.
I know enough to be dangerous but not enough to stamp out these final issues.
For all of the people who have questions or issues with their DSA based vlan configurations, it’s easy enough to get a review and suggestions to improve/fix or validate the config. Just post the config (each person should make their own thread so that it doesn’t get confusing).
On the MT6000 the 2.5 Gb wan port all the way at the end is direct to the CPU as eth1. The other five ports are in the switch.
To instantiate a VLAN on a direct to CPU port, use the notation eth1.N where N is the VLAN tag number you want. This can be configured as the wan Device in Luci by scrolling all the way to the end of the list and typing eth1.35 (for 802.1q tag 35) in the field marked custom. You need to press enter to make the change permanent. If you just click off the field after typing it will not be saved.
It is also possible to put eth1 into a bridge with the other ports and use DSA inside that bridge, but that is unnecessarily complicated simply to have a tagged wan uplink.
Hello again, I understand one can be easily get lost when doing multiple things and configurations. See this article from Opensource is Awesome
Is all explain with pictures and details, it might look like a lot of information but is not - He covert all the details.
If that help please post it on the forum if additional help is needed - Just let me know.
It seems like Zero Mark Fifty – or whatever he called himself – has moved on.
