From: andrew may <acmay@acmay.homeip.net>
To: Maksim Krasnyanskiy <maxk@qualcomm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What is the best way for multiple net_devices
Date: Wed, 27 Jun 2001 16:16:00 -0700 [thread overview]
Message-ID: <20010627161600.C23834@ecam.san.rr.com> (raw)
In-Reply-To: <3B3A5852.AAEF9531@mandrakesoft.com> <20010627145201.A23834@ecam.san.rr.com> <3B3A5852.AAEF9531@mandrakesoft.com> <20010627151829.B23834@ecam.san.rr.com> <4.3.1.0.20010627153532.036e9320@mail1>
In-Reply-To: <4.3.1.0.20010627153532.036e9320@mail1>
On Wed, Jun 27, 2001 at 03:36:37PM -0700, Maksim Krasnyanskiy wrote:
>
> >Any examples of drivers and apps that do this cleanly. The ones I have seen are not.
> TUN/TAP driver and tuncfg utility
> http://vtun.sf.net/tun
OK, thanks that is nice, but I think adding support to get into the /dev
namespace may be a little heavy for things like bonding or ipip.
I did not see tuncfg. From what I could see there were 2 ways to create
new devices. There was a script with mknod and then the ioctl(fd, TUNSETIFF,
(void *) &ifr).
I could do a similar ioctl for a pure net device but I still need a dummy
socket for creating/destroying devices.
I am going for an embedded system so I want to keep things light.
next prev parent reply other threads:[~2001-06-27 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 21:52 What is the best way for multiple net_devices andrew may
2001-06-27 22:04 ` Jeff Garzik
2001-06-27 22:18 ` andrew may
2001-06-27 22:36 ` Maksim Krasnyanskiy
2001-06-27 23:16 ` andrew may [this message]
[not found] <993679536.14418@whiskey.enposte.net>
2001-06-27 22:19 ` Stuart Lynne
-- strict thread matches above, loose matches on Subject: below --
2001-06-28 12:35 Jesse Pollard
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=20010627161600.C23834@ecam.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
/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