From: Harald Welte <laforge@netfilter.org>
To: Nikolai Dahlem <listuser@epygi.de>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: NAT problem with related connections
Date: Mon, 3 Nov 2003 08:48:05 +0100 [thread overview]
Message-ID: <20031103074805.GN1536@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <DAELKAPIKOFAFFKELNHOAEAHCAAA.listuser@epygi.de>
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
On Thu, Oct 30, 2003 at 11:31:19AM +0100, Nikolai Dahlem wrote:
> A Master connection is established between Host1 and Server.
> Host1 and Host2 negotiate connection parameters via the Server.
> Then related data connections are established between Host1 and Host2
> directly.
> The control-connection is established and an expectation is created.
> The related connections work in some cases, the problem is that NAT changes
> the source port.
this seems like a bug in your conntrack helper, but without having
access to the source I cannot possibly imagine what you are doing.
> Nikolai Dahlem
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-03 7:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 10:31 NAT problem with related connections Nikolai Dahlem
2003-11-03 7:48 ` Harald Welte [this message]
[not found] ` <DAELKAPIKOFAFFKELNHOCEAICAAA.Nikolai.Dahlem@epygi.de>
2003-11-03 11:08 ` Harald Welte
[not found] ` <DAELKAPIKOFAFFKELNHOGEAICAAA.Nikolai.Dahlem@epygi.de>
2003-11-03 15:39 ` Harald Welte
2003-11-04 13:41 ` Nikolai Dahlem
2003-11-04 15:44 ` Harald Welte
2003-11-03 11:12 ` Harald Welte
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=20031103074805.GN1536@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=listuser@epygi.de \
--cc=netfilter-devel@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.