From: Aleksander Kamenik <aleksander@krediidiinfo.ee>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] DNAT PREROUTING issue with IPTABLES
Date: Tue, 25 Sep 2007 08:44:25 +0000 [thread overview]
Message-ID: <46F8CA69.70009@krediidiinfo.ee> (raw)
In-Reply-To: <7ed6b0aa0709242228u211036fdoa33ffa47519ecb2e@mail.gmail.com>
Indunil Jayasooriya wrote:
>
> I have not added it to prerouting chain. I added just
> now. Forward, input and output chains have it.
PREROUTING must not have it. Only the three filter chains and only if
you use the state machine.
> telnet 2.3.4.5 <http://2.3.4.5> 25
>
> it accepts, It works.
>
OK, so DNAT at the second firewall works already. I missed that.
> Now what I need is that I want to telnet to first firewall, then, it
> will forward to second firewall, second firewall will forward to actual
> mail server.
Yes I got that.
Anyway, it's hard to guess without seeing all the rules of the first
firewall. Do any other DNAT's at the first firewall work already?
Is forwading enabled? "cat /proc/sys/net/ipv4/ip_forward" should be "1".
Oh, and by the way. I assumed your routing is in place. Is the the
second firewalls default route (gateway) the first firewall?
You can look at it with "ip route list | grep default".
If 1.2.3.4 and 2.3.4.5 are both external IP's then it's probably the
problem.
--
Aleksander Kamenik
system administrator
+372 6659 649
aleksander@krediidiinfo.ee
Krediidiinfo AS
http://www.krediidiinfo.ee/
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-09-25 8:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 5:40 [LARTC] DNAT PREROUTING issue with IPTABLES Indunil Jayasooriya
2007-09-25 7:50 ` Aleksander Kamenik
2007-09-25 8:35 ` Indunil Jayasooriya
2007-09-25 8:44 ` Aleksander Kamenik [this message]
2007-09-25 8:54 ` Riccardo (SCASI)
2007-09-25 9:18 ` Indunil Jayasooriya
2007-09-25 9:48 ` Aleksander Kamenik
2007-09-25 10:12 ` Indunil Jayasooriya
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=46F8CA69.70009@krediidiinfo.ee \
--to=aleksander@krediidiinfo.ee \
--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.