Windows Home shouldnt really exist. Microsoft trying to over segment as usual.
But I am not convinced thats Alex's problem unless he is trying to do the tagging from in windows itself.
If its done on the switch then the traffic for the other VLAN shouldnt even hit windows? I am not using Windows Home, but at the same time I dont even have VLAN tagging enabled on the network card which means windows has no knowledge of what VLAN it is using and as such wouldnt be filtering out other VLAN traffic.
When I tried to do a poor man guest network setup (without proper VLAN configuration) I had a FreeBSD VM with the same symptoms as Alex described.
Alex I attached some screenshots, my PC is on Port 2 untagged VLAN 3 (switch managed, windows has no vlan knowledge), the WAN port (repurposed as a LAN port) is where pfSense is connected. My other switch is also VLAN managed. All my client devices have no VLAN configuration, all untagged. VLAN3 normal private LAN, VLAN9 guest network with restrictions, VLAN1 no longer used as advised by pfSense devs to not use it.
On the RA vs DHCPv6 thing, I think it should have been just DHCP or static configuration the same as IPv4, people who have never used IPv6 before have to learn RA and how it works, which isnt a good thing, it adds a barrier and complexity to take up.
We seem to have gone from me trying to raise a point on the potential security benefits of having sticky IPv6 on every device, to why IPv6 isnt perfect.
What you guys think of it?