All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: habanero@us.ibm.com
Cc: xen-devel@lists.xensource.com
Subject: Re: networking oddities, present status ? changeset: 7145:71466686d026
Date: Fri, 30 Sep 2005 13:50:23 -0700	[thread overview]
Message-ID: <433DA50F.3020301@us.ibm.com> (raw)
In-Reply-To: <200509301502.50666.habanero@us.ibm.com>

Andrew Theurer wrote:
> On Friday 30 September 2005 13:10, Ted Kaczmarek wrote:
> 
>>What is the present status of networking? Also will assigning unique mac
>>addresses to individual bridges on a domO be supported?

I didn't see the parent post on this, and was working on exactly
the same question. Think there are still a few bugs out there,
especially with differing kernel configs (complex bridging,
some filtering, ipsec, tcp options, v6 support, etc). We'd like to beef
up some network test cases and then grind it out through all
the test frameworks. Yes on the latter question.

thanks,
Nivedita

> I have been experiencing some oddities as well.  Xen/bridge networking works 
> on some switches, but not on others.  Also if I have one host with a domU 

Which switches doesn't it work on, do you know?

> communicating to another host, an unrelated host (with xen) will sometimes 
> get "peth0: received packet with  own address as source address" error 
> messages.  I have to wonder if all these bridges on the xen equipped hosts 
> need unique MAC addresses (they all have fe:ff:ff:ff:ff:ff)

  reply	other threads:[~2005-09-30 20:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 18:10 networking oddities, present status ? changeset: 7145:71466686d026 Ted Kaczmarek
2005-09-30 20:02 ` Andrew Theurer
2005-09-30 20:50   ` Nivedita Singhvi [this message]
2005-09-30 21:16   ` Ted Kaczmarek
  -- strict thread matches above, loose matches on Subject: below --
2005-09-30 21:19 Ian Pratt
2005-09-30 22:32 ` Andrew Theurer
2005-10-01 10:17 Ian Pratt
2005-10-11 15:02 ` Andrew Theurer

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=433DA50F.3020301@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=habanero@us.ibm.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.