Background
A little while back I purchased a Devolo MAGIC 2 home kit (one single port, non-WiFi adapter and two dual-port WiFi-enabled adapters) - these worked perfectly fine (and continue to do so). I make extensive use of VLANs on my network - I created a VLAN on my (Linux) laptop and connected to one of the adapters via Ethernet and it passed the tagged VLAN traffic to the switch as expected.
Current Issue
Since the MAGIC 2 line lacks "business" features (like the ability to map SSIDs to VLANs), I decided to a) expand my powerline network by purchasing another MAGIC 2 WiFi unit and b) purchase a MikroTik hAP AC2 to use as a VLAN-supporting AP (connected to the new Devolo adapter via Ethernet, in place of my laptop).
The Devolo unit I purchased was one of new "MAGIC 2 WiFi next" units (the originals didn't seem to be in stock anywhere and the newer units are now sporting MIMO-enabled WiFi). I hooked everything up (after configuring the SSID and VLAN trunk port on the MikroTik) and couldn't get an IP address from my router. For reference, I plugged the MikroTik into one of the original MAGIC 2 WiFi units and it worked perfectly fine - address acquired via DHCP for the specific VLAN, passed IP traffic as expected.
I then went back to the new MAGIC 2 WiFi next just to double-check and nope...will pass un-tagged traffic perfectly well via WiFi and Ethernet, but tagged Ethernet traffic is a no-no.
TLDR
The newer Devolo MAGIC 2 next powerline adapters do NOT pass VLAN-tagged Ethernet traffic via their on-board Ethernet interface. This maybe either a change in the Ethernet chip being used (possible but hard to believe - every modern 1Gb/s Ethernet chip should pass tagged VLAN traffic out of the box) or a change in the onboard firmware (which is far more likely, my WiFi next unit is running 5.6.0, while the original MAGIC 2 WiFi units are running 5.4.0).
There is an update to 5.6.1 available for the original MAGIC 2 WiFi units but I don't think I'll be deploying it any time soon...
A little while back I purchased a Devolo MAGIC 2 home kit (one single port, non-WiFi adapter and two dual-port WiFi-enabled adapters) - these worked perfectly fine (and continue to do so). I make extensive use of VLANs on my network - I created a VLAN on my (Linux) laptop and connected to one of the adapters via Ethernet and it passed the tagged VLAN traffic to the switch as expected.
Current Issue
Since the MAGIC 2 line lacks "business" features (like the ability to map SSIDs to VLANs), I decided to a) expand my powerline network by purchasing another MAGIC 2 WiFi unit and b) purchase a MikroTik hAP AC2 to use as a VLAN-supporting AP (connected to the new Devolo adapter via Ethernet, in place of my laptop).
The Devolo unit I purchased was one of new "MAGIC 2 WiFi next" units (the originals didn't seem to be in stock anywhere and the newer units are now sporting MIMO-enabled WiFi). I hooked everything up (after configuring the SSID and VLAN trunk port on the MikroTik) and couldn't get an IP address from my router. For reference, I plugged the MikroTik into one of the original MAGIC 2 WiFi units and it worked perfectly fine - address acquired via DHCP for the specific VLAN, passed IP traffic as expected.
I then went back to the new MAGIC 2 WiFi next just to double-check and nope...will pass un-tagged traffic perfectly well via WiFi and Ethernet, but tagged Ethernet traffic is a no-no.
TLDR
The newer Devolo MAGIC 2 next powerline adapters do NOT pass VLAN-tagged Ethernet traffic via their on-board Ethernet interface. This maybe either a change in the Ethernet chip being used (possible but hard to believe - every modern 1Gb/s Ethernet chip should pass tagged VLAN traffic out of the box) or a change in the onboard firmware (which is far more likely, my WiFi next unit is running 5.6.0, while the original MAGIC 2 WiFi units are running 5.4.0).
There is an update to 5.6.1 available for the original MAGIC 2 WiFi units but I don't think I'll be deploying it any time soon...