The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: ido@the.linux-dude.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: ip_nat_irc bug?
Date: Mon, 10 Dec 2001 11:14:34 -0800 (PST)	[thread overview]
Message-ID: <20011210.111434.41640378.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112101251010.4615-100000@the.linux-dude.net>
In-Reply-To: <Pine.LNX.4.33.0112101251010.4615-100000@the.linux-dude.net>

   From: Ido Diamant <ido@the.linux-dude.net>
   Date: Mon, 10 Dec 2001 12:52:11 +0200 (IST)

    After compiling kernel 2.4.16, I'v seen that I can't dcc chat bots
   running on my local computer. I tried to see why its happening, and
   couldn't get into any reasonable idea.
   Yesterday I remembered that I compiled the 2.4.16 with the ip_nat_irc
   module, and loaded it by default with my firewall. I rmmod ip_nat_irc and
   suddenly I could dcc chat my local bots.
   Q. Why is it happening?
   Q. Am I using this module correctly? as far as I know, I just need to load
   the module, and thats it, am I wrong? should I create some kind of rule
   for it?
   Q. Is it bug?

This patch fixes the bug:

diff -u --recursive --new-file --exclude=CVS --exclude=.cvsignore ../vanilla/2.4/linux/net/ipv4/netfilter/ip_nat_irc.c linux/net/ipv4/netfilter/ip_nat_irc.c
--- ../vanilla/2.4/linux/net/ipv4/netfilter/ip_nat_irc.c	Tue Oct 30 15:08:12 2001
+++ linux/net/ipv4/netfilter/ip_nat_irc.c	Sat Dec  8 19:23:27 2001
@@ -1,8 +1,8 @@
 /* IRC extension for TCP NAT alteration.
- * (C) 2000 by Harald Welte <laforge@gnumonks.org>
+ * (C) 2000-2001 by Harald Welte <laforge@gnumonks.org>
  * based on a copy of RR's ip_nat_ftp.c
  *
- * ip_nat_irc.c,v 1.15 2001/10/22 10:43:53 laforge Exp
+ * ip_nat_irc.c,v 1.16 2001/12/06 07:42:10 laforge Exp
  *
  *      This program is free software; you can redistribute it and/or
  *      modify it under the terms of the GNU General Public License
@@ -81,7 +81,7 @@
 	}
 
 	newdstip = master->tuplehash[IP_CT_DIR_ORIGINAL].tuple.src.ip;
-	newsrcip = master->tuplehash[IP_CT_DIR_ORIGINAL].tuple.dst.ip;
+	newsrcip = ct->tuplehash[IP_CT_DIR_ORIGINAL].tuple.src.ip;
 	DEBUGP("nat_expected: DCC cmd. %u.%u.%u.%u->%u.%u.%u.%u\n",
 	       NIPQUAD(newsrcip), NIPQUAD(newdstip));
 

  reply	other threads:[~2001-12-10 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-10 10:52 ip_nat_irc bug? Ido Diamant
2001-12-10 19:14 ` David S. Miller [this message]
2001-12-10 11:26   ` Ido Diamant

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=20011210.111434.41640378.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ido@the.linux-dude.net \
    --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