Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Daniel Frederiksen <cyberdoc@cyberdoc.dk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Ip Src rewite.
Date: Tue, 25 Oct 2005 12:58:04 +0000	[thread overview]
Message-ID: <435E2BDC.1080507@cyberdoc.dk> (raw)
In-Reply-To: <435E26E3.2080204@cyberdoc.dk>

Oscar Mechanic wrote:
> Maybe I have missed somthing and you need to do it in POSTROUTING but
> how about SNAT.
> 

Well currently I do not NAT at all. I have ip_forwarding enabled and 
have assigned the first IP from the external block on the inside of the 
Gateway/Firewall. On the outside of the Gateway/Firewall I have assigned 
the WAN IP. This way when a system on the DMZ establishes a connection 
it is forwarded through the Gateway.

Any suggestions to changes are appreciated.

/Daniel..

> PS: ip can do stateless nat.
> 
> On Tue, 2005-
> 10-25 at 14:36 +0200, Daniel Frederiksen wrote:
> 
>>Hello folks..
>>
>>Does any of you know if it is possible to rewrite the ip src in a packet.
>>I have a problem involving a DMZ with external IP addresses routed 
>>trough a single WAN IP. When the server initiates a connection, it looks 
>>like it comes from the WAN ip instead of it's designated External IP 
>>routed through the WAN.
>>So in short, Is it possible to rewrite the packet in the router, with 
>>Iptables, to make it look like it comes from the external IP address 
>>instead of the WAN IP of the router/firewall.
>>
>>Thank you very much for your time, I appreciate it.
>>
>>/Daniel Frederiksen
>>
>>
>>NB: Small diagram of the setup.
>>
>>   DMZ                     GW/FW           ISP/Internet
>>-----------------------------------------------------------------------
>>   Server #1  --|
>>   e.f.g.h3/26  |
>>                |---- Gateway/Firewall --- ISP  WAN IP: a.b.c.d/30
>>   Server #2  --|      a.b.c.d1/30         Ext. IP: e.f.g.h/26
>>   e.f.g.h4/26         e.f.g.h1/26
>>----------------------------------------------------------------------
>>
>>_______________________________________________
>>LARTC mailing list
>>LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 
> 


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-10-25 12:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-25 12:36 [LARTC] Ip Src rewite Daniel Frederiksen
2005-10-25 12:45 ` Oscar Mechanic
2005-10-25 12:58 ` Daniel Frederiksen [this message]
2005-10-25 13:21 ` Oscar Mechanic
2005-10-25 13:25 ` Oscar Mechanic
2005-10-25 22:03 ` Daniel Frederiksen
2005-10-26  0:25 ` /dev/rob0
2005-10-26  1:20 ` Daniel Frederiksen

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=435E2BDC.1080507@cyberdoc.dk \
    --to=cyberdoc@cyberdoc.dk \
    --cc=lartc@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