| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
AW: AW: [SPAM] Re: [Xen-users] network bridge problem - xen 3.1 ondebian
Works with the broadcom ethernet driver....
-----Ursprüngliche Nachricht-----
Von: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] Im Auftrag von Martin
Goldstone
Gesendet: Tuesday, July 24, 2007 5:57 PM
An: Hinrich Aue; xen-users@xxxxxxxxxxxxxxxxxxx
Betreff: Re: AW: [SPAM] Re: [Xen-users] network bridge problem - xen 3.1
ondebian etch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I assume that output from the bnx2 driver is while the system is booted
with the Xen kernel? Is your other NIC a different manufacturer? If it
is, it might be work trying the other one if you can. I don't see why
it should be the bnx2 driver, as I've got 2 bonded with 2 e1000s,
bridged with VLANs running over them on a system here. I have
encountered problems (seemingly) with the bnx2 driver in the past though.
I'm also assuming you're using the default network (bridged) setup? In
that case, what is the output of '/etc/xen/scripts/network-bridge status'?
Hinrich Aue wrote:
> I use debian edge
> Xen 3.1
>
> I have two Ethernet cards. But I'm only using eth0. It's a 1000Mb card.
bnx2
> is the name of the driver module for the card.
>
> --------------------------------------
> bnx2: eth0 NIC Link is Up, 1000 Mbps full duplex, receive & transmit flow
> control ON
> --------------------------------------
>
> I also switched the Ethernet cable - the right card is attached.
>
> My network configuration is attached below
>
> Everything else is default debian etch installation + default xen 3.1.0
> binary installation.
>
> Interfaces ---------------------------
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> allow-hotplug eth0
> iface eth0 inet static
> address 10.1.1.251
> netmask 255.255.255.0
> network 10.1.1.0
> broadcast 10.1.1.255
> gateway 10.1.1.254
> # dns-* options are implemented by the resolvconf package, if
> installed
> dns-nameservers 10.1.1.253
> dns-search lci-software.com
>
> # The sexondary network interface
> allow-hotplug eth1
> iface eth1 inet static
> address 10.1.2.251
> netmask 255.255.255.0
> network 10.1.2.0
> broadcast 10.1.2.255
>
>
> ---------------------------
>
>
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: Martin Goldstone [mailto:m.j.goldstone@xxxxxxxxxxxxxxx]
> Gesendet: Tuesday, July 24, 2007 5:34 PM
> An: Hinrich Aue; xen-users@xxxxxxxxxxxxxxxxxxx
> Betreff: [SPAM] Re: [Xen-users] network bridge problem - xen 3.1 on debian
> etch
>
> Can you provide us with any more details of your networking setup, Xen
> version, distro etc?
>
> Mart
>
> Hinrich Aue wrote:
>> Hello group,
>
>
>
>> I'm having a problem with networking when booting xen kernel.
>
>
>
>> The networking works when booting in normal kernel.
>
>
>
>> But when booting into xen kernel, it does not work anymore.
>
>
>
>
>
>> The funny thing is that the bridge only shows RX packets, but 0 TX
> packets.
>
>
>> I've also tried the ethtool -K device tx off with every network device.
>
>
>
>> Any idea what could be wrong?
>
>
>
>> Thanks,
>
>> Hinrich
>
>
>
>
>> ------------------------------------------------------------------------
>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGpiFBRnwIDhcMR9MRAr42AJ0aMRWXGOFfSOMfTS0HwOZkbW7JfgCfY8MU
LzNCRwteS9NNLUk6VBViepk=
=DWJM
-----END PGP SIGNATURE-----
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home