From: Roger Singh <rogerindia@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [lartc] Virtual Interface
Date: Tue, 07 Feb 2006 13:23:17 +0000 [thread overview]
Message-ID: <ed235910602070523k3d208bbbpd0de384a183aa773@mail.gmail.com> (raw)
In-Reply-To: <43E3A576.2080604@mailinator.com>
[-- Attachment #1.1: Type: text/plain, Size: 2018 bytes --]
Mike,
Thanks. I will try it..
I have not explained the puspose for this doing this - just to give you an
idea I want to create around 200 virtual interfaces and send traffice
through all the interfaces simulating traffic comming from different
networks. Do you think this approach will scale to that level?
Roger
On 2/3/06, list user <nhgxfjijdrcd@mailinator.com> wrote:
>
> Hi Roger,
>
> [big snip: lost o.p.]
>
> There are a couple of different approaches you might try. One is to use
> uml-utilities' tunctl to create an ethernet tap. Another is to use the
> dummy interface. With either method you can bridge, route, configure as
> you would a physical device using ifconfig and/or ip.
>
> The following methods work for me. I use Fedora Core 4. Its network
> setup methods are in /etc/sysconfig/network-scripts.
>
> cd /etc/sysconfig/network-scripts
> ln -s ifup-eth ifup-tap
> ln -s ifdown-eth ifdown-tap
> echo 'ip link show tap0 | grep "tap0" 2>&1 >/dev/null || tunctl -t tap0
> DEVICE=tap0
> TYPE=ethernet
> ONBOOT=yes
> BOOTPROTO=static
> MACADDR=5a:5a:5a:5a:5a:5a
> NETWORK=192.168.0.0
> IPADDR=192.168.0.1
> BROADCAST=192.168.0.255
> NETMASK=255.255.255.0' > ifcfg-tap0
> ifup tap0
>
> ln -s ifup-eth0 ifup-dummy
> ln -s ifdown-eth ifdown-dummy
> echo 'ip link show dummy0 | grep "dummy0" 2>&1 >/dev/null || {
> ip link set dummy0 up
> ip link set dummy0 arp on
> ip link set dummy0 multicast on
> }
> DEVICE=dummy0
> TYPE=ethernet
> ONBOOT=yes
> BOOTPROTO=static
> MACADDR=a4:a5:a5:a5:a5:a5
> NETWORK=192.168.0.0
> IPADDR=192.168.0.2
> BROADCAST=192.168.0.255
> NETMASK=255.255.255.0' > ifcfg-dummy0
> ifup dummy0
>
> If all went well there should now be two new virtual ethernet devices,
> tap0 and dummy0.
>
> Hope this information is useful to you,
> Mike Wright :m)
>
> _______________________________________________
> LARTC mailing list
> LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
>
[-- Attachment #1.2: Type: text/html, Size: 2884 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-07 13:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 18:48 [lartc] Virtual Interface list user
2006-02-07 13:23 ` Roger Singh [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-04 20:17 [LARTC] virtual interface alen sarkinovic
2004-01-04 20:36 ` Stef Coene
2004-01-04 20:40 ` Martin A. Brown
2004-01-05 9:14 ` Aron Brand
2004-01-05 14:29 ` Roy
2006-02-02 12:33 ` [LARTC] Virtual Interface Roger Singh
2006-02-02 18:08 ` Ryan Castellucci
2006-02-03 15:17 ` Roger Singh
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=ed235910602070523k3d208bbbpd0de384a183aa773@mail.gmail.com \
--to=rogerindia@gmail.com \
--cc=lartc@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).