|No. I mean that if I plug into a trunk port, as the majority of ports were on that seniors's residence project, I can configure my computer to be on any VLAN I choose or even all of them, if I so decide. As I mentioned, that site has both computers and VoIP phones (ignoring the residents VLAN). A port appears at a jack in the user's office. It doesn't matter which device, phone or computer is plugged in, it will be on the a appropriate network|
You do realize that one of the major purposes of VLAN's is security within your network. Your method totally negates that security and pretty much leaves your entire network wide open to someone with nefarious purpose.
Otherwise, I'd have to configure a port to access a specific VLAN and it would be capable of connecting to only one at a time.
I can understand why you might want to do this as an administrator but I still wouldn't myself. I'm not worried about the two minutes it takes to change a port assignment, and then change my IP to match the subnet. Unless you're using a single subnet in your network, you're still having to change IP wihen you change VLAN assignment on your NIC. So no matter what you do, you still have to change some settings somwhere and it's not hard or time consuming to do it my way.
1) I am aware that VLAN0 is not normally used, as it means there is in fact no VLAN tag used. VLAN0 is used on some equipment to denote the default LAN, that is no VLAN.
Granted I only have direct experience with Cisco, 3COM, Baystack, Nortel and now Avaya L2/L3 switches but on none of the aforementioned have I ever seen VLAN 0
The default in all the above was VLAN 1. On all the L2/3 switches I've worked with have VLAN 1 applied to all ports once they've been reset to factory defaults because it (VLAN 1) is the default VLAN
Another reason for VLANs on a computer might be a server that's supposed to be available on more than one VLAN or LAN. If plugged into a trunk port, with VLANs enabled, it could then be on all the configured VLANs.
We do have a couple servers here configured with trunk ports but those are special cases. They are VMWare servers that run multiple VM servers inside and utilize the Virtual switch that's made by VMWare to break traffic out on the physical server and send it to the appropriate Virtual server. These boxes have a quad interface card as well as dual onboard NIC's and we use all 6 of those interfaces combined in what's called a "LAG" (Link Aggregation Group)
Other than the VMware servers, none of the over 100 servers in our environment are connected to a trunk port. All are connected to whatever VLAN (subnet) they belong in) We have about 10 different "server" VLAN's (subnets) at this point in time.
James, what I'm about to say is not meant to be rude or insulting so please don't take it that way, but I have to say it.
I don't think you've ever had any real training on VLAN's. Or if you did, whomever trained you didn't know what they were doing.
As I said above, putting clients on trunk ports negates a large part of the reason for using VLAN's.......which is to say security. You might as well just leave all your switches set to factory defaults (VLAN 1) and put all your equipment in the same subnet for all the security you presently have in your network.
You would do well to get some better training on the use of VLAN tagging and apply a better methodology at work or some day your present method is going to really bite you in the butt....especially if you're using DHCP for client connections.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.