From: Chadley Wilson <chadley@ngn.co.za>
To: netfilter@lists.netfilter.org
Subject: Susefirewall2 redirecting
Date: Tue, 23 Aug 2005 15:20:08 +0200 [thread overview]
Message-ID: <200508231520.08360.chadley@ngn.co.za> (raw)
Greetings,
I am struggling to figure out what I have wrong,
We have a remote desktop situation here.
My firewall is a Suse 9.3 box, and works well, but now I have a problem with
the firewall, and I think its because I lack some knowledge on how-to do
this:
Our ISP hosts the dns records for ngn.annoip.org which resolves to
196.31.62.99. But this is our firewall not the windows pc.
There are two lan cards in each the firewall 196.31.62 being the external and
196.100.100 being the internal.
Everthing on our lan must go through the firewall to gain access to the net
and vica-versa,
I have treid a few rules to redirect traffic from the internet --dport 3389 to
the remote desktop pc port 3389. But nothing seems to work.
These are the currecnt rules in my firewall setup for this.
-A PREROUTING -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m tcp
--dport 3389 -j MARK --set-mark 0x1
-A PREROUTING -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p udp -m udp
--dport 3389 -j MARK --set-mark 0x1
-A forward_ext -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m limit
--limit 3/min -m tcp --dport 3389 -m state --state NEW -j LOG --log-prefix
"SFW2-FWDext-ACC-REVMASQ " --log-tcp-options --log-ip-options
-A forward_ext -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m tcp
--dport 3389 -j ACCEPT
-A forward_int -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m limit
--limit 3/min -m tcp --dport 3389 -m state --state NEW -j LOG --log-prefix
"SFW2-FWDint-ACC-REVMASQ " --log-tcp-options --log-ip-options
-A forward_int -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m tcp
--dport 3389 -j ACCEPT
-A input_ext -p tcp -m limit --limit 3/min -m tcp --dport 3389 --tcp-flags
SYN,RST,ACK SYN -j LOG --log-prefix "SFW2-INext-ACC-TCP " --log-tcp-options
--log-ip-options
-A input_ext -p tcp -m tcp --dport 3389 -j ACCEPT
-A input_ext -p udp -m udp --dport 3389 -j ACCEPT
-A PREROUTING -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p tcp -m tcp
--dport 3389 -j REDIRECT --to-ports 3389
-A PREROUTING -s 196.31.62.0/255.255.255.0 -d 196.100.100.2 -p udp -m udp
--dport 3389 -j REDIRECT --to-ports 3389
-A PREROUTING -s 196.31.62.0/255.255.255.0 -d 196.31.62.99 -i eth0 -p tcp -m
tcp --dport 3389 -j DNAT --to-destination 196.100.100.2:3389
Any ideas as to how I can force this to work?
TIA
--
--
Chadley Wilson
Production Line Superintendant
Pinnacle Micro
Manufacturers of Proline Computers
====================================
Exercise freedom, Use LINUX
=====================================
next reply other threads:[~2005-08-23 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 13:20 Chadley Wilson [this message]
2005-08-23 13:39 ` Susefirewall2 redirecting Matt Zagrabelny
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=200508231520.08360.chadley@ngn.co.za \
--to=chadley@ngn.co.za \
--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