From owner-freebsd-bugs Wed May 30 7:50: 9 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8171C37B422 for ; Wed, 30 May 2001 07:50:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.1/8.11.1) id f4UEo2477166; Wed, 30 May 2001 07:50:02 -0700 (PDT) (envelope-from gnats) Date: Wed, 30 May 2001 07:50:02 -0700 (PDT) Message-Id: <200105301450.f4UEo2477166@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: ryan beasley Subject: Re: bin/22489: mass IP aliasing via ifconfig broken Reply-To: ryan beasley Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR bin/22489; it has been noted by GNATS. From: ryan beasley To: Bill Swingle Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/22489: mass IP aliasing via ifconfig broken Date: Wed, 30 May 2001 09:46:10 -0500 On Tue, May 29, 2001 at 10:43:34PM -0700, Bill Swingle wrote: > Why don't you just use the aliasing mechanisim that is built into > /etc/rc.network? > > ifconfig_de0_alias0="inet 64.81.6.35 netmask 255.255.255.255" > ifconfig_de0_alias1="inet 64.81.6.36 netmask 255.255.255.255" > ifconfig_de0_alias2="inet 64.81.6.37 netmask 255.255.255.255" > ifconfig_de0_alias3="inet 64.81.6.38 netmask 255.255.255.255" > etc.... The file controlling all of the addresses is an RCS'd flat text file with _just_ IPs listed under it. The purpose is so that the "junior" types could run around and add/remove addresses to be bound to this machine. I trust them much more w/ a flat text of IPIPetc than I would anyone mucking up rc.conf. :) > I'm not so sure this is a problem with FreeBSD since there is a > perfectly reasonable way to go about this that works. Either way, the rc.network essentially does the same thing; ifconfig alias, ifconfig alias, etc. The only difference is that I use a for/do/done loop whereas rc.network uses while/do/done. Anywho, if I run ifconfig and find all the addresses I bound listed there, but they're NOT responsive to external network traffic, I think that _is_ a FreeBSD problem. ... but on another note, I completely forgot that this was still open. ca-1 is running w/ a kernel from 12/19/2000 and I couldn't replicate the behavior anymore. (woot.) Guess it's time to close the PR. ;) -- Ryan Beasley FreeBSD SysAdmin http://www.enteract.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message