Date: Fri, 12 Jun 1998 02:55:57 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: "David L. Aldridge" <dlac@aldridge.com> Cc: black@cypher.net, freebsd-questions <freebsd-questions@FreeBSD.ORG> Subject: Re: IP Aliasing on FreeBSD 2.x Message-ID: <Pine.BSF.3.96.980612025521.11999e-100000@resnet.uoregon.edu> In-Reply-To: <357EC918.A26C1DA0@aldridge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 10 Jun 1998, David L. Aldridge wrote: > Ben, > I read your disclaimer and fully understand the busy/grouchy thing. So, if you > don't feel like branching to IP Aliasing at the moment, please use the Del key. > > I recently upgraded to FreeBSD 2.2.6 and lost the ability to ping an aliased > address from the box on which it is aliased. From the outside yes. It worked > before the upgrade. > I don't particularly wish to add routes during boot and wish to understand why > it has ceased working. Routing, I think. It hasn't worked for a while tho. If you want to be able to ping it add a route from the alias to 127.0.0.1. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980612025521.11999e-100000>