From: eth <eth@finsiel.ro>
To: netfilter@lists.samba.org
Subject: DNAT w ssh tunnel
Date: Fri, 21 Jun 2002 10:28:30 +0300 [thread overview]
Message-ID: <3D12D59E.6020709@finsiel.ro> (raw)
Hi listers.
I try to make a simple tunnel for a jdbc connection with port forward from one machine to another via a firewall.
|client| --Inet--> |firewall| --LAN--> |database|
The client runs a ssh client with port forwarding to the firewall machine. On the fw I have the "simpleproxy" which is a tcp proxy that forwards all local sockets to a remote host. Yet I thought I should do a:
iptables -t nat -A OUTPUT -d 194.226.254.1 -p tcp -m tcp --dport 1521 -j DNAT --to-destination 192.168.10.100:1521
... which should do the fw->database port forward trick; it doesn't. :-|
Dumping, it looks like packets leave from 192.168.10.1 (which is internal eth firewall) to 192.168.10.100 (which is the database server) , the server says SYN ACK and then the firewall sends a RST !! Why? Isn't DNAT supposed to keep track of all connection even those DNATed? What am I missing? The linux part is a RH 7.3 with a 2.4.18 from kernel.org.
next reply other threads:[~2002-06-21 7:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-21 7:28 eth [this message]
2002-06-21 7:49 ` DNAT w ssh tunnel Karl Fischer
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=3D12D59E.6020709@finsiel.ro \
--to=eth@finsiel.ro \
--cc=netfilter@lists.samba.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