Does ip_nat_irc not work with 2.4.18 ? All my old fserves have stopped
working. If I try logging in from the outside (for, say, a DCC file
xfer), I get "Connection Refused" in the client. I believe it ran fine
with 2.4.17. What's wrong ?
Please help.
On Sat, 2002-06-08 at 06:06, Nix N. Nix wrote:
> Does ip_nat_irc not work with 2.4.18 ? All my old fserves have stopped
> working. If I try logging in from the outside (for, say, a DCC file
> xfer), I get "Connection Refused" in the client. I believe it ran fine
> with 2.4.17. What's wrong ?
I figured it out:
ip_nat_irc.o doesn't track connection going to ports other than 6667.
So, if, initially, you connect to, say, twisted.ma.us.dal.net:6668, then
ip_nat_irc doesn't track your connection. :o(
>
>
>
> Please help.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
On Sat, Jun 08, 2002 at 10:32:06PM -0400, Nix N. Nix wrote:
> ip_nat_irc.o doesn't track connection going to ports other than 6667.
> So, if, initially, you connect to, say, twisted.ma.us.dal.net:6668, then
> ip_nat_irc doesn't track your connection. :o(
insmod ip_nat_irc ports=6667,6668,6669,7000 (etcetera)
On 8 Jun 2002, Nix N. Nix wrote:
>
> I figured it out:
>
> ip_nat_irc.o doesn't track connection going to ports other than 6667.
> So, if, initially, you connect to, say, twisted.ma.us.dal.net:6668, then
> ip_nat_irc doesn't track your connection. :o(
>
Hi, from ip_nat_irc.c
-- snip --
* Module load syntax:
* insmod ip_nat_irc.o ports=port1,port2,...port<MAX_PORTS>
*
* please give the ports of all IRC servers You wish to connect to.
* If You don't specify ports, the default will be port 6667
*/
-- snip --
You should change your insmod line for ip_nat_irc to include all port
you're supposed to connect to.
Hope this helps
Best regards.
--
Robinson Maureira Castillo
Asesor DAI
INACAP