It’s normal for a switch to strip a vlan tag when it sends a packet out, so that the endpoint doesn’t have to support vlans. Don’t worry about that. As far as the endpoint is concerned, it’s just normal subnetting.
okay that's what I thought
When it’s on the other vlan, can you even ping it? When you check the packet capture, can you see the ping and response? Where does it get dropped?
if I try to ping it it doesn't answer, the unifi logs do show that the packages have been forwarded to the subnet. If I use netcat to open a port on the other device it receives the connection request, but the NAS doesn't recognize it. Maybe I have to do some Wiresharking on a mirror port to see what exactly comes back, hoped I could get around it
doesn't the switch terminate any VLAN tagging at the port? so if I add the VLAN to the DSM configuration it doesn't receive any tagged packages and refuses them?
with all the other devices in the IoT subnet it works with setting the VLAN on the port of the switch. If I check back on the unifi site, I found this:
if I understand that in combination with your comment correctly: I set the native VLAN to
83
so everything tagged with83
is correctly forwarded to the NAS and accepted there, stuff tagged with1
are non native, the tag stays on and the NAS doesn't accept it?But that would make the Synology NAS quite hard to use in any corporate setting with multiple VLANs which need to interconnect and why does it work the other way around? while being in the default net
1
it does accept stuff from VLAN83
which would mean, I can't put it in the IoT net?