All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Brian J. Murrell" <netfilter@interlinx.bc.ca>
To: "Filip Sneppe (Cronos)" <filip.sneppe@cronos.be>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.4/2.5]
Date: 29 Jun 2003 15:37:46 -0400	[thread overview]
Message-ID: <1056915465.9614.59.camel@pc> (raw)
In-Reply-To: <1056913883.1068.70.camel@exile>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

On Sun, 2003-06-29 at 15:11, Filip Sneppe (Cronos) wrote:
> Hi Brian,
> 
> Are you ok with the following two patches? They allow for the
> amanda conntrack/nat modules to track up to 8 ports - it has
> more or less become a common practice for most conntrack/nat
> helpers in the kernel.

In what scenario would there be a need for multiple ports?  The
connection is initiated from the Amanda "server" to the clients.  It's
the clients that listen on port 10080, and it's the connection from the
server to the clients that is watched for, natted and conntracked.

I am having a hard time thinking of a scenario where a client would want
to listen on a port other than it's default and/or listen on multiple
ports for commands from the backup server.

The patch (the 2.4 one anyway) looks syntactically correct.  It's just
the need for it that I am not quite seeing.

b.

-- 
Brian J. Murrell <netfilter@interlinx.bc.ca>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-06-29 19:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-29 19:11 [PATCH 2.4/2.5] Filip Sneppe (Cronos)
2003-06-29 19:37 ` Brian J. Murrell [this message]
2003-06-29 20:20   ` Filip Sneppe (Cronos)
2003-06-29 20:31     ` Brian J. Murrell
2003-06-30 12:05       ` Harald Welte
2003-06-30 12:42         ` Brian J. Murrell
2003-06-29 20:56 ` 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=1056915465.9614.59.camel@pc \
    --to=netfilter@interlinx.bc.ca \
    --cc=filip.sneppe@cronos.be \
    --cc=netfilter-devel@lists.netfilter.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.