From: Joel Newkirk <netfilter@newkirk.us>
To: Jean-Christian Imbeault <jc@mega-bucks.co.jp>,
netfilter@lists.netfilter.org
Subject: Re: rules for Real's Helix Universal Media Server?
Date: Mon, 3 Mar 2003 02:54:50 -0500 [thread overview]
Message-ID: <200303030254.50601.netfilter@newkirk.us> (raw)
In-Reply-To: <3E62E020.2090004@mega-bucks.co.jp>
On Sunday 02 March 2003 11:54 pm, Jean-Christian Imbeault wrote:
> I am running Real's Helix Media Server on a linux box and would like
> to secure the box as much as possible but I can't figure what ports
> this media server needs. It seems to pretty much need everything about
> 1024 ...
http://service.real.com/help/library/guides/helixuniversalproxy/htmfiles/firewall.htm#198350
> Has anyone been able to come up with some rules for a Helix Media
> Server?
Presuming the rules are being run on the box itself, it looks like these
INPUT rules for a Universal Server:
# For Helix universal server dealing with media players
iptables -A INPUT -p tcp --multiport --dport 554,7070,8080 -j ACCEPT
iptables -A INPUT -p udp --dport 6970:6999 -j ACCEPT
# For Helix universal server communicating with universal proxy
iptables -A INPUT -p tcp --multiport --dport 3030,7802,7878 -j ACCEPT
iptables -A INPUT -p udp --dport 3030 -j ACCEPT
and these for a Universal Proxy server:
# for Helix universal proxy communicating with media players or child
proxies
iptables -A INPUT -p tcp --multiport --dport 554,1090,1755 -j ACCEPT
# for Helix universal proxy communicating with media servers
iptables -A INPUT -p tcp --dport 3030 -j ACCEPT
iptables -A INPUT -p udp --dport 3030 -j ACCEPT
# 6970-32000 for both media servers and parent proxies
iptables -A INPUT -p udp --dport 6970:32000 -j ACCEPT
Apparently that huge range of UDPs can be restricted with the "UDP Resend
Port Range" Proxy setting. The OUTPUT rules, if you need them as well,
should apparently be:
# for universal server communicating with media players
iptables -A OUTPUT -p udp --dport 6970:6999 -j ACCEPT
# for universal server communicating with universal proxy
iptables -A OUTPUT -p udp --dport 6970:32000 -j ACCEPT
# for universal proxy communicating with players or child proxies
iptables -A OUTPUT -p udp --dport 1024:5000 -j ACCEPT
iptables -A OUTPUT -p udp --dport 6970:65535 -j ACCEPT
# for universal proxy communicating with media server and parent proxy
iptables -A OUTPUT -p tcp --multiport --dport 554,1755,3030,7070,7878 -j
ACCEPT
iptables -A OUTPUT -p udp --dport 3030 -j ACCEPT
Also, a universal proxy needs to send on TCP 9090 and listen on a
configured port for administration.
These are certainly not the tightest rules possible for this beast, quite
likely around 50% of these rules wouldn't see any traffic if you have
ESTABLISHED,RELATED allowed through. (like OUTPUT going to a media
player) My suggestion would be to place EST/REL rules first, then these
rules, separated instead of using multiport match. After a reasonable
period of time, check the packet counts with "iptables -L -v -n" and see
which rules never hit, then try commenting them out of the script for a
while to ensure that you can do without them. If you know more about
how these communications are initiated than I do, you could probably
look at these rules and pick out which ones would only be replies.
j
next prev parent reply other threads:[~2003-03-03 7:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 4:54 rules for Real's Helix Universal Media Server? Jean-Christian Imbeault
2003-03-03 7:54 ` Joel Newkirk [this message]
2003-03-05 8:30 ` Jean-Christian Imbeault
2003-03-05 17:00 ` Joel Newkirk
2003-03-05 9:08 ` Jean-Christian Imbeault
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=200303030254.50601.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=jc@mega-bucks.co.jp \
--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 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.