Unsolved
This post is more than 5 years old
2 Posts
0
9368
August 28th, 2006 12:00
BCM5721 with vlan tagging
On a Dell PowerEdge 850, I'm trying to use the vlan tagging feature, unfortunately with no success.
This is the setup:
switch
|
hub -> other computer running TCPDUMP
|
PowerEdge also running TCPDUMP
Example scenario:
I'm sending out a DHCP request for vlan id 2. TCPDUMP (both on the PowerEdge and the other computer) indicates that a BOOTP/DHCP packet with vlan tag 2 is indeed being transmitted from the PowerEdge. The DHCP reply comes back, but according to the TCPDUMP on the PowerEdge it has no vlan tag. Because of this, the DHCP is not being processed by the vlan 2 interface on the PowerEdge.
However, the other computer running TCPDUMP shows that the DHCP reply DOES have a vlan tag 2. It seems that the vlan tagging is being stipped by the NIC on the PowerEdge for some reason.
The above scenario applies to all network traffic being transmitted from the PowerEdge to any vlan.
The OS I'm currently using is Debian Sarge 3.1 with kernel 2.6.16-2 (I've also tried Fedora Core 5 but with the same result)
The tool i use to configure vlan's is called "vconfig": a vlan (802.1q) configuration program. The required kernel module called "8021q" is loaded.
The concerning NIC is the onboard NIC of the PowerEdge 850: a Broadcom NetXtreme BCM5721. The required driver "tg3" is loaded. Below is an output from lspci -v.
0000:05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
Subsystem: Dell: Unknown device 01b6
Flags: bus master, fast devsel, latency 0, IRQ 21
Memory at fe5f0000 (64-bit, non-prefetchable)
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Capabilities: [d0] #10 [0001]
Does anyone has a clue how to fix this problem? Thanx.
This is the setup:
switch
|
hub -> other computer running TCPDUMP
|
PowerEdge also running TCPDUMP
Example scenario:
I'm sending out a DHCP request for vlan id 2. TCPDUMP (both on the PowerEdge and the other computer) indicates that a BOOTP/DHCP packet with vlan tag 2 is indeed being transmitted from the PowerEdge. The DHCP reply comes back, but according to the TCPDUMP on the PowerEdge it has no vlan tag. Because of this, the DHCP is not being processed by the vlan 2 interface on the PowerEdge.
However, the other computer running TCPDUMP shows that the DHCP reply DOES have a vlan tag 2. It seems that the vlan tagging is being stipped by the NIC on the PowerEdge for some reason.
The above scenario applies to all network traffic being transmitted from the PowerEdge to any vlan.
The OS I'm currently using is Debian Sarge 3.1 with kernel 2.6.16-2 (I've also tried Fedora Core 5 but with the same result)
The tool i use to configure vlan's is called "vconfig": a vlan (802.1q) configuration program. The required kernel module called "8021q" is loaded.
The concerning NIC is the onboard NIC of the PowerEdge 850: a Broadcom NetXtreme BCM5721. The required driver "tg3" is loaded. Below is an output from lspci -v.
0000:05:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5721 Gigabit Ethernet PCI Express (rev 11)
Subsystem: Dell: Unknown device 01b6
Flags: bus master, fast devsel, latency 0, IRQ 21
Memory at fe5f0000 (64-bit, non-prefetchable)
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
Capabilities: [58] Message Signalled Interrupts: 64bit+ Queue=0/3 Enable-
Capabilities: [d0] #10 [0001]
Does anyone has a clue how to fix this problem? Thanx.
0 events found
No Events found!
N_856
2 Posts
0
August 28th, 2006 13:00