From: varun_saa@vsnl.net
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: mails not going thru'
Date: Sat, 07 May 2005 21:03:11 +0500 [thread overview]
Message-ID: <f4dc0df4fdfc.f4fdfcf4dc0d@vsnl.net> (raw)
----- Original Message -----
From: Jason Opperisano <opie@817west.com>
Date: Saturday, May 7, 2005 8:17 pm
Subject: Re: mails not going thru'
> On Sat, May 07, 2005 at 10:14:49AM +0500, varun_saa@vsnl.net wrote:
> > *filter
> > :FORWARD ACCEPT [0:0]
> > :INPUT DROP [0:0]
> > :OUTPUT ACCEPT [0:0]
> > -A INPUT -s 127.0.0.1 -j ACCEPT
> > -A INPUT -p tcp -m tcp -i eth1 --dport 3128 --sport 1024:65535 -j
> ACCEPT> -A INPUT -p udp -m udp -i eth1 --dport 3128 --sport
> 1024:65535 -j ACCEPT
> > -A INPUT -s 62.0.0.0/255.0.0.0 -i eth0 -j REJECT
> > -A INPUT -p tcp -m tcp -s 217.81.0.0/255.255.0.0 -i eth0 -j REJECT
> > -A INPUT -i eth0 -j DROP
> > -A INPUT -p tcp -m tcp -i eth1 --sport 80 -j DROP
> > -A INPUT -m state -i eth1 --state ESTABLISHED,RELATED -j ACCEPT
> > -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
> > -A FORWARD -p tcp -i eth1 -o eth0 --dport 25 --sport 1024: -j
> ACCEPT --syn
> > -A FORWARD -p tcp -i eth1 -o eth0 --dport 110 --sport 1024: -j
> ACCEPT --syn
> > -A FORWARD -p tcp -i eth1 -o eth0 --dport 1863 --sport 1024: -j
> ACCEPT --syn
> > -A FORWARD -p tcp -i eth1 -o eth0 --dport 5050 --sport 1024: -j
> ACCEPT --syn
>
> the policy of your FORWARD chain is set to ACCEPT, so even if there's
> traffic you haven't accounted for in these rules--it will still be
> allowed through. you have a rule that allows SMTP (TCP 25) out--so i
> bet if you type:
>
> telnet 64.233.185.27 25
>
> which is the IP of gmail's preferred MX, you'd get connected. if
> you'reFORWARD policy was DROP, i'd say that the reason you can't
> send mail from
> a client machine is because you have no rule allowing DNS traffic out:
>
> -A FORWARD -i eth1 -o eth0 -p udp --sport 1024: --dport 53 -j ACCEPT
> -A FORWARD -i eth1 -o eth0 -p tcp --syn --sport 1024: --dport 53 \
> -j ACCEPT
>
> but since those packets will be accepted by the chain policy, my only
> guess is that you do not have any valid DNS servers configured on your
> client machines--on a *nix box:
>
> cat /etc/resolv.conf
>
> -j
>
> --
> "Richie: Mom, uh, I really like Potsy.
> Mrs. Cunningham: Well, Potsy's a nice boy, dear. Why shouldn't you
> like him?
> Richie: No, I mean... I REALLY like Potsy.
> Mr. Cunningham: We heard you the first time, son, you've got a
> homosexual attraction to Potsy."
> --Family Guy
>
Thanks a lot.
Sorry for the resend. I keep forgeting
to the check the reply addresses.
Varun
next reply other threads:[~2005-05-07 16:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-07 16:03 varun_saa [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-12 15:06 mails not going thru' varun_saa
2005-05-12 15:05 varun_saa
2005-05-12 11:50 varun_saa
2005-05-12 12:38 ` Jason Opperisano
2005-05-12 13:47 ` Jason Opperisano
2005-05-09 6:13 varun_saa
2005-05-09 6:19 ` Taylor, Grant
2005-05-09 6:01 varun_saa
2005-05-09 3:53 varun_saa
2005-05-09 14:34 ` Jason Opperisano
2005-05-07 9:09 varun_saa
2005-05-09 6:07 ` Taylor, Grant
2005-05-07 7:12 varun_saa
2005-05-07 7:21 ` Taylor, Grant
2005-05-07 5:14 varun_saa
2005-05-07 6:15 ` Taylor, Grant
2005-05-07 14:47 ` Jason Opperisano
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=f4dc0df4fdfc.f4fdfcf4dc0d@vsnl.net \
--to=varun_saa@vsnl.net \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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.