Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Guillermo Javier Nardoni <gjnardoni@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Changhing Source IP (Without SNAT i guess) issue, (help me please)
Date: Thu, 2 Jun 2005 20:51:23 -0300	[thread overview]
Message-ID: <7b85e5305060216511185bb4a@mail.gmail.com> (raw)

Hi, well i've been read a lot of tutorials but i can get this working.-
I tell you my scenario, so you can better understand me.


Scenario:

Linux Box with theses settings

eth0: (internal network 192.168.0.0/24)
ip: 192.168.0.1
nm: 255.255.255.0

eth1: (all internal server hanged through this nic. They are three)
ip: 192.168.1.1
nm: 255.255.255.0


eth2: (Nic used to make pppoe over a cisco 677)
ip: 10.0.0.1
nm: 255.0.0.0

ppp0: Internet Connection (pppoe dhcp)

Actually, everything is working perfectly but... 

Windows 2000 server running some Built-in software (such as a program
on an intranet)
listening on ports 7777/2106

eth0: 
ip: 192.168.1.2
nm: 255.255.255.0
gw: 192.168.2.1


Here we go with the issue:

When a customer make a connection through ppp0 interface, the linux
box route the packets (on ports 7777 and 2106) directly to
win2000 server and it works fine, but with the External IP of the
Firewall, so the software can't work .
so i have to change the source ip before routing (not with SNAT) to
use the firewall's internal ip (actually  192.168.2.1). how
should i do that?.,
i tried to do this using DNAT, SNAT, FORWARD but it doesn't work

I have many customers without system, so they are very ungry, ;-) 

Regards
Guillermo from Argentina.-


-- 
Atte.
Guillermo Javier Nardoni
Estudiante de Ing. en Sistemas
Tel: 03402-15540590


                 reply	other threads:[~2005-06-02 23:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7b85e5305060216511185bb4a@mail.gmail.com \
    --to=gjnardoni@gmail.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