From: Joel Newkirk <netfilter@newkirk.us>
To: juanca <juanca@sat.com.py>
Cc: netfilter@lists.netfilter.org
Subject: Re: Problems with my mail server
Date: 16 Apr 2003 22:28:09 -0400 [thread overview]
Message-ID: <1050546489.22423.4.camel@alpha.newkirk.us> (raw)
In-Reply-To: <098601c30486$14521bc0$0f00a8c0@juancarlitos>
On Wed, 2003-04-16 at 22:07, juanca wrote:
> I´ve implemented this firewall but when I started it
> My mail server doesn´t work
> what might it be problem?
> iptables -A INPUT -s 192.168.0.15 -j ACCEPT
> iptables -A INPUT -s 192.168.0.25 -j ACCEPT
>
> iptables -A INPUT -s 127.0.0.1 -j ACCEPT
>
> iptables -A INPUT -p tcp --dport domain -j ACCEPT
DNS usually runs on udp 53, not tcp. Also, you probably shoud have udp
53 open in OUTPUT as well as INPUT.
> iptables -A INPUT -p tcp --dport http -j ACCEPT
> iptables -A INPUT -p tcp --dport https -j ACCEPT
> iptables -A INPUT -p tcp --dport ftp -j ACCEPT
> iptables -A INPUT -p tcp --dport ftp-data -j ACCEPT
> iptables -A INPUT -p tcp --dport ftps -j ACCEPT
> iptables -A INPUT -p tcp --dport ftps-data -j ACCEPT
> iptables -A INPUT -p tcp --dport pop3 -j ACCEPT
> iptables -A OUTPUT -p tcp --dport pop3 -j ACCEPT
> iptables -A INPUT -p tcp --dport pop3s -j ACCEPT
> iptables -A INPUT -p tcp --dport smtps -j ACCEPT
> iptables -A INPUT -p tcp --dport smtp -j ACCEPT
> iptables -A OUTPUT -p tcp --dport smtp -j ACCEPT -j ACCEPT
> iptables -A INPUT -p tcp --dport 113 -j ACCEPT
> iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A OUTPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
> iptables -A INPUT -j DROP
Do you have DROP policy for INPUT (and/or OUTPUT)? If so,
you don't need this last rule. If not, you probably should.
j
next prev parent reply other threads:[~2003-04-17 2:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030416125602.18155.44510.Mailman@kashyyyk>
2003-04-17 2:07 ` Problems with my mail server juanca
2003-04-17 2:28 ` Joel Newkirk [this message]
2003-04-17 9:54 ` Achim Dreyer
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=1050546489.22423.4.camel@alpha.newkirk.us \
--to=netfilter@newkirk.us \
--cc=juanca@sat.com.py \
--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