wrote: Next steps:
I'm going to try to downgrade the firmware and setup the configuation again, and test.
I am pleasently surprised with a few things.
- The ER-X downgraded from 2.0.3 to 1.10.9 as easily as it upgraded.
- The downgrade kept the configuration in tact. I was expecting to get a factory defaut setup on boot. This was EPIC!
- Most importantaly IT WORKS!
Once the downgrade to 1.10.9 completed, I moved the cable from the access ports to the trunk ports and the link came up just as seemlessly as I expected it to two days ago.... yea.. .
Thanks again to @BuckeyeNet as without your reply to something that seemed not to be a problem, I never would have thought to downgrade the firmware.
To anyone reading this who is struggling with VLAN Trunking, the original post is a pretty good HowTo on setting up a trunk port, just ignore the fact that it wasn't working as that was a software issue.
Here are some additional notes:
The primary roadblocks I ran into are
- The initial setup from a factory default state will put the network on Switch0. This needs to be changed to a VLAN interface (a.k.a. VIF) attached to Switch0 and will look like "Switch0.200" for VLAN 200. Also called a Sub-Interface by some.
- Enable "VLAN Aware" on Switch0 and configure each port as appropriate for your network.
- pvid = Port VLAN ID (used for) Untagged frames = Access Port and is limited to one per port.
- vid = VLAN ID (used for) 802.1q Tagged Frames = Trunk Port and may have many (all?) configured on each Trunk port, seperated by commas.
Note that this is Ubiquti specific. I have 5 brands of managed switches and each one implements the configuration of 802.1q VLAN tagging slightly differently. This is the first time I've come accross the PVID being completely synonymous with an Untagged Port or an Access Port, let alone both. I think this does simplify things quite a bit.
