From owner-freebsd-stable Sun Sep 23 17:12:10 2001 Delivered-To: freebsd-stable@freebsd.org Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by hub.freebsd.org (Postfix) with ESMTP id 78BA437B403 for ; Sun, 23 Sep 2001 17:12:07 -0700 (PDT) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id AB46262D01 for ; Sun, 23 Sep 2001 17:12:06 -0700 (PDT) Date: Sun, 23 Sep 2001 17:12:57 -0700 (PDT) From: Lamont Granquist To: Subject: RE: loopback not working for anything other than 127.0.0.1 In-Reply-To: <006301c1448a$78fa4dd0$0a01a8c0@den2> Message-ID: <20010923170355.N36356-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 24 Sep 2001, Juha Saarinen wrote: > I thought about some of the things mentioned in that thread, and having > the ability to use some of the 127/8 addresses could actually be useful. > Is it possible to create aliases for the loopback interface? yes, ifconfig lo0 inet 127.0.0.2 netmask 0xffffffff alias works just fine. i do agree, though, that the lack of a route for 127/8 does seem to break the RFC. it states that 127/8 isn't supposed to leave the host, but: # tcpdump host 127.1.1.1 tcpdump: listening on fxp0 17:11:49.048088 192.168.69.11 > 127.1.1.1: icmp: echo request 17:11:50.053303 192.168.69.11 > 127.1.1.1: icmp: echo request 17:11:51.063315 192.168.69.11 > 127.1.1.1: icmp: echo request clearly they do. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message