On Fri, 1 Apr 2011, Jon wrote:
> Hello List, > > I am trying to get a 82546G dual NIC Intel card to do bonding with vlans > and a bridge for a xen server. I would like to be able to setup a bridge > and then assign it to a VM(domU) so it is on a specific VLAN. > > I have bonded eth0 and eth1 to bond0 and have created a bridge and did you create the bridge in dom0 or ??? > assigned the vlan to the bridge. When I try to send data through the > bridge and I am using tcpdump to sniff the wire I cannot see the VLAN > tag in the packet. using tcpdump in the virtual machine or the dom0 or domU? > I updated the driver to 8.0.30-NAPI because I had read that HW > acceleration on the card with earlier drivers was stripping the VLAN tag > off of the packet. But I am still not seeing the VLAN tag after updating > the driver. This is the kind of thing that usually has an issue (stacking of different virtual interfaces) and does seem like it is just starting to work correctly in the latest kernels. That said I have no idea if it works in el5 or not as I haven't directly tried it. > At this point I am lost and am not sure what to try next. Does this card > support VLAN tagging? From everything I have read it does but can absolutely yes, it supports hardware vlan tag insertion and stripping. One thing to note is that the hardware actually strips the vlan from the packet data when hardware offload is enabled. > someone who knows for sure confirm that for me please? Is there > something I am not understanding on why I am not seeing the tag? I have > tried to ping, dhcp, ssh and nothing ever shows the VLAN in the packet. but does the traffic over the vlan work? without tcpdump enabled, preferably. The model we're trying to move to matches upstream's declaration that when promisc mode is enabled (on the physical device) the vlan tag is not stripped in hardware. did you try tcpdump on eth0 or eth1? Why are you using bonding to create a bridge? a bridge connects two networks through two devices, and a bond makes two devices connect to a single network. They seem opposed. > > > Any help would be greatly appreciated!! :) > > Jon > > > > CentOS 5.5 > 2.6.18-194.32.1.el5xen #1 SMP > xen 3.1 > tcpdump version 3.9.4 > libpcap version 0.9.4 > > ifcfg-bond0: > > DEVICE=bond0 > BOOTPROTO=none > BONDING_OPTS="mode=1 miimon=100" > ONBOOT=yes > > > ifcfg-bond0.5: > > DEVICE=bond0.5 > BOOTPROTO=none > ONBOOT=yes > VLAN=yes > BRIDGE=xenbr5 > > > ifcfg-eth0: > > # Intel Corporation 82546GB Gigabit Ethernet Controller > DEVICE=eth0 > BOOTPROTO=none > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > ISALIAS=no > > > ifcfg-eth1: > > # Intel Corporation 82546GB Gigabit Ethernet Controller > DEVICE=eth1 > BOOTPROTO=none > ONBOOT=yes > MASTER=bond0 > SLAVE=yes > ISALIAS=no > > > ifcfg-xenbr5: > > DEVICE=xenbr5 > BOOTPROTO=static > IPADDR=192.168.6.2 > NETMASK=255.255.255.0 > ONBOOT=yes > TYPE=Bridge > > > lspci -vv: > > 01:06.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet > Controller (rev 03) > Subsystem: IBM Unknown device 0289 > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- > Stepping- SERR+ FastB2B- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- > Latency: 64 (63750ns min), Cache Line Size: 64 bytes > Interrupt: pin B routed to IRQ 20 > Region 0: Memory at f9ee0000 (64-bit, non-prefetchable) [size=128K] > Region 2: Memory at f9e80000 (64-bit, non-prefetchable) [size=256K] > Region 4: I/O ports at c800 [size=64] > Expansion ROM at f0040000 [disabled] [size=256K] > Capabilities: [dc] Power Management version 2 > Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA > PME(D0+,D1-,D2-,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=0 DScale=1 PME- > Capabilities: [e4] PCI-X non-bridge device > Command: DPERE- ERO+ RBC=512 OST=1 > Status: Dev=00:00.1 64bit+ 133MHz+ SCD- USC- DC=simple > DMMRBC=2048 DMOST=1 DMCRS=16 RSCEM- 266MHz- 533MHz- > > > modinfo e1000: > > filename: > /lib/modules/2.6.18-194.32.1.el5xen/kernel/drivers/net/e1000/e1000.ko > version: 8.0.30-NAPI > license: GPL > description: Intel(R) PRO/1000 Network Driver > author: Intel Corporation, <[email protected]> > srcversion: 1D436A0D02B18BE145D2AE1 > alias: pci:v00008086d000010B5sv*sd*bc*sc*i* > alias: pci:v00008086d00001099sv*sd*bc*sc*i* > alias: pci:v00008086d0000108Asv*sd*bc*sc*i* > alias: pci:v00008086d0000107Csv*sd*bc*sc*i* > alias: pci:v00008086d0000107Bsv*sd*bc*sc*i* > alias: pci:v00008086d0000107Asv*sd*bc*sc*i* > alias: pci:v00008086d00001079sv*sd*bc*sc*i* > alias: pci:v00008086d00001078sv*sd*bc*sc*i* > alias: pci:v00008086d00001077sv*sd*bc*sc*i* > alias: pci:v00008086d00001076sv*sd*bc*sc*i* > alias: pci:v00008086d00001075sv*sd*bc*sc*i* > alias: pci:v00008086d00001028sv*sd*bc*sc*i* > alias: pci:v00008086d00001027sv*sd*bc*sc*i* > alias: pci:v00008086d00001026sv*sd*bc*sc*i* > alias: pci:v00008086d0000101Esv*sd*bc*sc*i* > alias: pci:v00008086d0000101Dsv*sd*bc*sc*i* > alias: pci:v00008086d0000101Asv*sd*bc*sc*i* > alias: pci:v00008086d00001019sv*sd*bc*sc*i* > alias: pci:v00008086d00001018sv*sd*bc*sc*i* > alias: pci:v00008086d00001017sv*sd*bc*sc*i* > alias: pci:v00008086d00001016sv*sd*bc*sc*i* > alias: pci:v00008086d00001015sv*sd*bc*sc*i* > alias: pci:v00008086d00001014sv*sd*bc*sc*i* > alias: pci:v00008086d00001013sv*sd*bc*sc*i* > alias: pci:v00008086d00001012sv*sd*bc*sc*i* > alias: pci:v00008086d00001011sv*sd*bc*sc*i* > alias: pci:v00008086d00001010sv*sd*bc*sc*i* > alias: pci:v00008086d0000100Fsv*sd*bc*sc*i* > alias: pci:v00008086d0000100Esv*sd*bc*sc*i* > alias: pci:v00008086d0000100Dsv*sd*bc*sc*i* > alias: pci:v00008086d0000100Csv*sd*bc*sc*i* > alias: pci:v00008086d00001009sv*sd*bc*sc*i* > alias: pci:v00008086d00001008sv*sd*bc*sc*i* > alias: pci:v00008086d00001004sv*sd*bc*sc*i* > alias: pci:v00008086d00001001sv*sd*bc*sc*i* > alias: pci:v00008086d00001000sv*sd*bc*sc*i* > depends: 8021q > vermagic: 2.6.18-194.32.1.el5xen SMP mod_unload gcc-4.1 > parm: TxDescriptors:Number of transmit descriptors (array of int) > parm: TxDescPower:Binary exponential size (2^X) of each > transmit descriptor (array of int) > parm: RxDescriptors:Number of receive descriptors (array of int) > parm: TxDescriptorStep:Transmit Descriptor Step (array of int) > parm: Speed:Speed setting (array of int) > parm: Duplex:Duplex setting (array of int) > parm: AutoNeg:Advertised auto-negotiation setting (array of int) > parm: FlowControl:Flow Control setting (array of int) > parm: XsumRX:Disable or enable Receive Checksum offload (array > of int) > parm: TxIntDelay:Transmit Interrupt Delay (array of int) > parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array > of int) > parm: RxIntDelay:Receive Interrupt Delay (array of int) > parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of > int) > parm: InterruptThrottleRate:Interrupt Throttling Rate (array > of int) > parm: SmartPowerDownEnable:Enable PHY smart power down (array > of int) > parm: copybreak:Maximum size of packet that is copied to a new > buffer on receive (uint) > parm: ignore_64bit_dma:Ignore 64-bit DMA (DAC) capability (int) > parm: debug:Debug level (0=none,...,16=all) (int) > > ------------------------------------------------------------------------------ > Create and publish websites with WebMatrix > Use the most popular FREE web apps or write code yourself; > WebMatrix provides all the features you need to develop and > publish your website. http://p.sf.net/sfu/ms-webmatrix-sf > _______________________________________________ > E1000-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/e1000-devel > To learn more about Intel® Ethernet, visit > http://communities.intel.com/community/wired > ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf _______________________________________________ E1000-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
