VLAN Device Name changed?

[+DS_DV+]

Hi,

last time i created vlans was 2016/17.
in the age of IoT i created a new one.
but the Device name is

Code: [Select]

vlan01 instead of

Code: [Select]

re0_vlan60?

what did i do wrong? How can i fix that?


with kind regards

[Patrick M. Hausen]

Nothing to fix. This is how it's supposed to work now. You can always add a description that fits your needs.

[+DS_DV+]

but why?
there was no need for change and the old system was so much better.
the new one is just unnecessary confusing -.-

[Patrick M. Hausen]

The device names are limited in length and with the addition of QinQ (nested VLANs) the old scheme did not work anymore. Using a generic ID that is referenced somewhere else is a common data structure in software development called normalisation. It definitely was the right thing to do.

After initial complaints the UI was instantly improved and shows all the relevant information in the Assignments section, see screenshot for an example.

[franco]

but why?

Why not? Or: why do such unknown but intricate technicalities get in the way of your preference?


Cheers,
Franco

[SFC]

but why?

Why not? Or: why do such unknown but intricate technicalities get in the way of your preference?


Cheers,
Franco

Is there a reason we can't at least have the device ID match the vlan ID by default?  That would make scripting and visual identification a lot easier and is pretty common best practice in any network I've worked on.