All of lore.kernel.org
 help / color / mirror / Atom feed
From: geaaru <geaaru@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Maybe a bug of xen
Date: Tue, 08 Nov 2005 14:27:48 +0100	[thread overview]
Message-ID: <1131456468.12463.39.camel@localhost> (raw)

Hi!
Maybe, I found a bug of xen.
My system:
- domain0 - gentoo - xen-devel-3.0, kernel 2.6.12.5-r1
- domain1 - debian - kernel 2.6.12.5-r1 (2 interface: vif1.1 = eth0
(0.0.0.0), vif1.2 = eth1 (10.0.1.1 + gw 10.0.1.2))
Bridge:
xen-br0 (config as 10.0.1.2) include (vif1.2, vif0.0)
xen-br1 (config as 0.0.0.0) include (vif1.1, peth0)

On server domain1 I use a pppoe server. 

If a send a pppoe request of connection it works, but I see with
ethereal that there is alwais a arp request like this:
Who has 0.0.0.0? Gratuitos ARP
For these reason I try to disable arp protocol with:
- <dom0> ifconfig eth0 0.0.0.0 -arp up;
- <dom0> ifconfig peth0 0.0.0.0 -arp up;
- <dom0> ip link set eth0 arp off
- <dom0> ebtables -A *(all routing/nat tables) -p arp -j DROP;
- set to 0 or 1 /proc/sys/net/ipv4/arp_*;
But there is always arp request.
If I execute mii-tool or ethtool I have this output:

testing_xen ~ # mii-tool 
SIOCGMIIPHY on 'eth0' failed: Operation not supported 
eth1: negotiated 100baseTx-FD flow-control, link ok 
testing_xen ~ # ethtool eth0 
Settings for eth0: 
No data available

With mii-tool I can't read eth0, while is unload module of eth0 and the
reload module e1000 there is a new interface eth2 that mii-tool see
correctly. While eth0 had always same error message. I don't know!
On another abnormal of this system is that if I see traffic with
ethereal from a client see arp request, while from ethereal on server I
can't see arp request!

I think that this is a problem of xen, but maybe is a problem with e1000
kernel module or other. I don't know
Thanks for your replies.

Geaaru

             reply	other threads:[~2005-11-08 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-08 13:27 geaaru [this message]
2005-11-08 15:06 ` Maybe a bug of xen Horms
     [not found]   ` <1131472424.2627.8.camel@localhost>
     [not found]     ` <20051109023934.GB4192@verge.net.au>
2005-11-09 10:20       ` geaaru

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=1131456468.12463.39.camel@localhost \
    --to=geaaru@gmail.com \
    --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.