yes
Thank you. So the result is that the Native VLAN for the interface this client is connected to suddenly switches to the same VID from step 1?
I hope to have some time today to work through some scenarios and see which are surprising like this.
yes
Iām finding that step 2 is unnecessary, and if you use the Reset button in the client configuration then the Native VLAN reverts as expected.
2 Likes
Hi, yes, below is my experience as well. If Device VLAN is set to non-blank, while also updating other Device settings, the corresponding port/interface Native VLAN is maintained.
The opposite, when there is a blank VLAN field in the Device settings, while also updating other Device settings, always leads to the corresponding port/interface getting its Native VLAN erroneously (my opinion) reverted to Default. I suggest that the problem, code-wise, is that empty/blank VLAN is treated as Default instead of empty/blank when passing settings to the port/interface.
This is the issue that I have raised elsewhere.
Yes, that is the case. Native VLAN reverts to Native VLAN Default.
I havenāt reviewed other steps described here, yet. But I received the Control the other day, which is waiting for unboxing and setup. So I might be up for the same issues as well.
Edit: Just adding that the above experiences originally applied to Chrome on Android. But I also installed and tested, with the same experiences, on Opera, Dolphin, Brave and Firefox browsers on Android.
We are working to improve this experience and reduce the surprising nature of the override behavior.
1 Like
I literally just received your product but my experience has been poor so far. The very first thing I did after setup was change the default vlan ip range to fit my existing network so I dont have to go around and change all my static IPās but the entire appliance and app crash. The router no longer passes network traffic, does not give IPās, and the app crashes instantly when you try to view or edit the vlan settings again. A factory reset restores access but even at that, the router is unstable and unreliable at best. I am going to give benefit of the doubt and return this router for a replacement but reading the forums here, it sounds like this is a fatal flaw in the device that has not been fixed and if so, I will need to find an alternative router. Also, just for testing purposes, I didnt change the vlan settings, I simply connected it up with a single laptop, my speeds were 25% of my available internet bandwidth and a few minutes after that speed test the device stopped detecting the laptop being connected directly to it entirely. The system then froze and nothing could be done, no menu could be opened from the app, until it is manually reset.
1 Like
@yinyang30, Iām sorry to hear of such a rough experience. 
Iām sure that the aways helpful support will dig in and help you out if you reach out a hand. 
1 Like
I hope so, the hardware seems great, the company seems good, and it looks like it would fit my needs perfectly. I understand thatās a new product and it has some bugs but I feel like changing the IP address should be the most basic of things and shouldnāt brick the device. I will certainly reach out for more direct support when the replacement devices arrives. 
1 Like
Weāll be more than happy to investigate the issues you experienced. Please open a new thread describing the problems you run into, or reach out to support@alta.inc. I havenāt heard of the app crashing when editing the VLAN settings either. Could you tell us which platform youāre using? And confirm if the issue persists through a web browser at https://manage.alta.inc?
This, problem on surprising override of VLAN, might now have been solved by an update to Control(manage.alta.inc) today. 
Donāt know whether the same applies to the hardware Control device as I am yet to unbox and set it up. 
Have a look and see if it works as intended for you.
Not seeing any published release notes.
1 Like
@rutman286, me neither. I only see the updated features.