From: David Schwartz <davids@webmaster.com>
To: <davem@redhat.com>, <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: RFC2385 (MD5 signature in TCP packets) support
Date: Fri, 15 Mar 2002 16:06:27 -0800 [thread overview]
Message-ID: <20020316000629.AAA989@shell.webmaster.com@whenever> (raw)
In-Reply-To: <20020315.155748.68123299.davem@redhat.com>
On Fri, 15 Mar 2002 15:57:48 -0800 (PST), David S. Miller wrote:
>From: Alan Cox <alan@lxorguk.ukuu.org.uk>
>Date: Sat, 16 Mar 2002 00:12:48 +0000 (GMT)
>
>I've actually got a more constructive suggestion for the zebra folks.
>Route the BGP crap through a netlink tap device, mangle and unmangle the
>tcp frames in luserspace. Saves doing TCP in userspace, saves screwing up
>Dave's nice networking stack.
>
>You'll still need to kill SACK support to make it fit
>
>Another solution could involve a netfilter module to mangle
>the packets.
The problem is that this is intended to be used on machines that are routing
very high volumes of packets on multiple FEs. So the implementation would
have to be minimal cost for packets it didn't need to intercept. So I'd need
to hook into a kernel module or userspace through a filter.
Does ipchains/iptables support to filter selected packets through userspace
work? If it does, this might be an acceptable solution.
DS
next prev parent reply other threads:[~2002-03-16 0:08 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 22:36 RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-15 22:53 ` David S. Miller
2002-03-15 23:11 ` David Schwartz
2002-03-15 23:14 ` David S. Miller
2002-03-15 23:15 ` Alan Cox
2002-03-15 23:13 ` David Schwartz
2002-03-15 23:16 ` David S. Miller
2002-03-15 23:40 ` Alan Cox
2002-03-15 23:37 ` David S. Miller
2002-03-15 23:59 ` Alan Cox
2002-03-15 23:45 ` David S. Miller
2002-03-16 0:01 ` David Schwartz
2002-03-16 0:12 ` Alan Cox
2002-03-15 23:57 ` David S. Miller
2002-03-16 0:06 ` David Schwartz [this message]
2002-03-16 1:43 ` Alan Cox
2002-03-18 4:09 ` David S. Miller
2002-03-18 5:06 ` Mike Fedyk
2002-03-18 6:19 ` David S. Miller
2002-03-16 4:19 ` debugging eth driver Petko Manolov
2002-03-16 17:27 ` Alan Cox
2002-03-16 18:52 ` Petko Manolov
2002-03-16 20:56 ` Alan Cox
2002-03-17 1:36 ` Keith Owens
2002-03-17 3:37 ` Tomasz Kłoczko
2002-03-22 7:40 ` Cameron Simpson
2002-03-15 23:53 ` RFC2385 (MD5 signature in TCP packets) support David Schwartz
2002-03-15 23:54 ` David S. Miller
2002-03-16 0:14 ` Alan Cox
2002-03-17 10:00 ` bert hubert
2002-03-22 5:55 ` 2.5.7, IDE, 'handler not null', 'kernel timer added twice' David Schwartz
2002-03-22 6:10 ` Davide Libenzi
2002-03-22 10:59 ` Martin Dalecki
2002-03-22 20:13 ` Davide Libenzi
2002-03-23 13:12 ` Martin Dalecki
2002-03-22 6:31 ` Andre Hedrick
2002-03-15 23:19 ` RFC2385 (MD5 signature in TCP packets) support Alan Cox
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=20020316000629.AAA989@shell.webmaster.com@whenever \
--to=davids@webmaster.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@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