I tried to change the number of STATIC assigned IP in a VLAN 20 from 5 to 15.
Route 10 locks up , cant access internet or any local devices. Eventally coouple of minutes later I have access back - set static 15 to 5.
1 AP and 1 Switch offline - cant s, check access admin page, route10 has changed NATIVE VLAN changed from 1 to 20.
Have noticed this happen a number of times, usualy DHCP static IP assignment or Removing a device - The route 10 becomes unresonsive, if recovers great - NATIVE VLAN has changed on one or more ports, or needs are reboot or reset.
What firmware version are you running on Route10? There was an issue a few firmware versions ago where changing VLANs causes the ports to reset. Wondering if you are on a bit older firmware.
@Quackers We cannot reproduce this here. Can you give more information about what VLAN settings you are using so that we can try to reproduce your issue?
One possibility: There is a known issue right now where VLAN assignments using colors is NOT working correctly on Route10. They are working on the issue and I imagine it will be resolved quite soon. That being said, as a test would you be willing to change all colors on Route10 back to black, and try setting the VLANs manually on there instead?
There seems to be another UI bug. If you delete a vlan that was previously configured as a tagged member on a port, you can’t remove it anymore from the allowed vlans menu. It stays there forever unless you add the vlan again, remove it manually from all ports and then delete the vlan.
Going to devices → device → click port → native VLAN set to something other than default. Making any static IP changes causes it to go back to the default setting, thus losing DHCP for the devices connected via that port.
An observation: It seems that after a day or so the Native VLAN setting seems to stick. Not sure why that is, but if you set the Native VLAN then make any static IP assignments or change the icon of a device (basically any setting that uses the pop up it seems), the Native VLAN would swap back to Default.
same here, router is on 1.3v
I have saved several static IPs for devices, LAN4 supports NATIVE VLAN - it is set to Default, and Allowed, let’s say 150 and 1, i.e. NATIVE (by the way, it turned out that if there is no 1 in ALLOWED, the addressing from this network is not distributed).
I noticed that when I deleting a static IP from VLAN 150, the Native VLAN on the port can change to 150, cutting me off.
We still cannot reproduce anything similar to what is being described here. Can you please give OS, browser, and step-by-step instructions on how to reproduce the issue, even if it is a very short list, please?
Parts in this thread regarding overwriting the ports tagging from devices’ configuration is very similar to my experience reported in thread linked below:
Browser: arc
OS: windows 11 pro and MacOS Sequoia
Port 4 on Route10 SFP MM, this port have:
Native VLAN set Default
ALLOWED 1, 150
I Add wired, set serwer at valn150 and address 192.168.150.29, Mac adrress and I save this as static In devices card. Everything’s works ok.
When I delete this it’s cut me off on this port, and when I checked LAN4 via WiFi, APs are on LAN2 and LAN3, LAN4 has in NATIVE VLAN: 150
I use local controller also in VLAN150 maybe here is the problem.
Yes, the problem I described was on the Arc browser, so based on chromium. It was similar on safari.
However, I noticed that if I set the Native LAN port to e.g. 1 or anything else, just NOT Default, everything works as it should, Native LAN does not change.
I understand that Arc is based on Chromium, but based on Chromium is not quite the same as the actual Chromium browser. I use Vivaldi a lot myself, which is based on Chromium, but I sometimes experience bugs that exist on my browser but do not affect Chromium itself.
Thanks for confirming on Safari also.
I’m still looking for minimal steps to reproduce. Can you let me know if the following is accurate?
Configure a client override with a non-default VLAN
