In our lab, we have static IPs assigned to everything. We have less than 20 devices, some physical and some virtual on ESXi, ranging from servers to android tablets. Everything is wired ethernet. There are 3 VLANs on the switch. Our virtual linux machines work fine because the vSwitch seems to apply the tags, but our physical Linux machines need to have their ifcfg-eth0 interface changed to be ifcfg-eth0.20 in order to participate with the network. Our Android tablet with ethernet dongle cannot create this new ethernet config for vlan tagging the way linux does, due to it not being rooted and there are no tools for wired vlan setups as far as I know. (It is Android 4.0.)
Shouldn't the switch be responsible for tagging the network traffic based on a machine's subnet and the ports it is plugged into? Why do the physical Window's machines seem to handle the VLAN without extra setup, but the Linux physical machines need a new interface config to see traffic? Shouldn't the physical switch be able to do this the same way the vSwitch is doing it for our Virtual machines?
I just want the Android device to consume services from the VMs and Windows machines, but I can't even ping them or the gateway because the VLAN can't be set manually on the device.