From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "Jim C. Brown" <jma5@umd.edu>
Subject: Re: [Qemu-devel] tun/tap networking
Date: Sat, 1 Oct 2005 14:50:59 +0100 [thread overview]
Message-ID: <200510011451.02757.paul@codesourcery.com> (raw)
In-Reply-To: <20051001130712.GA28444@jbrown.mylinuxbox.org>
On Saturday 01 October 2005 14:07, Jim C. Brown wrote:
> On Sat, Oct 01, 2005 at 01:30:06PM +0200, Oliver Gerlich wrote:
> > That means it would work if the host NIC is connected to a switch? Then
> > the switch would send packets from the guest which are meant for the
> > host back to the host NIC and everything's fine! Or did I misunderstand
> > that now?
>
> If the switch sends packets from the host NIC back to itself, I believe
> that would work.
A switch will not send a packet back where it came from. That would be a sure
way to introduce infinite forwarding loops.
Paul
next prev parent reply other threads:[~2005-10-01 14:03 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 22:13 [Qemu-devel] tun/tap networking Don Kitchen
2005-09-30 22:21 ` Henrik Nordstrom
2005-09-30 22:21 ` Paul Brook
2005-09-30 23:01 ` Jim C. Brown
2005-10-01 8:12 ` Jean-Christian de Rivaz
2005-10-01 13:12 ` Jim C. Brown
2005-10-01 20:24 ` Jean-Christian de Rivaz
2005-10-01 21:09 ` Jim C. Brown
2005-10-01 21:17 ` Jean-Christian de Rivaz
2005-10-01 20:47 ` [Qemu-devel] tun/tap networking: patch for existing tun Jean-Christian de Rivaz
2005-10-02 2:42 ` Henrik Nordstrom
2005-10-02 7:56 ` Jean-Christian de Rivaz
2005-10-02 10:24 ` Henrik Nordstrom
2005-10-02 16:53 ` Lars Munch
2005-10-02 17:50 ` Jean-Christian de Rivaz
2005-10-02 19:47 ` Jim C. Brown
2005-10-02 20:27 ` Jean-Christian de Rivaz
2005-10-02 18:45 ` Anthony Liguori
2005-10-02 19:39 ` Jim C. Brown
2005-10-02 20:23 ` Jean-Christian de Rivaz
2005-10-02 22:37 ` Jim C. Brown
2005-10-03 9:46 ` Jean-Christian de Rivaz
2005-10-03 12:04 ` Jim C. Brown
2005-10-03 13:10 ` Jean-Christian de Rivaz
2005-10-03 13:19 ` Henrik Nordstrom
2005-10-03 13:13 ` Henrik Nordstrom
2005-10-03 14:14 ` Jean-Christian de Rivaz
2005-10-03 13:07 ` Henrik Nordstrom
2005-10-03 14:00 ` Jean-Christian de Rivaz
2005-10-03 15:04 ` Jim C. Brown
2005-10-03 13:01 ` Henrik Nordstrom
2005-10-03 13:58 ` Jean-Christian de Rivaz
2005-10-03 15:06 ` Jim C. Brown
2005-10-03 12:54 ` Henrik Nordstrom
2005-10-03 15:14 ` Jim C. Brown
2005-10-03 18:29 ` Fabrice Bellard
2005-10-03 19:22 ` Christian MICHON
2005-10-03 20:29 ` Jean-Christian de Rivaz
2005-10-04 7:09 ` Christian MICHON
2005-10-04 7:56 ` Jean-Christian de Rivaz
2005-10-03 21:36 ` Jim C. Brown
2005-10-04 8:23 ` Matteo
2005-10-04 11:34 ` Jim C. Brown
2005-10-01 17:49 ` [Qemu-devel] tun/tap networking Henrik Nordstrom
2005-10-01 20:54 ` Jean-Christian de Rivaz
2005-10-01 11:30 ` Oliver Gerlich
2005-10-01 13:07 ` Jim C. Brown
2005-10-01 13:50 ` Paul Brook [this message]
2005-10-01 21:15 ` Jim C. Brown
2005-10-02 2:21 ` Henrik Nordstrom
2005-10-01 17:52 ` Henrik Nordstrom
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=200510011451.02757.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=jma5@umd.edu \
--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 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.