From owner-freebsd-questions Tue Aug 27 12:37:32 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id MAA23997 for questions-outgoing; Tue, 27 Aug 1996 12:37:32 -0700 (PDT) Received: from yoss.canweb.net (root@yoss.canweb.net [207.0.185.8]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id MAA23992 for ; Tue, 27 Aug 1996 12:37:28 -0700 (PDT) From: satan@yoss.canweb.net Received: (from satan@localhost) by yoss.canweb.net (8.6.12/8.6.12) id PAA06068; Tue, 27 Aug 1996 15:29:13 -0400 Date: Tue, 27 Aug 1996 15:29:12 -0400 (EDT) To: questions@freebsd.org Subject: ip aliasing In-Reply-To: <2.2.32.19960827092109.0092166c@mailhost.epoch.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk My original question was: > >I am having trouble configuring my server for virtual ips. > >Its 'main' ip is 152.160.182.16 (ifconfig) > >I do the following > >ifconfig ed0 inet 152.160.5.1 alias > >route add -host 152.160.5.1 localhost > >The route command fails with 'file exists' error, and I cant ping > >the server on 152.160.5.1, even from a local machine (same LAN). > >Now, I have no problem aliasing to ips on same subnet, ie., > >aliasing to 152.160.182.224, for example. So I suspect this is a > >problem with netmask on ifconfig, but I cant figure out what it > >should be. On Tue, 27 Aug 1996, Greg Healy wrote: > shouldn't you try > ifconfig ed0 alias 152.160.5.1 netmask 255.255.255.255 I tried that too, with same results. Both of these commands put the 152.160.5.1 into the routing table (netstat -nr), but I cant ping that address. On Tue, 27 Aug 1996, Mike wrote: > For an IP alias, I use: > > ifconfig ed0 xxx.xxx.xxx.xxx netmask 255.255.255.255 alias > > I don't think you should have to add a route. Without the route, I still cannot ping that ip. Since the syntax of ifconfig command does not appear to make any difference, perhaps something else needs to be setup? The primary ip of 152.160.182.16 has absolutely no problems. --Stan