Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am bit new to VLAN. I want my two computers communicate through VLAN. I have following queries. As I am new to it my queries may be somewhat vague in some points. But i would like to hear from experts for my basic queries.

I have two PCs Computer A and Computer B in two different IP networks Network A and Network B Both my PC has windows OS installed.

  1. How to send a VLAN(#Number) tagged packet from Computer A to Computer B and how to detect and untag the packet at Computer B? (Please provide the steps for windows OS)
  2. For this action do I need to check if my ethernet card supports VLAN tagging/untagging? If yes how can I know if my card supports it or not?
  3. Is the VLAN applied for Wireless ethernet controllers also?
  4. Do I need any switch or router for this action?

Experts please given your inputs so that I can have a strong basic. If anyone can give some inputs how i can detect those VLAN in wireshirk, it will be helpful me also.


migration rejected from Mar 14 '15 at 0:11

This question came from our site for professional and enthusiast programmers. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as off-topic by HopelessN00b Mar 14 '15 at 0:11

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions on Server Fault must be about managing information technology systems in a business environment. Home and end-user computing questions may be asked on Super User, and questions about development, testing and development tools may be asked on Stack Overflow." – HopelessN00b
If this question can be reworded to fit the rules in the help center, please edit the question.

Maybe in superuser this question would fit properly? – Alfabravo Mar 10 '11 at 2:56

You're confusing layer 2 and layer 3 here.

You have two machines, each on a different IP (i.e. layer 3) network, this almost certainly means that they're on different segments (i.e. layer 2) with some form of routing (a L3 function) between them.

If you want them to be on the same VLAN (a L2 feature) they generally need to be on the same segment and that's configured by your switch (a L2 device). You'd need to reconfigure your switch, if possible, to ensure they're on the same VLAN/segment. Now this will mean that one or both of your machines will have to change IP but that's easy, at this point your have two machines on the same VLAN/segment, they can talk if their IP is configured correctly but crucially they don't need to be 'VLAN-aware', all of their IP traffic is managed in the default manner. This may be all that you're trying to do.

If you NEED them to be VLAN-aware what you need to do is the same as above but define the both machine's switch ports as being 'trunks' carrying the appropriate VLAN, then using the combination of Windows and NIC drivers (there is no one-instruction list for this, it varies based on version and adapter) you simply define a virtual NIC and tell it what VLAN to use. You they add IP information to these virtual NICs and it'll all just work. That said I'm not certain this is what you're trying to actually do so why not come back to us with more information including what you're actually trying to achieve here.


Generally, VLANs are set at the switch level to create a broadcast domain that can span a wider area. The ethernet card has nothing to do with it, it's all about how the switches route traffic.

That said, it would be helpful to know more about what you are trying to accomplish. There may be a better way to connect the two computers.


Not the answer you're looking for? Browse other questions tagged or ask your own question.