All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bartek Krajnik <bartek@bicom.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iptables : Incoming mail and ping problem
Date: Fri, 07 Feb 2003 14:14:47 +0000	[thread overview]
Message-ID: <marc-lartc-104462735601056@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104453889815152@msgid-missing>

On Thu, Feb 06, 2003 at 07:38:54PM +0600, Shaheen Hossain wrote:
> Diff between File I ( iptablesRC ) and File II (iptablesRC.2). File I works for incoming mail. File II does not for incoming mail, neither does pinging to this server to its external interface NIC IP. 
> 
> I could not figure out what the difference in these port allowing, reject or accept commands which are keeping the in-coming mail from coming on a RH Linux 7.3. Please help. Thanks.
> 
> ------------------------------------------------------------------------------
> [shossain@mohican shossain]$ diff /home/admin/firewall/iptablesRC /home/admin/firewall/iptablesRC.2 |  more
> 162c162
> < $IPTABLES -A allowed -p TCP -j REJECT
> ---
> > $IPTABLES -A allowed -p TCP -j DROP
> 185,187c185,187
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --dport 1503 -j allowed
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --dport 3389 -j allowed
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --dport 5001:65535 -j allowed
> ---
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --dport 1500:65535 -j allowed
> 192,200c192,200
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 22 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 25 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 42 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 80 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 113 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 143 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 174 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 443 -j ACCEPT
> < $IPTABLES -A tcp_packets -p TCP -s 0/0 --source-port 5001:65535 -j ACCEPT
> ---
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 22 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 25 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 42 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 80 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 113 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 143 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 174 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 443 -j ACCEPT
> > $IPTABLES -A tcp_packets -p TCP -s 0/0 --sport 1500:65535 -j ACCEPT
> 262d261
> <
> 268d266
> <
Send both files, not differences.

-- 
GPG-Key:
   http://www.bartek.bicom.pl/public_key.txt
   pub  1024D/948DE45D 2002-12-12 Bartek Krajnik <bartek@bicom.pl>
   Primary key fingerprint: 95E9 8E2D 1801 7864 2244  6EAA 03E5 764D 948D E45D


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2003-02-07 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-06 13:38 [LARTC] iptables : Incoming mail and ping problem Shaheen Hossain
2003-02-07 14:14 ` Bartek Krajnik [this message]
2003-02-12  8:29 ` Bartek Krajnik

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=marc-lartc-104462735601056@msgid-missing \
    --to=bartek@bicom.pl \
    --cc=lartc@vger.kernel.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.