You can configure a switch to use VLAN-tagging on each packet and thus send multiple VLAN's trough 1 port on the switch.
But this is normally done to connect to other VLAN switches wich in turn separate the traffic again.
The Software way
Theoreticly you could use an application wich separates the traffic according to these VLAN-tags and presents the OS with a virtual NIC for each VLAN.
However the only application wich I have ever seen that can do this is VMware ESX Server.
In VMware's case it is used to connect virtual machines to separated networks but do it over 1 physical connection. (Instead of giving each virtual machine its own real NIC)
(
http://www.vmware.com/products/vi/esx/#_tabfeatures )
You could configure VMware ESX server to present a virtual machine with multiple virtual NIC's each connected to a different VLAN. Then all these VLAN's can be trunked over the real NIC using vlan-tagging.
The downside to this all: You are now running your OS inside a virtual machine.
The hardware option
There are NIC's wich are VLAN aware. Example:
Every Intel NIC that can use the Intel PROset drive suite.
Problem is that this is not an option for you as you are using a laptop.
Screenshot:
This would do what you are asking however you need an Intel NIC with can use the PROset driver.
You can download the PROset driver free from the intel website.
The screenshot is from an onboard Intel PRO1000CT NIC on an 875P mobo.
So basicly every NIC Intel makes can do this.
To answer your question... no NIC (ethernet, wi-fi, ext) will ever be aware it's actually connected to VLAN instead of a LAN... it just won't know... that's the beauty of having a VLAN.
I think your still stuck in 1999... Time to wake up and catch up...
FYI: VLAN tagging is known as IEEE 802.1Q:
http://en.wikipedia.org/wiki/IEEE_802.1Q
However setting this all up is a manual process unless your switch also supports GVRP.
GVRP will "spread" the VLAN configuration to other switches making it an automatic process.
http://en.wikipedia.org/wiki/GVRP
Please quit bashing on the thread starter. His question does make sense.
If you needed to connect a OS to multiple VLAN's using only 1 NIC you would be asking thesame question.