From: Jihoon Chung <difro@sexycoder.com>
To: Bob <BHockney@ix.netcom.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: IRC DCC between 2 clients on the same net.
Date: Sat, 23 Nov 2002 21:33:51 +0900 [thread overview]
Message-ID: <20021123123351.GA11201@morpheus> (raw)
In-Reply-To: <3DDE5824.22076.E31BED@localhost>
On Fri, Nov 22, 2002 at 04:15:32PM -0800, Bob wrote:
> After attempting this, the problem is that the client receiving the file
> attempts a connection to the external ip, which is intercepted by ip_nat_irc
> and forwarded to the other client on the LAN, but with a source ip of client
> initiating the tcp connection, which is correct (it would be the ip of the a
> remote host if outside the firewall). The second client then responds, but
> since it is responding to an ip on its own subnet, the reply doesn't go
> through the gateway. The first client is expecting a reply from the external
> ip (since it sent the SYN there), but gets a reply from another ip and rejects
> it. The second client immediately closes the DCC connection, while the first
> continues to wait for a reply until it times out.
>
> This behavior is normal, by design in ip_nat_irc, and difficult to fix. One
> workaround, which does work, is modify the routing table of both clients to
> send all LAN traffic through the gateway. A kludge at best.
I see. Thanks.
Guess there is no clean solution for this situation.
when ip_nat_irc intercepts the dcc connection, can't you make it change the
source ip to the gateway's ip? That way, responding client would send
the packet to gateway where the dst ip would be changed back to the
original one ? Just a thought.. I don't know much about the netfilter
nat structure.
next prev parent reply other threads:[~2002-11-23 12:33 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
2002-11-22 4:11 ` Jihoon Chung
2002-11-23 0:15 ` Bob
2002-11-23 12:33 ` Jihoon Chung [this message]
-- 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=20021123123351.GA11201@morpheus \
--to=difro@sexycoder.com \
--cc=BHockney@ix.netcom.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.