Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@alistairt.ath.cx>
To: Mihai Tanasescu <cloud@sky.kappa.ro>
Cc: netfilter@lists.netfilter.org
Subject: Re: IRC and Conntrack problem
Date: Sun, 3 Nov 2002 06:15:28 -0500	[thread overview]
Message-ID: <20021103111528.GA14182@Ajftl1.ajfthome.on.ca> (raw)
In-Reply-To: <00d601c28286$83cf1390$6928a8c0@MIHAI>; from cloud@sky.kappa.ro on Sat, Nov 02, 2002 at 10:42:56 -0500


	1) the ipt_conntrack_irc and ipt_nat_irc modules need to know  
what
	    ports you are connecting to the IRC servers on.  You pass 
these
	    port numbers as a parameter to the module when loaded.

	2) IRC clients behind the firewall *must* use their *inside* ip
	    address *not* the firewall ip address ... this is notable in
	    MIRC -- the client defaults to using the ip reported by the
	    server. -- that turns the connection requests into something
             that iptables will drop as a forged IRC command -- check
             your logs.


  In my case:
/sbin/modprobe ip_conntrack_irc 
ports=6663,6664,6665,6666,6667,6668,6669,7000
/sbin/modprobe ip_nat_irc ports=6663,6664,6665,6666,6667,6668,6669,7000

You can edit ip_conntrack_irc.c and ip_nat_irc.c and change MAX_PORTS 
if you
  need more ports to connect to and then rebuild the modules.
	 

On 2002.11.02 10:42 Mihai Tanasescu wrote:
> I have installed the kernel module for conntracking irc connections.
> Still I can only receive dcc sends but I can't initiate any dcc send
> sessions. I get the error message failed to connect or something like
> that.
> What am I doing wrong?
> 



  reply	other threads:[~2002-11-03 11:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02 15:42 IRC and Conntrack problem Mihai Tanasescu
2002-11-03 11:15 ` Alistair Tonner [this message]
2002-11-03 18:11 ` Roy Sigurd Karlsbakk
  -- strict thread matches above, loose matches on Subject: below --
2002-11-02 15:39 Mihai Tanasescu

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=20021103111528.GA14182@Ajftl1.ajfthome.on.ca \
    --to=alistair@alistairt.ath.cx \
    --cc=cloud@sky.kappa.ro \
    --cc=netfilter@lists.netfilter.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