From owner-freebsd-stable@FreeBSD.ORG Mon Feb 12 18:23:40 2007 Return-Path: X-Original-To: freebsd-stable@FreeBSD.ORG Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02C5516A400; Mon, 12 Feb 2007 18:23:40 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [83.120.8.8]) by mx1.freebsd.org (Postfix) with ESMTP id 6AE8A13C494; Mon, 12 Feb 2007 18:23:39 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (zyrozo@localhost [127.0.0.1]) by lurza.secnetix.de (8.13.4/8.13.4) with ESMTP id l1CINXLD066224; Mon, 12 Feb 2007 19:23:38 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.13.4/8.13.1/Submit) id l1CINXHt066223; Mon, 12 Feb 2007 19:23:33 +0100 (CET) (envelope-from olli) Date: Mon, 12 Feb 2007 19:23:33 +0100 (CET) Message-Id: <200702121823.l1CINXHt066223@lurza.secnetix.de> From: Oliver Fromme To: freebsd-stable@FreeBSD.ORG, brooks@FreeBSD.ORG In-Reply-To: <20070212175940.GA52751@lor.one-eyed-alien.net> X-Newsgroups: list.freebsd-stable User-Agent: tin/1.8.2-20060425 ("Shillay") (UNIX) (FreeBSD/4.11-STABLE (i386)) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Mon, 12 Feb 2007 19:23:38 +0100 (CET) Cc: Subject: Re: Desired behaviour of "ifconfig -alias" X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-stable@FreeBSD.ORG, brooks@FreeBSD.ORG List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2007 18:23:40 -0000 Brooks Davis wrote: > Oliver Fromme wrote: > > Brooks Davis wrote: > > > ipv4_addrs_ is a much better replacement IMO. It's easy to > > > use and doesn't required the hackish pseudo array traversal used by > > > ifconfig_iface_aliasX. > > > > That might work for simple cases, but how do you specify > > other parameters beside the IPs if you need to? > > What do you need to set? It's sets IP and netmask. It doesn't handle > broadcast, but I'd be pretty suprised if that's needed often. True, not often, but sometimes. I had cases like that in certain environments with bridged networks and arp proxies. I'm fine with your proposed syntax, as long as all the existing ifconfig possibilities continue to be possible, i.e. no regression. > is needed? Axing ifconfig_iface_aliasX is not needed, but reducing the > visiability of the interface in the documentation is probably in order > particularly since it's quite fragile since you have to renumber whenever > you remove an entry. Yup, I agree, that's a PITA. That could be solved in the shell code, though, by not enumerating until a number doesn't exist, but instead looking at the set of all shell variables that have been set, similar to this: set | grep "^ifconfig_${IFACE}_alias" | cut -f1 -d= | ... Best regards Oliver -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, USt-Id: DE204219783 Any opinions expressed in this message are personal to the author and may not necessarily reflect the opinions of secnetix GmbH & Co KG in any way. FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "C is quirky, flawed, and an enormous success." -- Dennis M. Ritchie.