From owner-freebsd-stable Wed Feb 27 13:17:13 2002 Delivered-To: freebsd-stable@freebsd.org Received: from rwcrmhc53.attbi.com (rwcrmhc53.attbi.com [204.127.198.39]) by hub.freebsd.org (Postfix) with ESMTP id 1D61D37B400 for ; Wed, 27 Feb 2002 13:17:06 -0800 (PST) Received: from max ([12.254.136.195]) by rwcrmhc53.attbi.com (InterMail vM.4.01.03.27 201-229-121-127-20010626) with SMTP id <20020227211702.UGJQ2951.rwcrmhc53.attbi.com@max>; Wed, 27 Feb 2002 21:17:02 +0000 Message-ID: <05ca01c1bfd4$5b809550$0900a8c0@max> From: "John Nielsen" To: , "David A. Koran" References: Subject: Re: ifconfig aliases Date: Wed, 27 Feb 2002 14:18:52 -0700 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 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG ----- Original Message ----- From: "David A. Koran" To: Sent: Wednesday, February 27, 2002 1:51 PM Subject: ifconfig aliases > Did somebody make a change to the syntax of how the ifconfig aliases > (eg. "ifconfig_fxp0_alias1="inet some.ip.addr.ess netmask > some.net.mask.num") work? According to the old listings (and many > FreeBSD docs of the past) the netmask of the aliases in the past used > to be whatever your base netmask was. For example, this used to be > legal: > > ifconfig_fxp0="inet AAA.BBB.CCC.190 netmask 255.255.255.128" > ifconfig_fxp0_alias0="inet AAA. BBB.DDD.209 netmask 255.255.255.248" > ifconfig_fxp0_alias1="inet AAA. BBB.DDD.210 netmask 255.255.255.248" > ifconfig_fxp0_alias2="inet AAA. BBB.DDD.211 netmask 255.255.255.248" > ifconfig_fxp0_alias3="inet AAA. BBB.DDD.212 netmask 255.255.255.248" > ifconfig_fxp0_alias4="inet AAA. BBB.DDD.213 netmask 255.255.255.248" > ifconfig_fxp0_alias5="inet AAA. BBB.DDD.214 netmask 255.255.255.248" > > > now it's enforced in this way > > ifconfig_fxp0="inet AAA.BBB.CCC.190 netmask 255.255.255.128" > ifconfig_fxp0_alias0="inet AAA. BBB.DDD.209 netmask 255.255.255.248" > ifconfig_fxp0_alias1="inet AAA. BBB.DDD.210 netmask 255.255.255.255" > ifconfig_fxp0_alias2="inet AAA. BBB.DDD.211 netmask 255.255.255.255" > ifconfig_fxp0_alias3="inet AAA. BBB.DDD.212 netmask 255.255.255.255" > ifconfig_fxp0_alias4="inet AAA. BBB.DDD.213 netmask 255.255.255.255" > ifconfig_fxp0_alias5="inet AAA. BBB.DDD.214 netmask 255.255.255.255" > > I know in the docs, it states that if an alias is on the same subnet > of the first non-aliased 'base' address, it's required to have the > 0xffffffff subnet . However, for at least the past two to three > years, I've been able to aliases like the above (and the aliased > addresses were NOT on the same subnet as the non-aliased address) > without a problem, I recently VSup'ed today, built and installed > world (same kernel config for quite a while, just updated for > different designations from GENERIC), and I had to hack the rc.conf > to what is reflected in the second example. > > I apologize if this seems confusing, but I'm trying to track down > what exactly made the syntax change for aliases in this fashion. This bit me recently (at least, I'm pretty sure that's what the problem was). I had a machine running 4.5-RELEASE with fxp interfaces and netmasks as in your first example. Upgrading to -stable caused the aliases to behave unpredictably and generally be inaccessable. A source revert back to RELENG_4_5 didn't revert the behavior. Since I was on a tight schedule and it didn't occur to me until recently that it was probably the netmask, I did a clean reinstall of 4.5-RELEASE. I won't be much help in tracking down the specific change, but I can at least confirm that it's not particular to you. :) JN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message