From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: open ports
Date: Sun, 16 May 2004 10:43:06 +0100 [thread overview]
Message-ID: <200405161043.06615.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <BAY15-F39o5AUUYgqms00067882@hotmail.com>
On Sunday 16 May 2004 10:22 am, azeem ahmad wrote:
> hi all
> i have a LAN environment. users from LAN connect to internet via my linux
> box. on this box iptables firewall runs. what ports should i open to allow
> users to get all the services like all chat rooms and yahoo, msn messengers
> and browsing http/ftp etc
1. Start with the following ruleset
iptables -P FORWARD DROP
iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
iptables -A FORWARD -j LOG
2. Get one of your LAN machines to attempt a connection to something you want
to be allowed (eg: web borwsing).
3. Look at the LOG entries to see what packets tried to get through the
firewall (just before DROPped by the default policy).
4. Add a rule, between the two rules given above, to allow that type of
traffic (eg: for web browsing:
iptables -I 2 FORWARD -i $intIF -p tcp --dport 80 -j ACCEPT)
5. Read one of the networking tutorials from http://www.netfilter.org to get a
better understanding of what network protocols should always be allowed (eg:
both types of DNS), and how to find out what port numbers etc are used by the
services you want to allow through the system.
Regards,
Antony.
--
If you can't find an Open Source solution for it, then it isn't a real
problem.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-05-16 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 9:22 open ports azeem ahmad
2004-05-16 9:43 ` Antony Stone [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-16 9:52 azeem ahmad
2004-05-16 10:03 ` Rob Sterenborg
2004-05-16 15:09 ` Alistair Tonner
2004-05-17 0:55 azeem ahmad
2004-05-17 9:43 ` David Cannings
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=200405161043.06615.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