I have read several of the vlan threads and have also run into the fact that other devices hard code VLAN 1. Would it be possible to have the vlan id number to be selectable for the WAN and DtD vlans?
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
Still VLAN 1 is the one used (hard coded) in other devices most of the time and a configurable WAN ID would help a lot.
Also your work arounds in vlan-renumbering are very complicated for the network neophyte trying to setup a remote node with only radio support.
It just seems that a WAN ID configuration would be helpful in a lot of situations.
VLAN 1 was used for internet dating back all the way to the Linksys devices first being used in mesh under BBHN, when we added support for pulling it out on Ubiquiti devices it made sense (to keep the code the same) to pull it out on VLAN 1 as well. In addition at the time no devices were seen that were had the design flaw of having a hardcoded vlan configuration so there was no 'warning' about future issues (some of the worst vlan switches we have seen since that decision that have VLAN 1 hard configured don't even support moving any of the ports off of VLAN1 which completely defeats the purpose of having a VLAN switch and renders the hardware useless even if we move the VLAN ID, these devices are essentially critically flawed and still would not work for use in fully managing nodes and traffic)
AREDN (like many corporate networks) is designed to be a self sufficient self contained network, any integration outside of that generally requires specialized integration and there is no default decision that can be right for every case. Pulling out the WAN and other VLAN's is no different.
In addition the ability to pull out the WAN has always been classified more as a convince not a core system component (if you have any dependency on internet its recommenced to remove it as internet will likely fail in most major disasters)
If your doing just a radio only site you don't even need any of the VLAN gear, a simple "dumb" switch will handle the connections integrating together.
As for "out of normal usage" that really depends as well. Getting into personal experience (which does not mean its global fact just means what I have experienced personally) one of the first things I was taught back in networking courses was to move the corporate infrastructure up into the high order ranges and leave the low ranges empty. I've been in many corporate networks over the years during my day job that have followed similar standards (I would say most actually don't use VLAN1 in corporate networks, only really small business networks would I say its common but again that is a personal experience and not a proven global fact)
Ultimately at the moment its not supported to change the WAN port VLAN, whether it will be in the future, I don't know, no one has opened any feature request ticket for it in bloodhound ( http://bloodhound.aredn.org/ ) so it hasn't gone through any sort of formal discussion to render an official opinion on it yet.