Ethernet LAN Question about VLAN tagging for packets

Bookmark this page:  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Question about VLAN tagging for packets mohamad.ridha 03-21-07
Posted by on March 21, 2007, 2:43 pm
Please log in for more thread options


Hi,

Does anyone know how to resolve the following situation:

I have a VLAN switch that has three ports: port 1 is connected to
network uplink, port 2 is connected to a server, port 3 is connected
to a desktop.
I'd like to make the following scenario to work:

In preboot environment (EFI), I need to use an application from the
desktop to send packets to the server (port 2) and use another
application to send packets to network uplink (port 1).
In OS environment, all packets should send packets to network uplink
(port 1).
To support this scenario, what should the switch be configured?
Can using PVID resolve this problem, for example we set PVID port
1="1", PVID port 2="2", and PVID port 3="1" or "2", so packets
arrived at port 3 will be tagged with its PVID number (either "1" or
"2") by the switch and forwarded to port which has the same PVID
number (but this won't work since port 3 need to be able to forward
packets to port 1 and port 2 depending on the application.

Thanks so much for the help.


Posted by Albert Manfredi on March 21, 2007, 5:53 pm
Please log in for more thread options



> I have a VLAN switch that has three ports: port 1 is connected to
> network uplink, port 2 is connected to a server, port 3 is connected
> to a desktop.
> I'd like to make the following scenario to work:
>
> In preboot environment (EFI), I need to use an application from the
> desktop to send packets to the server (port 2) and use another
> application to send packets to network uplink (port 1).
> In OS environment, all packets should send packets to network uplink
> (port 1).
> To support this scenario, what should the switch be configured?
> Can using PVID resolve this problem, for example we set PVID port
> 1="1", PVID port 2="2", and PVID port 3="1" or "2", so packets
> arrived at port 3 will be tagged with its PVID number (either "1" or
> "2") by the switch and forwarded to port which has the same PVID
> number (but this won't work since port 3 need to be able to forward
> packets to port 1 and port 2 depending on the application.

Why is there any need for VLANs in what you describe? Why not simply
forget about using VLANs? In both of your conditions, I don't see where
VLANs are needed.

Also, if you do want to add VLANs, best not to use VID of 1, since some
switches use VID 1 for non-VLAN traffic.

Bert


Posted by glen herrmannsfeldt on March 21, 2007, 8:05 pm
Please log in for more thread options


mohamad.ridha@intel.com wrote:
(snip)

> To support this scenario, what should the switch be configured?
> Can using PVID resolve this problem, for example we set PVID port
> 1="1", PVID port 2="2", and PVID port 3="1" or "2", so packets
> arrived at port 3 will be tagged with its PVID number (either "1" or
> "2") by the switch and forwarded to port which has the same PVID
> number (but this won't work since port 3 need to be able to forward
> packets to port 1 and port 2 depending on the application.

I would consider what might happen with non-virtual LANs.

VLANs should each be like a separate physical net, for IP that
usually means a different (sub)net. That would usually mean two
physical ports for host 3, though if it is VLAN aware it might
be able to do two logical ports on one physical port. That is,
the host should tag the ports based on routing table destination.

-- glen


Posted by on March 23, 2007, 8:25 am
Please log in for more thread options


> mohamad.ri...@intel.com wrote:
>
> (snip)
>
> > To support this scenario, what should the switch be configured?
> > Can using PVID resolve this problem, for example we set PVID port
> > 1="1", PVID port 2="2", and PVID port 3="1" or "2", so packets
> > arrived at port 3 will be tagged with its PVID number (either "1" or
> > "2") by the switch and forwarded to port which has the same PVID
> > number (but this won't work since port 3 need to be able to forward
> > packets to port 1 and port 2 depending on the application.
>
> I would consider what might happen with non-virtual LANs.
>
> VLANs should each be like a separate physical net, for IP that
> usually means a different (sub)net. That would usually mean two
> physical ports for host 3, though if it is VLAN aware it might
> be able to do two logical ports on one physical port. That is,
> the host should tag the ports based on routing table destination.
>
> -- glen

If you have a Layer 2 switch it should already take care of your
issue. A layer 2switch will know what port the server is on. Unless
I'm missing something I also don't see what the vlan is doing for you
in this example.


Posted by BernieM on March 24, 2007, 11:11 pm
Please log in for more thread options



> Hi,
>
> Does anyone know how to resolve the following situation:
>
> I have a VLAN switch that has three ports: port 1 is connected to
> network uplink, port 2 is connected to a server, port 3 is connected
> to a desktop.
> I'd like to make the following scenario to work:
>
> In preboot environment (EFI), I need to use an application from the
> desktop to send packets to the server (port 2) and use another
> application to send packets to network uplink (port 1).
> In OS environment, all packets should send packets to network uplink
> (port 1).
> To support this scenario, what should the switch be configured?
> Can using PVID resolve this problem, for example we set PVID port
> 1="1", PVID port 2="2", and PVID port 3="1" or "2", so packets
> arrived at port 3 will be tagged with its PVID number (either "1" or
> "2") by the switch and forwarded to port which has the same PVID
> number (but this won't work since port 3 need to be able to forward
> packets to port 1 and port 2 depending on the application.
>
> Thanks so much for the help.
>

Unless it's a layer-3 switch aka router, hosts in different vlans cannot
contact each other. One solution is to have a trunk link to the server and
have the server in both the network uplink vlan and the pc vlan. Then the
pc can communicate with the server and the server can communicate with the
network uplink. if you want the pc to communicate with whatever's at the
other end of the network uplink then configure routing on the server and
configure the pc to use it as it's default gateway.

BernieM



Similar ThreadsPosted
Question about VLAN tagging for packets March 21, 2007, 2:43 pm
Priority Tagging and VLAN Tags March 28, 2006, 11:25 am
Promiscuous Mode on Sun BGE Network Driver Drops VLAN-tagged Packets April 20, 2005, 2:02 pm
Tagging TOS to 802.1P COS March 18, 2008, 5:14 am
VLAN question... August 3, 2006, 10:24 am
Re: Restart: VLAN question... August 26, 2006, 10:50 am
VLAN/Broadcast Question March 10, 2007, 2:50 pm
Ethereal Decoding 802.11 WEP Packets December 8, 2004, 5:01 pm
ping corrupted packets February 21, 2005, 12:19 pm
DVMRP report packets September 24, 2006, 10:25 pm
Seeing Packets on an Ethernet Port That Should Not Be There October 4, 2007, 11:54 pm
Using Jumbo packets in gigabit ethernet July 19, 2004, 1:08 am
Dropped packets/broken TCP connections August 23, 2006, 9:48 am
arbitrary packets on an ethernet network January 19, 2007, 5:11 am
Connection to Switch Drops Packets But Hub Works July 10, 2007, 1:36 am