From: Herbert Poetzl <herbert@13thfloor.at>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Connecting vde and LAN
Date: Fri, 12 Aug 2005 02:11:06 +0200 [thread overview]
Message-ID: <20050812001106.GA21001@MAIL.13thfloor.at> (raw)
In-Reply-To: <200508111800.14002.paul@codesourcery.com>
On Thu, Aug 11, 2005 at 06:00:12PM +0100, Paul Brook wrote:
> > I guess this means that VDE would have to provide a kernel-layer
> > component which grabs the packets from eth0 and provides the faked eth0
> > for the Host OS...
>
> You can do all this with the standard linux tools. Something like the
> following(untested) script. ifrename is part of the Linus Wireless Tools. If
> your distro doesn't have it you can download it here:
> http://www.hpl.hp.com/personal/Jean_Tourrilhes/Linux/Tools.html
and nameif is a lot older, part of net-tools and
basically installed on every machine which has
ifconfig ... hmm, scratch the last part, it is
installed on every machine :)
HTH,
Herbert
> Paul
>
> #! /bin/sh
> # Take eth0 down so it can be renamed
> ifdown eth0
> # Rename eth0, and create a new bridge interface called eth0
> # This avoids having to change host network configuration.
> ifrename -i eth0 -n realeth0
> brctl addbr eth0
> brctl addif eth0 realeth0
> # bring realeth0 up without an IP so the bridge can use it
> ifconfig realeth0 0.0.0.0 up
> # bring the new eth0 up
> ifup eth0
> # Start vde, and add it to the bridge.
> vde_switch -t tap0
> ifconfig tap0 0.0.0.0 up
> brctl addif eth0 tap0
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
next prev parent reply other threads:[~2005-08-12 0:33 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
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 [this message]
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=20050812001106.GA21001@MAIL.13thfloor.at \
--to=herbert@13thfloor.at \
--cc=paul@codesourcery.com \
--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).