* Problems with IRC "module"
@ 2002-12-09 15:09 Michael A. Nunes
0 siblings, 0 replies; only message in thread
From: Michael A. Nunes @ 2002-12-09 15:09 UTC (permalink / raw)
To: netfilter
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-12-09 15:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-09 15:09 Problems with IRC "module" Michael A. Nunes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox