From owner-freebsd-bugs Wed Aug 30 8:10: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 0BAAE37B42C for ; Wed, 30 Aug 2000 08:10:04 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id IAA85174; Wed, 30 Aug 2000 08:10:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 30 Aug 2000 08:10:04 -0700 (PDT) Message-Id: <200008301510.IAA85174@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Ruslan Ermilov Subject: Re: kern/20785: changing interface IP in same subnet doesn't propagate properly Reply-To: Ruslan Ermilov Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/20785; it has been noted by GNATS. From: Ruslan Ermilov To: Robert Watson Cc: bug-followup@FreeBSD.org Subject: Re: kern/20785: changing interface IP in same subnet doesn't propagate properly Date: Wed, 30 Aug 2000 18:00:07 +0300 On Tue, Aug 22, 2000 at 02:06:06PM -0400, rwatson@FreeBSD.org wrote: > > Changing the IP address of an interface may not necessarily cause new > sockets to make use of the new IP address, if the address is in the same > subnet as the previous address under IPv4. This only seems to affect > outgoing packets to non-local addresses; the correct IP is used for outgoing > local packets on the subnet. > I recently experienced this bug (with exact the same workaround) when I was playing with my libalias(3) ICMP fixes. Yesterday, when I was playing with my kernel ICMP error generation fixes, I noticed that a similar bug happens with `-reject' static routes and thought that this might be related to this bug. 1. Add the `-reject' route on your gateway machine: # route add -host 1.2.3.4 -iface lo0 -reject 2. From another box ping this host: $ ping -c1 1.2.3.4 You will not see the ICMP unreachable message. 3. On the router box, re-add the default route: # route delete default # route add default $foo 4. From another box try to ping this host again: $ ping -c1 1.2.3.4 Now you will see the ICMP unreachable message. -- Ruslan Ermilov Oracle Developer/DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message