From: Evan Bigall <evan.bigall@scalent.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Problem with VLANs on tg3 NICs
Date: Thu, 18 Jan 2007 16:46:48 -0500 [thread overview]
Message-ID: <45AFEAC8.7050904@scalent.com> (raw)
In-Reply-To: <8A87A9A84C201449A0C56B728ACF491E04F1AA@liverpoolst.ad.cl.cam.ac.uk>
[-- Attachment #1.1: Type: text/plain, Size: 6089 bytes --]
Ian Pratt wrote:
>>I have 3 machines,
>> T60 thinkpad with e1000 NIC
>> Dell PowerEdge 2950 with bnx2 NIC
>> HP DL360 G4P with tg3 NIC
>>All running xen 3.03 / 2.6.16.29-xen
>>
>>I have a netbootable image with 2.6.16.29-xenU. This image when it
>>boots creates a vlan eth0.4002, and then tries to communicate on that
>>interface to a central server.
>>
>>
>
>Please can you describe the setup in more detail, including the bridge
>and NIC setup in dom0. It sounds like you're trying to pass a VLAN trunk
>into a guest and then use vconfig inside the guest, but I didn't think
>you could do this with the standard linux bridge as it didn't support
>VLAN trunking.
>
The network setup in dom0 is the default (I've just downloaded the
source tarball and then built and installed it. The only change I've
made is to enable 8021.q support in the xenU kernel). Then you are
correct, in domU I use vconfig to create a vlan interface and ifconfig
to give it an address and bring it up. On systems whose NICs don't use
the tg3 driver, this seems to work fine. I can tcpdump on the bridge in
dom0 and see the tagged traffic coming and going. Here is some info
from dom0 on one of the working systems.
Successful arp request / reply:
[root@localhost ~]# tcpdump -s 0 -e -v -x -i xenbr0 vlan 4002 and arp
tcpdump: WARNING: xenbr0: no IPv4 address assigned
tcpdump: listening on xenbr0, link-type EN10MB (Ethernet), capture size
65535 bytes
13:41:05.560522 00:0e:aa:04:00:0a > 00:0e:aa:04:00:01, ethertype 802.1Q
(0x8100), length 46: vlan 4002, p 0, ethertype ARP, arp who-has
10.21.1.1 tell 10.21.1.9
0x0000: 0fa2 0806 0001 0800 0604 0001 000e aa04 ................
0x0010: 000a 0a15 0109 0000 0000 0000 0a15 0101 ................
13:41:05.560596 00:0e:aa:04:00:01 > 00:0e:aa:04:00:0a, ethertype 802.1Q
(0x8100), length 64: vlan 4002, p 0, ethertype ARP, arp reply 10.21.1.1
is-at 00:0e:aa:04:00:01
0x0000: 0fa2 0806 0001 0800 0604 0002 000e aa04 ................
0x0010: 0001 0a15 0101 000e aa04 000a 0a15 0109 ................
0x0020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x0030: 0000
Bridge:
[root@localhost ~]# brctl show
bridge name bridge id STP enabled interfaces
xenbr0 8000.feffffffffff no peth0
vif0.0
vif41.0
vif42.0
vif43.0
Interfaces:
[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:18:8B:47:B9:DA
inet addr:10.20.36.150 Bcast:10.20.36.255 Mask:255.255.255.0
inet6 addr: fe80::218:8bff:fe47:b9da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1966533 errors:0 dropped:0 overruns:0 frame:0
TX packets:98750 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1034752722 (986.8 MiB) TX bytes:73493849 (70.0 MiB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:208 errors:0 dropped:0 overruns:0 frame:0
TX packets:208 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20595 (20.1 KiB) TX bytes:20595 (20.1 KiB)
peth0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:2387336 errors:0 dropped:0 overruns:0 frame:0
TX packets:1488147 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1704932347 (1.5 GiB) TX bytes:400348056 (381.8 MiB)
Interrupt:16 Memory:d6000000-d6011100
vif0.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:98764 errors:0 dropped:0 overruns:0 frame:0
TX packets:1966544 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:73496741 (70.0 MiB) TX bytes:1034753448 (986.8 MiB)
vif41.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:74309 errors:0 dropped:0 overruns:0 frame:0
TX packets:234316 errors:0 dropped:82 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15679399 (14.9 MiB) TX bytes:123190189 (117.4 MiB)
vif42.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:74107 errors:0 dropped:0 overruns:0 frame:0
TX packets:171556 errors:0 dropped:68 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15630126 (14.9 MiB) TX bytes:96787536 (92.3 MiB)
vif43.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:74210 errors:0 dropped:0 overruns:0 frame:0
TX packets:179269 errors:0 dropped:44 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15624781 (14.9 MiB) TX bytes:107122338 (102.1 MiB)
xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
UP BROADCAST RUNNING NOARP MTU:1500 Metric:1
RX packets:46072 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2601825 (2.4 MiB) TX bytes:0 (0.0 b)
/Evan
[-- Attachment #1.2: Type: text/html, Size: 11098 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2007-01-18 21:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 19:33 Problem with VLANs on tg3 NICs Evan Bigall
2007-01-18 20:37 ` Ian Pratt
2007-01-18 21:46 ` Evan Bigall [this message]
2007-01-18 22:35 ` Ian Pratt
2007-01-19 0:30 ` Evan Bigall
2007-01-19 6:04 ` Nate Carlson
2007-01-19 7:52 ` Ian Pratt
2007-01-19 13:09 ` Evan Bigall
2007-01-19 14:14 ` Ian Pratt
2007-01-19 14:17 ` Christopher G. Stach II
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45AFEAC8.7050904@scalent.com \
--to=evan.bigall@scalent.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.