mathison

Consider this toggle between a preset with Tagged dtd vlan and untagged local lan on interfaces. Provides a fall back scenario to access the node. Ubiquity provides the configuration option...

Im not suggesting all 3 VLANs be introduce on all of the ports!!! That's I feel that for a novice user without any background on configuring vlans, would be exposed...

https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial GUI work fine in the main line build...

I concur, a toggle for dtd for each port. would be simple... Its counter to the way the config handles this tho... Ports get assigned to vlans not vlans to...

The checkbox table? would be great! Consider a 3 way slider |off/T/U| for the WAN. List ports 'wan.2' for DtD helps me integrate with my core switches!

A few notes... @aanon4 I Like the idea! consider adding another column for "tagged ID" #'s. That places all the config in one table. Keep all this stuff collocated in...

This is how I really need a node configured... 

plug-in works! but... When the WAN VLAN number set (in my case 1) the plug in doesn't recognize the vlan # for the WAN. It still thinks WAN is untagged....

If I can use VLAN id 1 like another node do? Should I start using another vlan id at the hub?

interesting. It would make use of this, as long as: -Can be enable and disabled after install -Provides a portal for clients connecting to a node in AP mode. -option...