From owner-freebsd-questions Wed Oct 22 19:20:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20625 for questions-outgoing; Wed, 22 Oct 1997 19:20:49 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA20619 for ; Wed, 22 Oct 1997 19:20:46 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.7/8.8.5) with SMTP id TAA01778; Wed, 22 Oct 1997 19:20:34 -0700 (PDT) Date: Wed, 22 Oct 1997 19:20:34 -0700 (PDT) From: Doug White Reply-To: Doug White To: Mark Stout cc: freebsd-questions@FreeBSD.ORG Subject: Re: HELP: Example of aliased IP error messages In-Reply-To: <3.0.1.32.19971017131719.00c1cc10@vpm.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 17 Oct 1997, Mark Stout wrote: > I need help in fixing the following errors. I'm using 2.2.1 from the > subscription CD that was used to upgrade a 2.1.5R machine. I've installed > this CD on two other machines with no problems, but this one machine is > having alot of problems. > > Here's what I get when I enter the following command: > spunky:[2]#ifconfig de0 alias 209.60.152.110 netmask 255.255.255.255 > > Here's the output from a remote machine pinging this aliased IP address > fm1: {18} ping 209.60.152.110 > PING 209.60.152.110 (209.60.152.110): 56 data bytes > 64 bytes from 209.60.152.110: icmp_seq=0 ttl=255 time=0.468 ms > 64 bytes from 209.60.152.110: icmp_seq=1 ttl=255 time=1.039 ms > 64 bytes from 209.60.152.110: icmp_seq=2 ttl=255 time=0.439 ms > > So it can be pinged from a remote system. Now, here it is on the same > pmachine that has the aliased IP adddress > spunky:[3]# > PING 209.60.152.110 (209.60.152.110): 56 data bytes > > > Now, can someone tell me why these are occuring and how I can fix them? I've seen this happen on other IP aliased machines. I need to experiment with this myself, but I just though that perhaps the loopback interface routes are interfereing with this. > ------------------------------- > Contents from /var/log/syslog > ------------------------------- > Oct 17 13:03:38 spunky /kernel: > arpresolve: can't allocate llinfo for 209.60.152.110 > Oct 17 13:03:38 spunky routed[56]: > write(rt_sock) RTM_ADD 209.60.152.216/32 --> 209.60.152.216: > Can't assign requested address > Oct 17 13:03:39 spunky /kernel: > Oct 17 13:03:43 spunky /kernel: arp_rtrequest: bad gateway value This is definitely routing. Try killing routed if you aren't using it. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major