Many months ago, I set up VLANs for the various things stuck on my LAN separating video and home automation. The full conversation for all devices has not been completed.

Yesterday, I did an update all modules as I was behind a bit on PG3. I think there were some minor updates to IoX. Anyway, after a reboot, my eisy could not be found! Logged in via the cloud and found my IP was now in one of my VLANs!! Weird! It was always in the default VLAN prior to this reboot and it has been updated and rebooted several times since the VLANs were created and my switches configured. The eisy is still in the defualt VLAN port. Again, it hasn't changed in several prior reboots but suddenly it deceided it liked the Video VLAN!!

Any thoughts on how this occurred and where I add VLAN assignments to the eisy! It's fine where it is for now, but this kind of freaked me out.

Thanks!

John

Edited June 22Jun 22 by johnjces

The network router / switch decides that. Devices get their vlan assignment during authentication:

• Wireless devices are assigned and routed when they have successfully authenticated

• ET ports assignments and routes are set by the router or managed switch they are plugged in to, and the device gets what it gets from that network side assignment

My managed switches were all set up well but in some linux distros you can create VLAN interface using connection manager. Just wondering if it could be set in the eisy ...but in any event, my managed switch went wonky...failing and it has died. Ports went weird and now VPN is even down! Argh.

Oh well!
John

What you are referring to is VLAN tagging. It can be done on the client side, but that would usually only be done on network infrastructure devices or servers. Eiher way, the eISY does not support VLAN tagging on ingress or egress.

Did your network switch perhaps revert the eISY port to the native VLAN? It may also be reffered to as a trunk port on the network switch in which case most implementations would often send a native VLAN as untagged traffic. Bottom line- this problem almost has to be on the network infrastructure side.

@TheRydad Very true and no it didn't revert to the native or default VLAN and now the switch is dead.

The point of my post was to find out if the eISY supported VLAN tagging. I don't think that was very clear and then to find out if somehow after the reboot after an update the eISY got tagged in the update or by mistake. But alas it was not my eisy...

Edited June 24Jun 24 by johnjces