* Problems with IRC code
@ 2002-12-12 15:10 Michael A. Nunes
0 siblings, 0 replies; only message in thread
From: Michael A. Nunes @ 2002-12-12 15:10 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. I have no need to be able to
dynamically load/unload parts of the kernel. Therefore, 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 ports 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!
Question: What in the IRC code 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-12 15:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-12-12 15:10 Problems with IRC code Michael A. Nunes
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.