From owner-freebsd-stable@FreeBSD.ORG  Sat Feb  7 00:02:14 2004
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 794C316A4CE
	for <freebsd-stable@freebsd.org>;
	Sat,  7 Feb 2004 00:02:14 -0800 (PST)
Received: from moek.pir.net (moek.pir.net [130.64.1.215])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 2643D43D1D
	for <freebsd-stable@freebsd.org>;
	Sat,  7 Feb 2004 00:02:14 -0800 (PST)	(envelope-from pir@pir.net)
Received: from pir by moek.pir.net with local (Exim)
	id 1ApNPp-0001xe-00
	for freebsd-stable@freebsd.org; Sat, 07 Feb 2004 03:02:13 -0500
Date: Sat, 7 Feb 2004 03:02:13 -0500
From: Peter Radcliffe <pir@pir.net>
To: freebsd-stable@freebsd.org
Message-ID: <20040207080213.GA6540@pir.net>
Mail-Followup-To: freebsd-stable@freebsd.org
References: <4023C702.6010100@gopostal.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4023C702.6010100@gopostal.ca>
User-Agent: Mutt/1.4.1i
X-fish: <darwin><
X-Copy-On-Listmail: Please do NOT Cc: me on list mail.
Subject: Re: FreeBSD 4.9 ifconfig paralysing interface
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: freebsd-stable@freebsd.org
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2004 08:02:14 -0000

"Eli K. Breen" <eli@gopostal.ca> probably said:
> Using ifconfig to bring down my network interface, adding an IP alias, 
> and bringing this interface back up causes the non-aliased IP to cease 
> to be pingable and is effectively dead (no ping, ftp, ssh etc), until 
> this interface is brought down and up again.

> fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet 192.168.98.1 netmask 0xffffff00 broadcast 192.168.98.255
                                    ^^^^^^^^^^
>         inet6 fe80::2d0:b7ff:fe5a:cb7e%fxp0 prefixlen 64 scopeid 0x2
>         inet 192.168.98.2 netmask 0xffffff00 broadcast 192.168.98.255
                                    ^^^^^^^^^^
>         ether 00:d0:b7:5a:cb:7e
>         media: Ethernet autoselect (100baseTX <full-duplex>)
>         status: active

`man ifconfig`;

     alias   Establish an additional network address for this interface.  This
             is sometimes useful when changing network numbers, and one wishes
             to accept packets addressed to the old interface.  If the address
             is on the same subnet as the first network address for this
             interface, a non-conflicting netmask must be given.  Usually
             0xffffffff is most appropriate.

P.

-- 
pir