From: "Nix N. Nix" <nix@go-nix.ca>
To: "Nix N. Nix" <nix@go-nix.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ip_nat_irc & 2.4.18
Date: 08 Jun 2002 22:32:06 -0400 [thread overview]
Message-ID: <1023589926.8435.1.camel@tux> (raw)
In-Reply-To: <1023530798.29159.2.camel@tux>
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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-06-09 2:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-08 10:06 ip_nat_irc & 2.4.18 Nix N. Nix
2002-06-09 2:32 ` Nix N. Nix [this message]
2002-06-09 2:51 ` Robinson Maureira Castillo
2002-06-09 10:44 ` Mathias Gygax
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=1023589926.8435.1.camel@tux \
--to=nix@go-nix.ca \
--cc=linux-kernel@vger.kernel.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