Not getting option to set VLAN ID for few of my NIC cards

[aaj7]

I want to set VLAN ID for my NIC cards and I am using windows 7 OS but in configuration page of some of the cards are not showing options to set VLAN ID. Could you please guide me for setting VLAN ID.
Following NIC cards I am using.
Broadcom NetXtreme 57xx Gigabit Controller
D-Link DGE-528T Gigabit Ethernet Adapter
Intel® Ehternet Connection I217-LM
Intel® Gigabit 4P I350-t Adapter

Out of which I am able to see VLAN ID option only for Broadcom

And for other I am not getting option to set VLAN ID

Are other three card supports VLAN ID configuration?
If they support then could you please guide me for the same.

Thanks,

 

[bill001g]

I suspect it is because you generally do not set the vlan on a physical interface on a end device it is generally set on some form of virtual interface. It is generally used when there are multiple vlans being carried on the cable and you need to identify the traffic.

To use this feature properly you need to understand the concept of tagged and untagged vlans and it is way to complex to explain in a forum. If you only have a single network connection then you do not need to put a number in the packets. The switch you connect it to will have been configured to assign the data to the proper vlan and if necessary when passing between switches add and remove any vlan tags.

The only time you really need to have a tag is if the physical nic is representing multiple virtual nic cards. The vlan tags are normally added and controlled by the software that is doing the virtualization. Windows does not have native support for this in most their non server versions so you will have to add software to get it in most cases.

I really don't see why you would ever put a vlan tag on physical interface since you run the risk of untagged traffic being send and certain types of traffic like spanning tree bpdu are always sent untagged.

 

[aaj7]

I suspect it is because you generally do not set the vlan on a physical interface on a end device it is generally set on some form of virtual interface. It is generally used when there are multiple vlans being carried on the cable and you need to identify the traffic.

To use this feature properly you need to understand the concept of tagged and untagged vlans and it is way to complex to explain in a forum. If you only have a single network connection then you do not need to put a number in the packets. The switch you connect it to will have been configured to assign the data to the proper vlan and if necessary when passing between switches add and remove any vlan tags.

The only time you really need to have a tag is if the physical nic is representing multiple virtual nic cards. The vlan tags are normally added and controlled by the software that is doing the virtualization. Windows does not have native support for this in most their non server versions so you will have to add software to get it in most cases.

I really don't see why you would ever put a vlan tag on physical interface since you run the risk of untagged traffic being send and certain types of traffic like spanning tree bpdu are always sent untagged.

Thanks for quick reply,
I understand your point but I am trying to build a small network in which I am having few devices and PC which are on same network (few devices are also having same IP addresses).
To build above network I am using few managed switch to create VLAN network between them. And these managed switches (using trunk port) and PC’s are connected using unmanaged switch.
Let say PC-01 want to communicate with device D1 which is on VLAN 77 then I have to configure PC-01 with VLAN 77 so that it can communicate with devices which are on VLAN 77.
But as I had mention earlier that with “Broadcom NetXtreme 57xx Gigabit Controller” I am able to set VLAN ID and able to communicate with devices which are on same VLAN.
But when I use Intel® Gigabit 4P I350-t Adapter I didn’t able to set VLAN ID on it.
It will be really helpful if you guide me for setting VLAN ID on “Intel® Gigabit 4P I350-t Adapter”.

 

[Kewlx25]

Here's a screenshot of my Intel i210 VLAN management page.

Intel210 VLAN

 

[bill001g]

What you are trying to do is extremely non standard. You might as well forget the fact that you have managed switches at all when you connect unmanged ones to them and pass tagged data though them.

The first problem you have is will the unmanaged switch even allow you to pass data though it with tags on it.

The next problem is you are dependent on the PC driver to get all this correct. What will it do when it gets packets with tags for other vlans. The biggest issue you have is there is always a untagged vlan. Some vlan is assigned to this even though there is not a number on it. What happens if the pc is assigning the vlan you set on the nic to be the untagged.

Normally when you run tags on nic you setup virtual nics to accomplish this.

I suspect you are going to get very inconsistent results because you not really using the feature the way you are suppose to.