From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Michael Weiser <michael@weiser.dinsnail.net>
Cc: Pascal Hambourg <pascal@plouf.fr.eu.org>,
Robert White <rwhite@pobox.com>,
netfilter@vger.kernel.org
Subject: Re: Restrictive FTP egress using conntrack helper
Date: Sun, 12 Feb 2017 15:19:40 +0100 [thread overview]
Message-ID: <20170212141940.GA15863@salvia> (raw)
In-Reply-To: <20170212123052.GD2935@weiser.dinsnail.net>
On Sun, Feb 12, 2017 at 01:30:52PM +0100, Michael Weiser wrote:
[...]
> What's bugging me is that I still don't see an expectation being
> created with conntrack -L expect.
It's very unlikely to see FTP expectation via conntrack -L since they
are created and destroyed very quickly if you are testing with a FTP
client.
You can probably watch it there by manually creating a connection via
netcat, and talk FTP, eg.
$ nc ftp.netfilter.org 21
220 ProFTPD 1.3.5 Server (netfilter/iptables FTP site) [::ffff:150.214.142.16 ]
USER anonymous
331 Anonymous login ok, send your complete email address as your password
PASS nothing
PASV
# conntrack -L expect
299 proto=6 src=192.168.2.195 dst=150.214.142.167 sport=0 dport=49926 mask-src=255.255.255.255 mask-dst=255.255.255.255 sport=0 dport=65535 master-src=192.168.2.195 master-dst=150.214.142.167 sport=46532 dport=21 class=0 helper=ftp
conntrack v1.4.4 (conntrack-tools): 1 expectations have been shown.
So `conntrack -E expect' is likely a better option for the debugging
purposes you need.
next prev parent reply other threads:[~2017-02-12 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 17:14 Restrictive FTP egress using conntrack helper Michael Weiser
2017-02-11 22:13 ` Robert White
2017-02-12 9:14 ` Pascal Hambourg
2017-02-12 12:30 ` Michael Weiser
2017-02-12 14:19 ` Pablo Neira Ayuso [this message]
2017-02-12 15:42 ` Michael Weiser
2017-02-12 11:32 ` Michael Weiser
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=20170212141940.GA15863@salvia \
--to=pablo@netfilter.org \
--cc=michael@weiser.dinsnail.net \
--cc=netfilter@vger.kernel.org \
--cc=pascal@plouf.fr.eu.org \
--cc=rwhite@pobox.com \
/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.