# VLAN and port tagging confusion

**URL:** <https://forum.alta.inc/t/vlan-and-port-tagging-confusion/4439>\
**Category:** Routers\
**Tags:** vlan, bug-report\
**Created:** [January 23, 2025, 7:04pm UTC](https://forum.alta.inc/t/vlan-and-port-tagging-confusion/4439 "2025-01-23T19:04:28Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![ebuckland81](https://forum.alta.inc/user_avatar/forum.alta.inc/ebuckland81/32/3446_2.png) [@ebuckland81](https://forum.alta.inc/u/ebuckland81)\
**Post date:** [January 24, 2025, 8:19am UTC](https://forum.alta.inc/t/vlan-and-port-tagging-confusion/4439/13 "2025-01-24T08:19:58Z")

</div>

Yes, done! 👍

And, I was wondering if I should branch the following off to another topic to keep things organized:

Somewhat hidden in this topic was also the fact that updating a device connected to an Untagged port, associated to a specific VLAN, gets unintentionally (at least in my opinion) Tagged to that VLAN and Native VLAN set to Default.

E.g. if I set Native VLAN 90 and Allowed VLANs 90 for a specific port, it gets set to Native VLAN Default by saving the Device with a changed static IP (or changing from dynamic to static IP) even though the Device VLAN was blank before. Reverting from a static IP to dynamic IP (delete setting and leave field blank) does not overwrite the Native VLAN for the port.

---

_[View the full topic](https://forum.alta.inc/t/vlan-and-port-tagging-confusion/4439)._