From owner-freebsd-hackers  Thu May 20  9:13:15 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from horse.supranet.net (horse.supranet.net [205.164.160.8])
	by hub.freebsd.org (Postfix) with ESMTP id 1D55A15011
	for <hackers@freebsd.org>; Thu, 20 May 1999 09:13:12 -0700 (PDT)
	(envelope-from gavinb@supranet.net)
Received: from rat (rat.supranet.net [205.164.160.15])
	by horse.supranet.net (8.9.3/8.9.3) with SMTP id LAA21026;
	Thu, 20 May 1999 11:12:43 -0500 (CDT)
Message-Id: <4.1.19990520110819.00d2a7a0@mail.supranet.net>
X-Sender: gavinb@mail.supranet.net
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
Date: Thu, 20 May 1999 11:11:14 -0500
To: "Chuck Youse" <cyouse@cybersites.com>
From: Benjamin Gavin <gavinb@supranet.net>
Subject: Re: Dumb IP alias confusion.
Cc: hackers@freebsd.org
In-Reply-To: <004401bea2da$7685c100$4d7b5ccf@f8m7n1>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Hi,
  You need to either set the netmask of the alias address to
255.255.255.255, or add a manual route statement:

route add <alias_address> 127.1

  That will do it.  Then you will be able to get to the alias address from
the aliased machine.  On a side note:

1.  Does anyone know how to get this same thing to work with natd??  i.e.
is there a way for the natd box to see ports that it is redirecting as they
would be seen from the outside world??  I am pretty sure that the Cisco PIX
firewalls will do this, but I was wondering if it was possible with FreeBSD.

Thanks,
Ben Gavin

At 12:04 PM 5/20/99 -0400, you wrote:
>I didn't notice this until recently, but on our production web servers I use
>IP aliasing to host multiple sites on one box.  Pretty normal stuff.  Here's
>an ifconfig on one of these boxes:
>
>xl0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet 208.156.59.51 netmask 0xffffff00 broadcast 208.156.59.255
>        inet 208.156.59.10 netmask 0xffffff00 broadcast 208.156.59.255
>        ether 00:10:5a:e4:87:22
>        media: 100baseTX <full-duplex>
>        supported media: autoselect 100baseTX <full-duplex> 100baseTX
><half-dupl
>ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex>
>10baseT/UTP
>xl1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255
>        ether 00:10:5a:e4:87:0d
>        media: 100baseTX <full-duplex>
>        supported media: autoselect 100baseTX <full-duplex> 100baseTX
><half-dupl
>ex> 100baseTX 10baseT/UTP <full-duplex> 10baseT/UTP <half-duplex>
>10baseT/UTP
>lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
>        inet 127.0.0.1 netmask 0xff000000
>
>Looks pretty good.  The only problem is that connections from the local
>machine will only connect to the _first_ (or "real") IP address for an
>interface.  A connection, for example, from this machine to 208.156.59.10
>just hangs ...
>
>I'm assuming that I've simply forgotten some configuration step.  This box
>is running 3.1-STABLE/May-9.
>
>Chuck Youse
>Director of Systems
>cyouse@cybersites.com
>
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-hackers" in the body of the message

/--------------------------------------------------------------------------/
  Benjamin Gavin - Senior Consultant

  ***********  NO SPAM!!  ************


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message