qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: Oliver Gerlich <olig9@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] bug reports and suggestions
Date: Mon, 8 May 2006 13:28:41 -0400	[thread overview]
Message-ID: <20060508172841.GA28661@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <445F7A4F.1080007@gmx.de>

On Mon, May 08, 2006 at 07:05:19PM +0200, Oliver Gerlich wrote:
> > Currently I'm working on a version that doesn't require a kernel module to
> > do this - it will have the limitation of only supporting tcp/ip packets when
> > talking between host/guest.
> 
> Are you sure that limitation is not too "heavy"? How would eg. UDP, ICMP
> or Multicast DNS work with the non-kernel-solution? And wouldn't an
> ethernet-level emulation be cleaner and also easier to explain to other
> users?

Bleh, sorry, I meant IP. It will theoretically support UDP, ICMP, etc
(as long as it's encapsulated within an IP packet  it should work). I'm
primarily testing with TCP/IP.

Ethernet-level emulation is significantly cleaner but it will not work without
either kernel patches or a kernel module. I'm looking for a 100% user space
solution.

> 
> >>Another interesting thing concerning networking: I use a little script
> >>to set up a bridge between eth0 and tap0; but I have give the new bridge
> >>interface (eg. br0) an IP address and such stuff, because eth0 doesn't
> >>work. This is with Linux 2.6, but I read that with Linux 2.4 it was not
> >>necessary to configure br0, as eth0 would still be accessible. Does
> >>anyone know why this changed? I think it would be much easier if an
> >>interface used in a bridge was still usable.
> > 
> > 
> > eth0 is still usable. It is just slightly cleaner to use br0 directly.
> 
> This is what I tried:
> 
> brctl addbr br0
> brctl addif br0 eth0
> 
> After this, a ping to the IP of eth0 (192.168.0.10) still worked. But a
> ping to the gateway (192.168.0.1) didn't. Running `ifconfig br0 up`
> didn't help either. Do you have a hint how to make this work?
> 

What do your routing tables look like right before and right after you
run those two commands?

> 
> Thanks,
> Oliver
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> 
> iD8DBQFEX3pLTFOM6DcNJ6cRAsTuAKCvN0b68WV/dFsznXWhv+tfaxvZZgCfdYLp
> VKEpNiUYKchHgRswHIL/BGo=
> =cTW3
> -----END PGP SIGNATURE-----
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  reply	other threads:[~2006-05-08 17:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 21:51 [Qemu-devel] bug reports and suggestions Don Kitchen
2006-05-05 23:12 ` Oliver Gerlich
2006-05-06 23:03   ` [Qemu-devel] " Anthony Liguori
2006-05-07  5:40     ` wangji
2006-05-08 15:58   ` [Qemu-devel] " Jim C. Brown
2006-05-08 17:05     ` Oliver Gerlich
2006-05-08 17:28       ` Jim C. Brown [this message]
2006-05-06 22:55 ` [Qemu-devel] " Anthony Liguori
2006-05-08 16:17 ` [Qemu-devel] " Jim C. Brown

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=20060508172841.GA28661@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --cc=olig9@gmx.de \
    --cc=qemu-devel@nongnu.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).