From: "Filip Sneppe (Cronos)" <filip.sneppe@cronos.be>
To: Robert Allmeroth <Robert.Allmeroth@epygi.de>
Cc: netfilter@lists.netfilter.org
Subject: Re: Conntrack helper problems (patch-o-matic-20030107)
Date: 27 Feb 2003 23:35:35 +0100 [thread overview]
Message-ID: <1046385336.737.10.camel@exile> (raw)
In-Reply-To: <PIEIIGGHCLEGAPAHFMDOIENNCJAA.Robert.Allmeroth@epygi.de>
On Thu, 2003-02-27 at 17:16, Robert Allmeroth wrote:
>
> here is what i have / see:
>
> FTP conntrack problem:
> bash-2.05# cat /proc/net/ip_conntrack
> tcp 6 431573 ESTABLISHED src=172.30.255.1 dst=10.20.0.17 sport=1572 dport=21 src=10.20.0.17 dst=10.20.10.197 sport=21
> dport=1572 [ASSURED] use=1
> EXPECTING: - use=1 proto=6 src=10.20.0.17 dst=10.20.10.197 sport=0 dport=1573
>
> The sport=0 seems wrong to me..
>
Hi Robert,
It's not necessarily wrong. Basically a conntrack helper
will tell connection tracking what connection to expect
based on IP/TCP header and packet payload info from the
"master" connection.
Often, it will get both IP addresses, plus one port
(destination port is the obvious candidate). With this
info, the expectation will be set up. The other port
is "random" (ie. picked by the client) and can't
really be predicted.
When a conntrack helper sets up an expecation, it
fills in the necessary values and also uses a mask
to point out the relevant info.
The sport=0 here basically means "any port" and is
probably the result of the mask being set to 0 for
the sport of the expectation.
About your problem, are all relevant conntrack + nat
modules loaded (check with lsmod) ?
Regards,
Filip
next prev parent reply other threads:[~2003-02-27 22:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 16:16 Conntrack helper problems (patch-o-matic-20030107) Robert Allmeroth
2003-02-27 16:54 ` Justin Piszcz
2003-02-27 22:35 ` Filip Sneppe (Cronos) [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-27 22:38 Robert Allmeroth
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=1046385336.737.10.camel@exile \
--to=filip.sneppe@cronos.be \
--cc=Robert.Allmeroth@epygi.de \
--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