From: Harald Welte <laforge@netfilter.org>
To: Nick Pasich <newsletters@NickAndBarb.net>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: MAX_PORTS for ftp modules
Date: Tue, 27 Jan 2004 12:01:49 +0100 [thread overview]
Message-ID: <20040127110149.GI11761@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20040126211441.GA10833@66.27.62.2>
[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]
On Mon, Jan 26, 2004 at 01:14:41PM -0800, Nick Pasich wrote:
> Hi,
>
> I've exhausted the MAX_PORTS limit of 8 for ftp using my own port id.
>
> I'm wondering if there are any repercussions in upping the limit to say,
> 16 in the following modules.
No, as has been discussed before (and I believe is also on the FAQ or
some HOWTO).
> ip_conntrack_ftp.c: #define MAX_PORTS 8
> ip_conntrack_irc.c: #define MAX_PORTS 8
> ip_conntrack_tftp.c: #define MAX_PORTS 8
> ip_nat_ftp.c: #define MAX_PORTS 8
> ip_nat_irc.c: #define MAX_PORTS 8
> ip_nat_tftp.c: #define MAX_PORTS 8
>
>
> I noticed that ipfwadm_core.c has "IP_FW_MAX_PORTS" which is defined in
> ipfwadm_core.h as 10.
ipfwadm is 2.0.x kernel backwards compatibility. please don't look at
that code ever again ;)
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2004-01-27 11:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 21:14 MAX_PORTS for ftp modules Nick Pasich
2004-01-27 9:40 ` Henrik Nordstrom
2004-01-27 11:01 ` Harald Welte [this message]
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=20040127110149.GI11761@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=newsletters@NickAndBarb.net \
/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.