From: "Michael A. Nunes" <p@pcmike.net>
To: netfilter@lists.netfilter.org
Subject: Problems with IRC "module"
Date: Mon, 9 Dec 2002 10:09:18 -0500 [thread overview]
Message-ID: <002201c29f94$f22a9b90$02100e0a@jupiter> (raw)
Background: I currently do NOT build my kernel with any modules, as my linux
box is only used as a firewall/router/etc. I don't see a need to be able to
dynamically load/unload things. As such, I build all netfilter code
directly into my kernel.
Problem: Up until 2.4.20 it has always been possible for me to hard-code
ports into ip_conntrack_irc.c and ip_nat_irc.c by simply adding the
following:
if (ports[0] == 0) {
ports[0] = 4646;
ports[1] = 5190;
ports[2] = 5554;
ports[3] = 6667;
ports[4] = 6868;
ports[5] = 7000;
in the respect parts of either file. Like I said, this has ALWAYS worked up
until 2.4.20. DCCs in/out on any port in the above list would always work.
With 2.4.20 after adding the above the only thing that works is DCCs IN!
DCCs going out from a NAT'd box no longer make it through to the internet!
My question to you: What in the IRC "module" has changed so drastically that
I can no longer use the above method for "hard-coding" ports?
--
Michael A. Nunes
/p at pcmike dot net
http://pcmike.net/
reply other threads:[~2002-12-09 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002201c29f94$f22a9b90$02100e0a@jupiter' \
--to=p@pcmike.net \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox