Date: Wed, 30 May 2001 09:40:03 -0700 (PDT) From: Bill Swingle <unfurl@dub.net> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/22489: mass IP aliasing via ifconfig broken Message-ID: <200105301640.f4UGe3w94607@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/22489; it has been noted by GNATS. From: Bill Swingle <unfurl@dub.net> To: ryan beasley <ryanb@enteract.com> Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/22489: mass IP aliasing via ifconfig broken Date: 30 May 2001 09:36:44 -0700 On Wed, May 30, 2001 at 09:46:10AM -0500, ryan beasley wrote: > 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 IP<newline>IP<newline>etc than I would anyone mucking up > rc.conf. :) I can totally understand that. > > 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 <blah1> alias, ifconfig <blah2> alias, etc. The only > difference is that I use a for/do/done loop whereas rc.network > uses while/do/done. Have you tried while/do/done to see if it makes a difference? have you tried using the rc.network method to see if this problem exist then? > > 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. That's very true. > ... 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. ;) Glad to hear it. :) -Bill > > -- > Ryan Beasley <ryanb@enteract.com> > FreeBSD SysAdmin http://www.enteract.com -- -=| --- Bill Swingle --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org -=| Do Not Taunt Happy Fun Ball(tm) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200105301640.f4UGe3w94607>