From: Marek Kierdelewicz <marek@piasta.pl>
To: NetDev <netdev@vger.kernel.org>
Cc: Ignacy Gawedzki <lkml@qult.net>
Subject: Re: TUN/TAP hacking
Date: Thu, 24 Jul 2008 08:50:06 +0200 [thread overview]
Message-ID: <20080724085006.1163d122@catlap> (raw)
In-Reply-To: <4887E818.4020305@isomerica.net>
Hi Ignacy & netdev,
> I thought I'd be able to use the TAP interfaces to create some sort
> of a network emulator. For a start I just "bridged" two tap
> interfaces, much in the same way as the example of br_select.c from
> http://vtun.sf.net , assigned both interfaces different IPv4
> addresses (both with a /32 prefix),
As far as I understand you're trying to bridge two interfaces of the
same host. It's no good for a test network, because local traffic
(from/to the same host) will always be forwarded locally (via lo?) and
will never reach any ethX or tapX interface (not without kernel
hacking). There's another way... You can use QEMU[1]/KQEMU[2]/KVM[3] for
guest system virtualization with options that create tapX interfaces
on host and ethX on guests. Then you can bridge taps the way you want
(even with eths on your host system) as described in [4][5]. For guest
system I'd recommend openwrt kamikaze[6]. It's small in terms of system
image size and memory consumption so you can build a complex virtual
network of 10+ hosts using only 200MB of disk space and 320MB of ram.
[1] http://bellard.org/qemu/
[2] http://bellard.org/qemu/kqemu-doc.html
[3] http://kvm.qumranet.com/kvmwiki
[4] http://www.fedoraforum.org/forum/showpost.php?p=530775&postcount=1
[5] http://calamari.reverse-dns.net:980/cgi-bin/moin.cgi/bridge
[6] http://openwrt.org/
Cheers,
Marek Kierdelewicz
next prev parent reply other threads:[~2008-07-24 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080723235514.GA8992@zenon.in.qult.net>
2008-07-24 2:25 ` TUN/TAP hacking Dan Noé
2008-07-24 6:50 ` Marek Kierdelewicz [this message]
2008-07-24 8:34 ` Ignacy Gawedzki
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=20080724085006.1163d122@catlap \
--to=marek@piasta.pl \
--cc=lkml@qult.net \
--cc=netdev@vger.kernel.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).