Two different VLANs on the same port

Does this sound feasible? I'm a bit scared of stuffing this up since the Backbone LAN is already in production (though not set up with a VLAN). If anyone has a different way to set up the two LANs, then any information is much appreciated!

Thanks, Håvard

If your wanting to do this with single nic'd hosts the switch needs to allow vlan trunking on the port. Frames are 'tagged' according to which vlan they're in. The most common tagging standard is "802.1q".

Is DLINK 3526 supports VLAN tagging.

If not then you can have LINUX box creating VLAN's and managing network and DLINK will be just a Swicth working edge.

CK

snipped-for-privacy@gmail.com wrote:

The hosts actually have to nic's but the other one is used for production "outwards" and needs to be left as it is. But if I understand you correctly it's just a matter of setting up the two VLAN's and specify that the connected ports are to be part of both VLANs? The nic drivers (Intel mostly) should be able to differentiate the received frames?

There would be some change at the nic / os to configure them for trunking dot1q encapsulation. Once that's done, yes, the nic / stack will differentiate between tagged frames but what's going on at the switch end? You need layer-3 switching / routiung to forward frames between the different vlans / subnets.

BernieM