*BSD News Article 97506


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!metro!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news-peer.sprintlink.net!news.sprintlink.net!Sprint!newsxfer3.itd.umich.edu!newsxfer.itd.umich.edu!news.mtu.edu!msunews!gvsu!river.it.gvsu.edu!behrensm
From: behrensm@river.it.gvsu.edu (Matt Behrens)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: IP Aliasing
Date: 10 Jun 1997 16:55:09 GMT
Organization: Grand Valley State University
Lines: 33
Message-ID: <5nk0td$hid@news.gvsu.edu>
References: <01bc576a$ff7a8260$64d91dce@phishhead.dawtech.com> <86afmc5qqm.fsf@bitbox.follo.net> <339cc8f2.88895331@news.mindspring.com> <5njja2$dnh@news.gvsu.edu> <1997Jun10.152644.14248@bilver.oau.org>
NNTP-Posting-Host: river.it.gvsu.edu
X-Newsreader: TIN [version 1.2 PL0]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:42719

Bill Vermillion (bill@bilver.oau.org) wrote:

: Matt Behrens <behrensm@river.it.gvsu.edu> wrote:

: >This is a different type of aliasing, no?
: >
: >What the original poster wanted to know about was what should really be
: >called IP masquerading.  Aliasing is a different animal.  But then again
: >we call our slices partitions and our partitions slices so who cares :)

: So what is the difference between masquerading and aliasing.

: They appeared (to me) to do the same thing, and I assumed
: (wrongly I guess) that different OSes named them differently.

Aliasing has always meant, AFAIK, simply allowing an IP address to respond
to packets sent to a different number.  i.e. if you have a machine
10.0.0.1 and you want to move it to 10.0.10.1, you alias 10.0.10.1 to
10.0.0.1 and all packets sent to 10.0.10.1 and 10.0.0.1 arrive at
10.0.0.1.  When you're finished with the move, of course, you remove the
alias.

Masquerading (or NAT, network address translation) is the act of providing
a sort of "front" for a number of different hosts on a remote network that
doesn't understand their numbers.  In this example, 10.0.0.1, 10.0.0.2,
and 10.0.0.3 can all use 10.10.10.10 to use services on a network that
knows 10.10.10.10 but can't route to 10.0.0.x.

--
  Matt Behrens
  Zigg Computer Services
  zigg@iserv.net
  http://www.iserv.net/~zigg/