From: Ian McBeth <imcbeth@telus.net>
To: netfilter@lists.netfilter.org
Subject: Re: port forwarding problem
Date: 28 Jan 2003 17:56:07 -0700 [thread overview]
Message-ID: <1043801767.3685.47.camel@blackice.telco.ca> (raw)
Hello.....
I think you must have the SNAT in there as well
-A PREROUTING -p tcp -m tcp -d (external IP) -i eth1 --dport 25 -j DNAT
--to-destination 192.168.0.2:25
-A POSTROUTING -p tcp -m tcp -s 192.168.0.2 -o eth1 -j SNAT --to-source
62.194.25.2:25
-A FORWARD -p tcp -m tcp -d 192.168.0.2 -i eth1 -o eth0 --dport 25
let me know if this helps
Ian
On Tue, 2003-01-28 at 01:14, oarojo@intermediacorp.com wrote:
> hello guys!!! Can someone help me on my problem regarding iptables???
>
> This has been my problem a month now.. I'm running a redhat 7.3
firewall
> server with two NICs; eth0 facing the internal network (192.168.0.x)
and
> eth1 facing the internet (external network). Now I wish to forward all
> traffic on eth1, port 25 to another to my mail server (say,
192.168.0.2). I
> did something like:
>
> iptables -t nat -A POSTROUTING -s 192.168.0.0/24 -j MASQUERADE
> iptables -A FORWARD -p tcp --dport 25 -d 192.168.0.2 -j ACCEPT
> iptables -A PREROUTING -t nat -p tcp --dport 25 -d x.x.x.x -j DNAT
> --to 192.168.0.2
>
> Now when i used to test SMTP connection thru telnetting from another
> server... say:
>
> #telnet xxx.xxx.xxx.xxx 25
>
> It just stucked in there doesn't continue...
>
> using nmap on my firewall:
>
> #nmap xxx.xxx.xxx.xxx -p 25
>
> it says that port 25 is filtered...
>
>
> Is there anything wrong with my iptable rules? I would really
appreciate if
> you can send me your help... thanks!
>
>
> Oliver
>
>
>
next reply other threads:[~2003-01-29 0:56 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 0:56 Ian McBeth [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-16 12:53 Port forwarding problem Carlos Mtz-Troncoso
2010-10-16 13:13 ` Pascal Hambourg
2010-10-16 13:19 ` Carlos Mtz-Troncoso
2010-10-16 13:37 ` Pascal Hambourg
2010-10-16 14:01 ` Carlos Mtz-Troncoso
2010-10-16 18:19 ` Pascal Hambourg
2008-04-24 19:17 Port Forwarding Problem Ivan Hernandez
2008-04-25 19:49 ` Grant Taylor
2005-07-18 5:17 George Esperanza
2005-04-15 10:36 Julian Labuschagne
2005-04-15 10:34 Julian Labuschagne
2005-04-15 8:40 ` Samuel Díaz García
2005-04-15 11:23 ` Julian Labuschagne
2005-04-15 14:32 ` Taylor, Grant
2005-04-15 14:40 ` Jason Opperisano
2003-02-25 18:06 Tom Smith
2003-02-25 20:14 ` Willi Dyck
2003-02-25 21:53 ` Tom Smith
2003-02-26 3:20 ` Arnt Karlsen
[not found] ` <3E5C3DEE.70104@openadventures.org>
2003-02-26 14:07 ` Arnt Karlsen
[not found] <001601c2d1fa$669894e0$990da8c0@..153.service>
2003-02-11 19:11 ` Port forwarding problem DarKRaveR
2003-02-11 19:14 ` Rob Sterenborg
2003-02-11 18:21 Danila Octavian
2003-01-28 8:14 port " oarojo
2003-01-29 1:21 ` Arnt Karlsen
2002-11-14 4:29 Port " Tom Elsesser
2002-11-24 20:40 ` Joel Newkirk
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=1043801767.3685.47.camel@blackice.telco.ca \
--to=imcbeth@telus.net \
--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