From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Hicks <peter.hicks@poggs.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Thousands of interfaces
Date: Tue, 31 Oct 2006 21:46:11 +0300 [thread overview]
Message-ID: <454799F3.1020609@tls.msk.ru> (raw)
In-Reply-To: <20061031092550.GA8201@tufnell.london.poggs.net>
Peter Hicks wrote:
> All,
>
> I have a dual 3GHz Xeon machine with a 2.4.21 kernel and thousands (15k+) of
> ipip tunnel interfaces. These are being used to tunnel traffic from remote
> routers, over a private network, and handed off to a third party.
[]
> Is there a userspace program which would handle this application better than
> using interfaces?
Not that it may be suitable for your case because of various reasons (including
but not limited to your use of specific - IPIP - type of tunnels, interoperability
issues), but take a look at the tinc principles -- http://www.tinc-vpn.org/ . They
use single interface (based on tun driver) and a single select-loop-based userspace
program. Initially you configure routing to route ALL your peer's traffic to this
interface, and next tincd takes care of {dis,re}appearing peers, shortest pathes,
{un}reachability of certain networks and so on.
I don't know whenever their implementation scales up to 15K+ peers any better than
current in-kernel implementation, but I think it's easier to deal with this stuff
in userspace anyway. And the principles which are in the base of tinc are very..
interesting and are unique (as far as I know) to it, making this solution ideal for
certain setups.
/mjt
prev parent reply other threads:[~2006-10-31 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 9:25 Thousands of interfaces Peter Hicks
2006-10-31 9:31 ` David Miller
2006-10-31 15:55 ` Ben Greear
2006-10-31 18:22 ` Stephen Hemminger
2006-10-31 21:36 ` David Miller
2006-10-31 18:46 ` Michael Tokarev [this message]
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=454799F3.1020609@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hicks@poggs.co.uk \
/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