All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lennert Buytenhek <buytenh@gnu.org>
To: jamal <hadi@cyberus.ca>
Cc: Marc Boucher <marc@mbsi.ca>, bert hubert <ahu@ds9a.nl>,
	netdev@oss.sgi.com
Subject: Re: [PATCH,RFC] explicit connection confirmation
Date: Fri, 8 Nov 2002 13:28:03 -0500	[thread overview]
Message-ID: <20021108182803.GA27346@gnu.org> (raw)
In-Reply-To: <Pine.GSO.4.30.0211080605410.14675-100000@shell.cyberus.ca>


On Fri, Nov 08, 2002 at 06:22:00AM -0500, jamal wrote:

> > netfilter, yeah, sure, 'could have', but please.
> 
> apology if i sounded like one of those adolescent netfilter dangerous
> fools who show up with "mama, look what i can do with a packet now that
> ive read netfilter docs"

No, you don't sound such, sorry for reacting the way i did.


> > 'Make it a netfilter module' is generally what people say when
> > they are confronted with a feature they don't like.
> 
> My angle was to avoid being intrusive to the tcp code.
> you might get a fish sent to you in .nl in an armani suit;->

Sorry but I don't like fish nor armani suits :-)


> > There was a thread about this in private mail round April this year,
> > in which some good points were raised.
> 
> There are some good points; however, whats the app for this feature?

My specific application is a proxy application that replaces the
in-kernel IP masquerading functionality, using a wildcard REDIRECT
rule plus SO_ORIGINAL_DST.  The main reason I'm doing it in userspace
is because downstream bandwidth limiting becomes a whole lot easier
this way than doing it in-kernel -- it would need complicated state
tracking and nonobvious window field manipulations if done there.

The applications that Bert and Marc named sound sane too.  There's
just a whole lot of things this thing can be used for.


cheers,
Lennert

  parent reply	other threads:[~2002-11-08 18:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-07  9:32 [PATCH,RFC] explicit connection confirmation Lennert Buytenhek
2002-11-07 11:27 ` bert hubert
2002-11-07 12:09   ` Lennert Buytenhek
2002-11-07 13:36     ` jamal
2002-11-07 15:27       ` Lennert Buytenhek
2002-11-08 11:22         ` jamal
2002-11-08 11:52           ` bert hubert
2002-11-08 11:56             ` Marc Boucher
2002-11-08 18:28           ` Lennert Buytenhek [this message]
2002-11-07 13:49     ` bert hubert
2002-11-07 14:30       ` Lennert Buytenhek
2002-11-07 16:24         ` bert hubert
2003-08-14 13:11 ` Lennert Buytenhek
2003-08-25 11:09   ` Harald Welte

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=20021108182803.GA27346@gnu.org \
    --to=buytenh@gnu.org \
    --cc=ahu@ds9a.nl \
    --cc=hadi@cyberus.ca \
    --cc=marc@mbsi.ca \
    --cc=netdev@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.