From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: FTP passive not working
Date: Tue, 13 Apr 2004 21:00:22 +0100 [thread overview]
Message-ID: <200404132100.22389.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <20040413134749.4e38203a@mgalepc.utilitran.com>
On Tuesday 13 April 2004 8:47 pm, Michael Gale wrote:
> Hello,
>
> Passive connections to the client work on the local LAN but they are
> connecting to a different IP on the box -- because the server will return
> the external IP of the firewall for passive connections to the main IP.
Yes, I knew that would connect to the other IP on the server - I just wanted
to check that the server was supporting passive connections :)
> I am sure that the problem is that "RELATED" option under state do not work
> with a user defined chain.
Uh?
> iptables -A userchain -i external -o internal -d internalIP -m state
> --state ESTABLISHED,RELATED -j ACCEPT
Nothing wrong with that. No reason at all you can't match those parameters
in a user-defined chain.
I'm not aware of anything in netfilter you can do on a built-in chain which
you can't do on a user-defined chain except apply a default policy.
Regards,
Antony.
--
I don't know, maybe if we all waited then cosmic rays would write all our
software for us. Of course it might take a while.
- Ron Minnich, Los Alamos National Laboratory
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-04-13 20:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-13 17:41 FTP passive not working Michael Gale
2004-04-13 17:59 ` Rob Sterenborg
2004-04-13 19:13 ` Michael Gale
2004-04-13 19:43 ` Michael Gale
2004-04-13 20:08 ` Michael Gale
2004-04-13 20:20 ` Michael Gale
2004-04-13 19:37 ` Antony Stone
2004-04-13 19:47 ` Michael Gale
2004-04-13 20:00 ` Antony Stone [this message]
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=200404132100.22389.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--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