From: Sudhakar Chandra <thaths@openscroll.org>
To: netfilter@lists.netfilter.org
Subject: Re: Routing between two firewalls
Date: Wed, 23 Jun 2004 18:48:59 +0530 [thread overview]
Message-ID: <40D98343.5000006@openscroll.org> (raw)
In-Reply-To: <200406231034.54767.Antony@Soft-Solutions.co.uk>
Antony Stone wrote:
> Do you have FORWARDing rules on both gateways allowing TCP port 25 packets
> from your internal network to the mail server?
Ah, ha! That was the problem. The proper FORWARDing rule was absent
(which is why I had posted to the netfilter mailing list instead of some
mailing list about routing). I added the rule and things are going great.
Thanks a bunch.
Thaths
--
"Trying is the first step towards failure." -- Homer J. Simpson
Slacker Without Borders http://openscroll.org/
Key fingerprint = 8A 84 2E 67 10 9A 64 03 24 38 B6 AB 1B 6E 8C E4
next prev parent reply other threads:[~2004-06-23 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 9:19 Routing between two firewalls Sudhakar Chandra
2004-06-23 9:34 ` Antony Stone
2004-06-23 13:18 ` Sudhakar Chandra [this message]
2004-06-23 10:04 ` Dharmendra T.
2004-06-23 10:00 ` Antony Stone
2004-06-23 12:00 ` John A. Sullivan III
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=40D98343.5000006@openscroll.org \
--to=thaths@openscroll.org \
--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