qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Connecting vde and LAN
Date: Sun, 10 Jul 2005 14:58:58 -0400	[thread overview]
Message-ID: <20050710185858.GA22762@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <42D16795.3090304@gmx.de>

On Sun, Jul 10, 2005 at 08:23:17PM +0200, Oliver Gerlich wrote:
> > The best solution is to use a vde_switch with libpcap and libnet. This allows
> > intercepting packets meant for the guests (via libnet) and forwarding them thru
> > vde. libpcap allows for packets in vde to be passed on to the lan. This also
> > allows for a sort of seamless bridging between host and guest lan. (Technically
> > a tap device is still required to be able to talk to the host, but my understanding
> > is that libpcap handles this automatically.) Plus, the nic remains eth0.
> > 
> > I am not sure how libpcap and libnet would work with DHCP or ARP, but since
> > they work on the ethernet level I suppose a single dhcpd server on eth0 would
> > work in this case, but I am not 100% sure.
> > 
> 
> Sounds interesting! How do I set this up? Couldn't find anything on
> Google, and personally I have no idea how to do this :)
> 
> Oliver

I should have stated that VDE doesn't actually have a version of vde_switch
which uses libpcap or libnet - so it will have to be written first. I'm working
toward that end, but right now its been a slow start.

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

  reply	other threads:[~2005-07-10 19:32 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-10 12:27 [Qemu-devel] Connecting vde and LAN Oliver Gerlich
2005-07-10 16:42 ` Henrik Nordstrom
2005-07-10 17:37   ` Jim C. Brown
2005-07-10 18:23     ` Oliver Gerlich
2005-07-10 18:58       ` Jim C. Brown [this message]
2005-07-11  2:21     ` Henrik Nordstrom
2005-07-11  2:33       ` Jim C. Brown
2005-07-11  7:50         ` Henrik Nordstrom
2005-07-11 15:02           ` Jim C. Brown
2005-07-11 23:01             ` Jim C. Brown
2005-07-12  2:49               ` Henrik Nordstrom
2005-07-12 22:25                 ` Jim C. Brown
2005-08-04 10:14                   ` Henrik Nordstrom
2005-08-05 16:54                     ` Jim C. Brown
2005-08-10 19:07                       ` Jim C. Brown
2005-08-11 14:56                         ` Henrik Nordstrom
2005-08-11 16:24                           ` Oliver Gerlich
2005-08-11 16:56                             ` Jim C. Brown
2005-08-12 10:02                               ` Henrik Nordstrom
2005-08-12 18:07                                 ` Jim C. Brown
2005-08-11 17:00                             ` Paul Brook
2005-08-12  0:11                               ` Herbert Poetzl
2005-08-12  9:53                             ` Henrik Nordstrom
2005-07-10 17:48   ` Oliver Gerlich
2005-07-11  1:36     ` Henrik Nordstrom
2005-07-12 19:43     ` Ross Kendall Axe
2005-07-12 20:31       ` Oliver Gerlich
2005-07-13  3:02         ` Ross Kendall Axe
2005-07-10 18:27   ` Bakul Shah

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=20050710185858.GA22762@jbrown.mylinuxbox.org \
    --to=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 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).