Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Fabien LE BLEVEC <fleblevec@nerim.net>
Cc: netfilter@lists.netfilter.org
Subject: Re: public ip on LAN
Date: Fri, 02 Jan 2004 18:27:23 +0100	[thread overview]
Message-ID: <3FF5A9FB.7000302@nerim.net> (raw)
In-Reply-To: <6.0.0.22.0.20040102224831.044036c0@amitpasari.com>


In the PREROUTING chain, you said for example :

iptables -A PREROUTING -s 203.122.51.179 -j DNAT --to 172.16.1.2
iptables -A PREROUTING -s 203.122.51.180 -j DNAT --to 172.16.1.3
....
or more accurate :
iptables -A PREROUTING -s 203.122.51.181 -p tcp --dport 80 -j DNAT --to 
172.16.1.4
...

I think it should  be correct for your configuration.

Don't forget to authorize the traffic in the FORWARD chain .


Fabien


Amit Pasari a écrit :

> Thanks John,
> Let me explain
> on My LAN i have ip address - 172.16.1.1
> subnet - 255.255.0.0
> on My WAN i have ipaddress - 203.122.51.178
> subnet - 255.255.255.240
>
> Now , my clients want to have public / Live ip instead of private ips 
> which i am giving as  many of my clients uses webserver , and other 
> applications which people from outside world needs to access .
> I can redirect  ports for one clients but how about 10 clients wanting 
> the same .
> So i need to give them a public ip so that all the traffic can be 
> redirected their ip .
>
>
> Regards
> Amit
>
> At 09:54 PM 1/2/04, you wrote:
>
>> On Fri, 2004-01-02 at 11:30, Amit Pasari wrote:
>> > Hello,
>> > I am using Redhat 8.0 with iptables to provide my client internet 
>> services
>> > . Everything is going well .
>> > i have been giving private ips of 172.16.0.0 series to my clients .
>> > But now some of my clients need public ips . i do have many public 
>> ips with
>> > me .so can somebody tell how can i give public ips to my clients .
>> >
>> > Thanks & Regards
>> > Amit
>> > Orangeinfoways.com
>>
>> Could you please clarify what you mean by giving ips to your clients?
>> Thanks - John
>> -- 
>> John A. Sullivan III
>> Chief Technology Officer
>> Nexus Management
>> +1 207-985-7880
>> john.sullivan@nexusmgmt.com
>> ---
>> If you are interested in helping to develop a GPL enterprise class
>> VPN/Firewall/Security device management console, please visit
>> http://iscs.sourceforge.net
>
>
>
>
>




  parent reply	other threads:[~2004-01-02 17:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02 17:19 public ip on LAN Amit Pasari
2004-01-02 17:15 ` Michael Gale
2004-01-02 17:27 ` Fabien LE BLEVEC [this message]
2004-01-02 18:30   ` Craig Steadman
2004-01-02 18:42     ` Antony Stone
2004-01-02 18:46     ` Michael Gale
2004-01-02 19:07       ` Can iptables do this ? Ramoni
2004-01-02 19:19         ` Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2004-01-02 16:30 public ip on LAN Amit Pasari
2004-01-02 16:22 ` Michael Gale
2004-01-02 16:30   ` Antony Stone
2004-01-02 16:47     ` Michael Gale
2004-01-02 16:23 ` Antony Stone
2004-01-02 17:40   ` Amit Pasari
2004-01-02 17:31     ` John A. Sullivan III
2004-01-02 17:42       ` Michael Gale
2004-01-02 16:24 ` John A. Sullivan III
     [not found]   ` <6.0.0.22.0.20040102223444.0305cdb0@amitpasari.com>
2004-01-02 17:01     ` John A. Sullivan III

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=3FF5A9FB.7000302@nerim.net \
    --to=fleblevec@nerim.net \
    --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