From owner-freebsd-isp  Fri Feb 14 04:00:53 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA28512
          for isp-outgoing; Fri, 14 Feb 1997 04:00:53 -0800 (PST)
Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA28481
          for <freebsd-isp@freebsd.org>; Fri, 14 Feb 1997 04:00:44 -0800 (PST)
Received: (from ernie@localhost) by spooky.eis.net.au (8.8.5/8.6.12) id WAA23654 for freebsd-isp@freebsd.org; Fri, 14 Feb 1997 22:00:28 +1000 (EST)
From: Ernie Elu <ernie@spooky.eis.net.au>
Message-Id: <199702141200.WAA23654@spooky.eis.net.au>
Subject: Aliases
To: freebsd-isp@freebsd.org
Date: Fri, 14 Feb 1997 22:00:28 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,
in the past I have been running freebsd-2.1.6 and decided to upgrade one of
my web servers to freebsd 2.2-GAMMA, the upgrade went fine except for 3
single i/p aliases that I had that were all bound to ed0

ie.

ifconfig ed0 alias a.b.c.d netmask 0xffffffff
ifconfig ed0 alias e.f.g.h netmask 0xffffffff

etc.

After rebooting with the 2.2-GAMMA kernel ony the first of the 3 aliases 
could be pinged. I played around for a while with no luck so I tried binding
the 3 aliases to the lo device instead of ed0 and all worked fine.

I am happy to leave it that way but I would like someone to share any ideas
as to what happened between 2.1.6 and 2.2-GAMMA to make the original config
break.

The upgrade technique I used was to install all the 2.2-GAMMA source tree
and do a make world then rebuild the kernel.

- Ernie.