From: "Filip Sneppe (Cronos)" <filip.sneppe@cronos.be>
To: "Brian J. Murrell" <netfilter@interlinx.bc.ca>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.4/2.5]
Date: 29 Jun 2003 22:20:53 +0200 [thread overview]
Message-ID: <1056918054.1068.96.camel@exile> (raw)
In-Reply-To: <1056915465.9614.59.camel@pc>
On Sun, 2003-06-29 at 21:37, Brian J. Murrell wrote:
>
> 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.
>
Well not a lot of common scenarios, I will give you that, but
I just figured that in some situations, people run services
on different ports, not the standard ports the services are normally
associated with. Sometimes because those ports are blocked by
another firewall, sometimes to confuse portscanners. I just
figured that the other conntrackers in the kernel had this
feature so I added it to your code...
Regards,
Filip
next prev parent reply other threads:[~2003-06-29 20:20 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
2003-06-29 20:20 ` Filip Sneppe (Cronos) [this message]
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=1056918054.1068.96.camel@exile \
--to=filip.sneppe@cronos.be \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@interlinx.bc.ca \
/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.