public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* ip_nat_irc & 2.4.18
@ 2002-06-08 10:06 Nix N. Nix
  2002-06-09  2:32 ` Nix N. Nix
  0 siblings, 1 reply; 4+ messages in thread
From: Nix N. Nix @ 2002-06-08 10:06 UTC (permalink / raw)
  To: linux-kernel

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.




^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip_nat_irc & 2.4.18
  2002-06-08 10:06 ip_nat_irc & 2.4.18 Nix N. Nix
@ 2002-06-09  2:32 ` Nix N. Nix
  2002-06-09  2:51   ` Robinson Maureira Castillo
  2002-06-09 10:44   ` Mathias Gygax
  0 siblings, 2 replies; 4+ messages in thread
From: Nix N. Nix @ 2002-06-09  2:32 UTC (permalink / raw)
  To: Nix N. Nix; +Cc: linux-kernel

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/
> 



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip_nat_irc & 2.4.18
  2002-06-09  2:32 ` Nix N. Nix
@ 2002-06-09  2:51   ` Robinson Maureira Castillo
  2002-06-09 10:44   ` Mathias Gygax
  1 sibling, 0 replies; 4+ messages in thread
From: Robinson Maureira Castillo @ 2002-06-09  2:51 UTC (permalink / raw)
  To: Nix N. Nix; +Cc: linux-kernel

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: ip_nat_irc & 2.4.18
  2002-06-09  2:32 ` Nix N. Nix
  2002-06-09  2:51   ` Robinson Maureira Castillo
@ 2002-06-09 10:44   ` Mathias Gygax
  1 sibling, 0 replies; 4+ messages in thread
From: Mathias Gygax @ 2002-06-09 10:44 UTC (permalink / raw)
  To: linux-kernel

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)

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2002-06-10 13:26 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-06-08 10:06 ip_nat_irc & 2.4.18 Nix N. Nix
2002-06-09  2:32 ` Nix N. Nix
2002-06-09  2:51   ` Robinson Maureira Castillo
2002-06-09 10:44   ` Mathias Gygax

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox