All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bob Hockney" <zeus@ix.netcom.com>
To: Jihoon Chung <difro@sexycoder.com>, netfilter@lists.netfilter.org
Subject: Re: IRC DCC between 2 clients on the same net.
Date: Thu, 21 Nov 2002 19:52:39 -0800	[thread overview]
Message-ID: <3DDD3987.28137.1A389300@localhost> (raw)
In-Reply-To: <20021118035555.GA5525@sexycoder.com>

> I have 2 clients behind a masquerading gateway.
> 
> When one of them DCC SEND to the outside world, everything's fine.
> (Thanks
> to ip_conntrack_irc/ip_nat_irc)
> 
> But when I DCC-SEND from one client to the other client on the same
> network, it doesn't work.  The sending side fails almost immediately.
> 
> Is this normal?
> I'm using kernel 2.4.17.

DCC is a passive protocol so sending a file means an inbound tcp connection, why 
you need the irc modules in the first place.  What is happening is that 
ip_nat_irc has little choice but to substitute the external ip of your gateway 
for your LAN ip in the DCC SEND request, thus making the other client think it 
should connect to your gateway instead of the LAN address of the client machine 
to get the file -- what you want if the other client is outside your firewall.  
ip_nat_irc then intercepts this and forwards the connection to the LAN ip making 
to DCC SEND request.

Try unloading the two irc modules and attempting a SEND, which should work if 
the two LAN computers can connect to each other.  Also, make sure the rules in 
the FORWARD chain of the gateway box allow connections to the external ip from 
you LAN.

-Bob


  reply	other threads:[~2002-11-22  3:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  3:55 IRC DCC between 2 clients on the same net Jihoon Chung
2002-11-22  3:52 ` Bob Hockney [this message]
2002-11-22  4:11   ` Jihoon Chung
2002-11-23  0:15     ` Bob
2002-11-23 12:33       ` Jihoon Chung
  -- strict thread matches above, loose matches on Subject: below --
2002-11-15  8:37 Jihoon Chung

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=3DDD3987.28137.1A389300@localhost \
    --to=zeus@ix.netcom.com \
    --cc=difro@sexycoder.com \
    --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 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.