Actually you DO have it on a vlan. It's just vlan 1 if you haven't changed it. This is the default vlan for traffic on a vlan-aware device that hasn't been configured to do otherwise. Do what you like..just remember the rules of tagging/untagging/pvid below. You can keep it on vlan 1, just handle it on the other vlan-aware switches accordingly. (Where I used 5, you can use 1).I also note that I dont have my normal LAN on a VLAN (like you do vlan 5). Do you recommend I simply put my home network on a VLAN to make this easier down the line.
If a packet arrives at a port UNtagged, the packet will get tagged with the PVID vlan before moving along. Think of it as a default vlan for unlabeled (untagged) packets.
PVID is necessary because not all devices 'speak vlan' (tags). A vlan-aware switch needs to know what to do with a packet that isn't tagged. Computers and other end-user devices typically don't handle tagged packets. It is best to only expose these devices to UNtagged packets.
You really only have two choices... untagged (U) or tagged (T). Selecting "nothing" probably just means that that port won't be a member of that particular vlan. At least that's how it is on mine (Netgear).
When a port is tagged, packets sent out are tagged with the 802.1q vlan info added to the header. The receiving equipment of that packet is expected to know how to handle this. Vlan aware devices such as smart/managed switches, our STBs, and the ActionTec do. Computers, blu-ray players, etc usually don't, and will either ignore the tag, or drop the packet all together, or behave unpredictably. Hence why I said don't tag traffic to end-user devices like those.
When a port is untagged, packets sent out are not tagged with the 802.1q vlan info. The receiving equipment therefore has no idea what vlan, if any, it is supposed to be associated with. If that equipment is a vlan-aware switch, that packet will inherit that receiving port's PVID vlan ID before moving along. If the receiving equipment is not vlan-aware, then it accepts the packet as is. (this is what you want for computers, end-user typical devices).
Ports can of course be associated with multiple vlans, and those vlans can individually be either untagged or tagged on that port.
Got a headache yet?