From owner-freebsd-hackers  Thu May 20  9: 6:32 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from nero.cybersites.com (nero.cybersites.com [207.92.123.21])
	by hub.freebsd.org (Postfix) with ESMTP id 693ED15034
	for <freebsd-hackers@freebsd.org>; Thu, 20 May 1999 09:06:29 -0700 (PDT)
	(envelope-from cyouse@cybersites.com)
Received: from f8m7n1 (dhcp77.cybersites.com [207.92.123.77])
	by nero.cybersites.com (8.8.7/8.8.7) with SMTP id LAA27925
	for <freebsd-hackers@freebsd.org>; Thu, 20 May 1999 11:12:27 -0400
Message-ID: <004401bea2da$7685c100$4d7b5ccf@f8m7n1>
From: "Chuck Youse" <cyouse@cybersites.com>
To: <freebsd-hackers@freebsd.org>
Subject: Dumb IP alias confusion.
Date: Thu, 20 May 1999 12:04:37 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.1
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

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