All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: dccp@vger.kernel.org
Subject: Re: DCCP conntrack/NAT
Date: Tue, 08 Apr 2008 16:21:59 +0000	[thread overview]
Message-ID: <47FB9BA7.6080500@trash.net> (raw)
In-Reply-To: <47F64C0D.5080700@trash.net>

Patrick McHardy wrote:
> I've added this patch on top to handle the out-of-sync case by
> letting Requests pass in (almost) any state and resyncing when
> seeing a valid Response.
> 
> Last TODO before the DCCP_LISTEN support is to fix connection
> pickup for established connections. Since it doesn't see the
> initial Request/Response it doesn't know which side has which
> role and also can't properly pick an inital state.

I skipped this for now since it gets a bit ugly and is
not very important for an initial version. I'm uploading
my current tree to kernel.org now, should be there within
the next 20 minutes.

I'll post a patch for DCCP_LISTEN soon (not sure if I will
manage to get it ready today though).


WARNING: multiple messages have this Message-ID (diff)
From: Patrick McHardy <kaber@trash.net>
To: Gerrit Renker <gerrit@erg.abdn.ac.uk>,
	dccp@vger.kernel.org,
	Netfilter Development Mailinglist
	<netfilter-devel@vger.kernel.org>
Subject: Re: DCCP conntrack/NAT
Date: Tue, 08 Apr 2008 18:21:59 +0200	[thread overview]
Message-ID: <47FB9BA7.6080500@trash.net> (raw)
In-Reply-To: <47FB7D3E.4060703@trash.net>

Patrick McHardy wrote:
> I've added this patch on top to handle the out-of-sync case by
> letting Requests pass in (almost) any state and resyncing when
> seeing a valid Response.
> 
> Last TODO before the DCCP_LISTEN support is to fix connection
> pickup for established connections. Since it doesn't see the
> initial Request/Response it doesn't know which side has which
> role and also can't properly pick an inital state.

I skipped this for now since it gets a bit ugly and is
not very important for an initial version. I'm uploading
my current tree to kernel.org now, should be there within
the next 20 minutes.

I'll post a patch for DCCP_LISTEN soon (not sure if I will
manage to get it ready today though).


  parent reply	other threads:[~2008-04-08 16:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-04 15:41 DCCP conntrack/NAT Patrick McHardy
2008-04-04 15:41 ` Patrick McHardy
2008-04-04 19:59 ` Jan Engelhardt
2008-04-04 19:59   ` Jan Engelhardt
2008-04-05 10:09 ` Pablo Neira Ayuso
2008-04-05 10:09   ` Pablo Neira Ayuso
2008-04-05 10:12 ` Pablo Neira Ayuso
2008-04-05 10:12   ` Pablo Neira Ayuso
2008-04-06  0:28 ` Patrick McHardy
2008-04-06  0:28   ` Patrick McHardy
2008-04-07 21:50 ` Gerrit Renker
2008-04-07 21:50   ` Gerrit Renker
2008-04-07 22:45 ` Patrick McHardy
2008-04-07 22:45   ` Patrick McHardy
2008-04-08  9:27 ` Gerrit Renker
2008-04-08  9:27   ` Gerrit Renker
2008-04-08 10:30 ` Patrick McHardy
2008-04-08 10:30   ` Patrick McHardy
2008-04-08 10:33 ` Patrick McHardy
2008-04-08 10:33   ` Patrick McHardy
2008-04-08 11:18 ` Patrick McHardy
2008-04-08 11:18   ` Patrick McHardy
2008-04-08 13:38 ` Gerrit Renker
2008-04-08 13:38   ` Gerrit Renker
2008-04-08 14:12 ` Patrick McHardy
2008-04-08 14:12   ` Patrick McHardy
2008-04-08 14:26 ` Patrick McHardy
2008-04-08 14:26   ` Patrick McHardy
2008-04-08 16:21 ` Patrick McHardy [this message]
2008-04-08 16:21   ` Patrick McHardy

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=47FB9BA7.6080500@trash.net \
    --to=kaber@trash.net \
    --cc=dccp@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 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.