Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Bo Jacobsen" <subs@systemhouse.dk>
To: netfilter@lists.netfilter.org
Subject: Problem seperating FTP & ms-streaming traffic
Date: Sun, 14 Mar 2004 22:49:41 +0100	[thread overview]
Message-ID: <000d01c40a0e$450f0a50$de0aa8c0@comp> (raw)

I have a problem allowing forwarding of passive internal ftp traffic and, at the
same time disallowing ms-streaming (port 1755).

Whenever I allow the passive ftp, it also allows ms-streaming going through.

My rules are:

iptables -A FORWARD -m state --state NEW,ESTABLISHED -s local_lan --sport highports --dport ftp -j ACCEPT
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -s local_lan --sport highports --dport highports -j ACCEPT

ms-streaming is a highport (1024:) but as there are no NEW in the second rule, it should
not apply to new ms-streaming connections.


Any idears 

Bo Jacobsen




             reply	other threads:[~2004-03-14 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-14 21:49 Bo Jacobsen [this message]
2004-03-14 22:21 ` Problem seperating FTP & ms-streaming traffic Antony Stone
2004-03-15  0:57   ` Bo Jacobsen
2004-03-15  1:05     ` forum
2004-03-15  7:26     ` Antony Stone

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='000d01c40a0e$450f0a50$de0aa8c0@comp' \
    --to=subs@systemhouse.dk \
    --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