From owner-freebsd-current@FreeBSD.ORG Fri Nov 5 21:52:20 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5FB1316A4CE; Fri, 5 Nov 2004 21:52:20 +0000 (GMT) Received: from hub.org (hub.org [200.46.204.220]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2D64543D48; Fri, 5 Nov 2004 21:52:20 +0000 (GMT) (envelope-from scrappy@hub.org) Received: from localhost (unknown [200.46.204.144]) by hub.org (Postfix) with ESMTP id AE13112A73C; Fri, 5 Nov 2004 17:52:16 -0400 (AST) Received: from hub.org ([200.46.204.220]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 73805-03; Fri, 5 Nov 2004 21:52:16 +0000 (GMT) Received: from ganymede.hub.org (blk-222-46-91.eastlink.ca [24.222.46.91]) by hub.org (Postfix) with ESMTP id 4A12312A73B; Fri, 5 Nov 2004 17:52:16 -0400 (AST) Received: by ganymede.hub.org (Postfix, from userid 1000) id 8BD693927B; Fri, 5 Nov 2004 17:52:18 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 8AB5038533; Fri, 5 Nov 2004 17:52:18 -0400 (AST) Date: Fri, 5 Nov 2004 17:52:18 -0400 (AST) From: "Marc G. Fournier" To: freebsd-stable@freebsd.org Message-ID: <20041105174622.W46679@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at hub.org cc: freebsd-current@freebsd.org Subject: "bug" with ifconfig ... ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Nov 2004 21:52:20 -0000 I just made one of my 4.x remote servers inaccessible and just tested it on my 5.x laptop, and it does the same thing ... not sure if this is considered a 'desirable' effect, or a but ... but ... 'ifconfig -alias' will wipe out all IPs on the device: mobile# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 rl0: flags=8843 mtu 1500 options=8 inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255 ether 00:0d:88:22:78:e4 media: Ethernet 10baseT/UTP status: active mobile# ifconfig rl0 -alias mobile# ifconfig -a lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 rl0: flags=8843 mtu 1500 options=8 ether 00:0d:88:22:78:e4 media: Ethernet 10baseT/UTP status: active I was running a script that happened to pick up a 'zero length' IP (and I hadn't properly tested for it), so erased all the IPs configured on that device, instead of generating an error ... Checking the man page, if this *is* desired effect, a bit of a warning might be in order: " -alias Remove the network address specified. This would be used if you incorrectly specified an alias, or it was no longer needed. If you have incorrectly set an NS address having the side effect of specifying the host portion, removing all NS addresses will allow you to respecify the host portion." "Remove the network address specified.", to me, means that if one isn't specified, nothing should/would happen :( ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664