From: Mohammad Khan <mkhan@lextranet.com>
To: varun_saa@vsnl.net, netfilter@lists.netfilter.org
Subject: Re: net2phone rules
Date: Mon, 14 Feb 2005 17:16:07 -0500 [thread overview]
Message-ID: <1108419367.13080.18.camel@localhost.localdomain> (raw)
In-Reply-To: <55503955141a.55141a555039@vsnl.net>
On Tue, 2005-02-08 at 01:01, varun_saa@vsnl.net wrote:
> Hello,
> I want my firewall to allow Net2phone.
>
> A visit to http://web.net2phone.com/consumer/commcenter/helpfirewall.asp
> states that you need to open up at least three ports:
> tcp 80 - tcp 6800 - udp 6801.
>
> One should use INPUT or FORWARD rule ?
Depends on where is your net2phone client.
If it is *NOT* on your firewall, use FORWARD
I visited the net2phone link, your forward rules should be
# Following two rules would allow log in,
# maintaining online status, and instant messaging
-A FORWARD -s internal_ne_ips -d relay.net2phone.com -p tcp --dport 80
-m state --state NEW,ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -s relay.net2phone -p tcp --sport 80 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
# Following two rules would allow voice packets to go out
-A FORWARD -s internal_net_ips tcp --sport 6800 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -s internal_net_ips -p udp --sport 6801 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
# Following two rules would allow voice packets to get in
-A FORWARD -d external_ip tcp --dport 6800 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
-A FORWARD -d external_ip -p udp --dport 6801 -m state --state
NEW,ESTABLISHED,RELATED -j ACCEPT
Above rules can be made more restrictive !
Enjoy firewalling.
Mohammad
--
"Mad cow? You'd be mad too, if someone was trying to eat you."
prev parent reply other threads:[~2005-02-14 22:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 6:01 net2phone rules varun_saa
2005-02-14 22:16 ` Mohammad Khan [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=1108419367.13080.18.camel@localhost.localdomain \
--to=mkhan@lextranet.com \
--cc=netfilter@lists.netfilter.org \
--cc=varun_saa@vsnl.net \
/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