Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Michael Gale <mgale@utilitran.com>
To: netfilter@lists.netfilter.org
Subject: Re: public ip on LAN
Date: Fri, 2 Jan 2004 09:47:47 -0700	[thread overview]
Message-ID: <20040102094747.145b4409.mgale@utilitran.com> (raw)
In-Reply-To: <200401021630.07811.Antony@Soft-Solutions.co.uk>

On Fri, 2 Jan 2004 16:30:07 +0000
Antony Stone <Antony@Soft-Solutions.co.uk> wrote:

> On Friday 02 January 2004 4:22 pm, Michael Gale wrote:
> 
> > On Fri, 02 Jan 2004 22:00:16 +0530
> >
> > Amit Pasari <info@amitpasari.com> 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
> >
> > 	I have never understood this configuration ... why would clients on a
> > internal LAN need public IP addresses ?
> 
> Stupid protocols which bury OSI layer 3/4 information inside layer 7 
> datagrams.
> 
> Examples: H.323, FTP, PPTP.
> 
> Without a NAT helper which understands what to change inside the packets, so 
> that it matches the headers, you can't use these protocols across NATted 
> connections.
> 
> Antony.
> 
> -- 
> In Heaven, the police are British, the chefs are Italian, the beer is Belgian, 
> the mechanics are German, the lovers are French, the entertainment is 
> American, and everything is organised by the Swiss.
> 
> In Hell, the police are German, the chefs are British, the beer is American, 
> the mechanics are French, the lovers are Swiss, the entertainment is Belgian, 
> and everything is organised by the Italians.
> 
>                                                      Please reply to the list;
>                                                            please don't CC me.
> 
> 

	Yes but usually there are special proxies available for these. But I guess if you have not other choice.


-- 
Michael Gale
Network Administrator
Utilitran Corporation


  reply	other threads:[~2004-01-02 16:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2004-01-02 17:19 Amit Pasari
2004-01-02 17:15 ` Michael Gale
2004-01-02 17:27 ` Fabien LE BLEVEC
2004-01-02 18:30   ` Craig Steadman
2004-01-02 18:42     ` Antony Stone
2004-01-02 18:46     ` Michael Gale

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=20040102094747.145b4409.mgale@utilitran.com \
    --to=mgale@utilitran.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