All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Joachim Wickman" <jwickman@tawi.fi>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] IRC and DCC
Date: Fri, 02 Nov 2001 22:24:43 +0000	[thread overview]
Message-ID: <marc-lartc-100473984221789@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100473755914896@msgid-missing>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

I have compiled everything into the kernel

  ----- Original Message ----- 
  From: Greg Scott 
  To: 'Joachim Wickman' ; lartc@mailman.ds9a.nl 
  Sent: Saturday, November 03, 2001 12:31 AM
  Subject: RE: [LARTC] IRC and DCC


  There are some modules you need to modprobe.  Try this:
   
      /sbin/modprobe ip_conntrack_irc

  I'll bet there are also others.  Is there some central list of modules and what they do anywhere?
   
  - Greg
   
   
    -----Original Message-----
    From: Joachim Wickman [mailto:jwickman@tawi.fi]
    Sent: Friday, November 02, 2001 3:47 PM
    To: lartc@mailman.ds9a.nl
    Subject: [LARTC] IRC and DCC


    Hello

    I'm running NAT on my Linux box (192.168.0.1) with this command
     
    /usr/local/sbin/iptables -t nat -A POSTROUTING -o ippp0 -j MASQUERADE
     
    Everything is working fine, except DCC in IRC.
    When I try to send something the remote machine get's "can't connect"
     
    Have I missed something, or what?
    It does work when I NAT with ipchains, but I like iptables more.
     
    Thanks,
       Joachim

     

[-- Attachment #2: Type: text/html, Size: 3888 bytes --]

  reply	other threads:[~2001-11-02 22:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-02 21:46 [LARTC] IRC and DCC Joachim Wickman
2001-11-02 22:24 ` Joachim Wickman [this message]
2001-11-02 22:31 ` Greg Scott
2001-11-04 17:16 ` Largo Hellenz
2001-11-04 23:56 ` Sebastian 'spax' Pape
2001-11-08 16:01 ` Ivan Lopez
2001-11-08 18:40 ` Joachim Wickman
2001-11-12 10:33 ` Joachim Wickman
2001-11-12 13:13 ` Joachim Wickman
2001-11-12 13:22 ` Greg Scott

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=marc-lartc-100473984221789@msgid-missing \
    --to=jwickman@tawi.fi \
    --cc=lartc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.