From: Carlos Valiente <lists@virutass.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Question about tun/tap networking
Date: Mon, 03 May 2004 10:27:38 +0100 [thread overview]
Message-ID: <1083576457.713.8.camel@rilke> (raw)
In-Reply-To: <1083548132.4095a1e4ba072@www.postoffice.tpg.com.au>
On Mon, 2004-05-03 at 02:35, nhand42@tpg.com.au wrote:
> You could also muck about with proxyarp or bridging but honestly, I wouldn't bother
> with that. Routing is a lot easier to understand.
Bridging is not that difficult, either:
0. Get the userland bridge utils from http://bridge.sourceforge.net/ and
make sure your host Linux kernel is configured with CONFIG_BRIDGE
1. Create a bridge device (called 'br0', for instance):
# brctl addbr br0
2. Activate both TUN interfaces (but don't assign them IP addresses:
you'll do that for the bridge device instead)
# ifconfig tun0 0.0.0.0
# ifconfig tun1 0.0.0.0
3. Add both TUN interfaces to the bridge:
# brctl addif br0 tun0
# brctl addif br0 tun1
4. Set the bridge device IP address:
# ifconfig br0 172.16.1.1
C
next prev parent reply other threads:[~2004-05-03 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 1:13 [Qemu-devel] Question about tun/tap networking Arne Bernin
2004-05-03 1:35 ` nhand42
2004-05-03 9:27 ` Carlos Valiente [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-03 3:09 Jim C. Brown
2004-05-03 11:45 ` Arne Bernin
2004-05-03 12:59 ` Renzo Davoli
2004-05-03 13:12 ` Renzo Davoli
2004-05-03 14:05 ` Renzo Davoli
2004-05-03 20:22 ` Jim C. Brown
2004-05-03 21:31 ` Arne Bernin
[not found] <200406230754.07821.pjr@ucar.edu>
2004-06-23 17:03 ` Jim C. Brown
2004-06-23 17:15 ` Phil Rasch
2004-06-23 17:16 ` Gianni Tedesco
2004-06-23 19:32 ` 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=1083576457.713.8.camel@rilke \
--to=lists@virutass.net \
--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.