From: Rudi Starcevic <tech@wildcash.com>
To: netfilter@lists.netfilter.org
Subject: Re: RDP and iptables ruleset
Date: Thu, 09 Dec 2004 14:27:19 -0800 [thread overview]
Message-ID: <41B8D147.5050600@wildcash.com> (raw)
In-Reply-To: <17F5DA2FB6F18744BA13C2197738727CD19AC1@alchmail.alch-la-dc.alchemy.net>
Hi James,
I set up RDP port-forwarding for the first time myself earlier this week.
I'm using Debian 3 and Win 2003.
These rules work well for me with a default policy of Accept ( which
I'll update shortly )::
##### start NAT routing #####
$IPTABLES --table nat --append POSTROUTING --out-interface eth0 -j
MASQUERADE
# forward remote desktop media_server_1
$IPTABLES -t nat -A PREROUTING -i eth0 -p tcp --dport 3389 -s
xxx.xxx.xxx.xxx -j DNAT --to 192.168.0.10:3389
# ENABLE FORWARDING / NAT / MASQUERADING
echo "1" > /proc/sys/net/ipv4/ip_forward
Hope this helps.
Kind regards,
Rudi.
James Bowling wrote:
>I seem to be having some issues with iptables 1.2.11 and getting RDP to
>be allowed through. My windows box is NAT'd behind my Gentoo 2004.3
>box. Here is my NAT Tables:
>
># iptables -t nat -L
>Chain PREROUTING (policy ACCEPT)
>target prot opt source destination
>DNAT tcp -- anywhere anywhere tcp
>dpt:3389 to:10.0.1.2:3389
>
>Chain POSTROUTING (policy ACCEPT)
>target prot opt source destination
>SNAT tcp -- anywhere anywhere tcp
>dpt:3389 to:10.0.1.2:3389
>MASQUERADE all -- anywhere anywhere
>
>Chain OUTPUT (policy ACCEPT)
>target prot opt source destination
>
>
>Here is my iptables rules:
>
># iptables -L
>Chain INPUT (policy ACCEPT)
>target prot opt source destination
>ACCEPT all -- anywhere anywhere
>REJECT udp -- anywhere anywhere udp
>dpt:bootps reject-with icmp-port-unreachable
>REJECT udp -- anywhere anywhere udp
>dpt:domain reject-with icmp-port-unreachable
>ACCEPT tcp -- anywhere anywhere tcp dpt:ssh
>
>ACCEPT tcp -- anywhere anywhere tcp dpt:ftp
>
>ACCEPT tcp -- anywhere anywhere tcp
>dpt:ftp-data
>ACCEPT tcp -- anywhere anywhere tcp
>dpt:8245
>DROP tcp -- anywhere anywhere tcp
>dpts:0:1023
>DROP udp -- anywhere anywhere udp
>dpts:0:1023
>
>Chain FORWARD (policy ACCEPT)
>target prot opt source destination
>DROP all -- anywhere 10.0.1.0/24
>ACCEPT all -- 10.0.1.0/24 anywhere
>ACCEPT all -- anywhere 10.0.1.0/24
>ACCEPT all -- anywhere anywhere state
>RELATED,ESTABLISHED
>ACCEPT all -- anywhere anywhere
>
>Chain OUTPUT (policy ACCEPT)
>target prot opt source destination
>
>This is just a very basic rule set as you can see. What happens is when
>I connect with RDP it goes through to the login and then after
>authentication it just sits there and eventually times out. Any ideas
>on what is going on? Any help would be appreciated.
>
>
>Regards,
>James Bowling
>
>
>
>
>
prev parent reply other threads:[~2004-12-09 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 18:06 RDP and iptables ruleset James Bowling
2004-12-08 23:05 ` Jason Opperisano
2004-12-09 22:27 ` Rudi Starcevic [this message]
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=41B8D147.5050600@wildcash.com \
--to=tech@wildcash.com \
--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