Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ivan Hernandez <ihernandez@kiusys.com>
To: netfilter@vger.kernel.org
Subject: Port Forwarding Problem
Date: Thu, 24 Apr 2008 16:17:13 -0300	[thread overview]
Message-ID: <4810DCB9.8070208@kiusys.com> (raw)

I have a problem that seems difficult to resolve.

On a LAN a set of computers in the range 192.168.1.x that have already 
assigned a default gw 192.168.1.1 run an application that must connect 
to an internet server 234.56.78.9 to the tcp port 4444 much like a 
telnet app.

The 192.168.1.1 gw does no serves internet  in any way so the 
192.168.1.x network is isolated except for 1 computer, that has 2 nic's 
and is the computer running linux that i need to configure.

That machine has eth0 with 192.168.1.2 and an eth1 with an internet 
address 200.100.23.4.

Now, i can't touch routing on the clients, and clients only can see 
192.168.1.2. I used simpleproxy this way:
simpleproxy -L 4444 -R 234.56.78.9:4444
to solve the problem, but there is any chance to solve it with iptables???

As clients don't have 192.168.1.2 as router, it seems difficult to use 
DNAT because packets are sent to internet, but as 192.168.1.x -> 
234.56.78.9 so they never come back.

Ideally it should receive packets on eth0 like 192.168.1.x -> 
192.168.1.2:4444, and send them to eth1 as 200.100.23.4 -> 
234.56.78.9:4444 and manage the responses to send back the packets 
234.56.78.9:4444 -> 200.100.23.4 from eth1 to 192.168.1.2:4444 -> 
192.168.1.x on eth0

i hope i have found a way to explain the problem!!!
Thanks a lot

Ivan Hernandez
Kiu System Solutions


             reply	other threads:[~2008-04-24 19:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-24 19:17 Ivan Hernandez [this message]
2008-04-25 19:49 ` Port Forwarding Problem Grant Taylor
  -- 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
2005-07-18  5:17 Port Forwarding Problem 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-29  0:56 port " Ian McBeth
2003-01-28  8:14 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=4810DCB9.8070208@kiusys.com \
    --to=ihernandez@kiusys.com \
    --cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox