From owner-freebsd-hackers Sat May 20 09:27:23 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA02132 for hackers-outgoing; Sat, 20 May 1995 09:27:23 -0700 Received: from isl.cf.ac.uk (isl-gate.elsy.cf.ac.uk [131.251.22.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA02123 for ; Sat, 20 May 1995 09:27:21 -0700 Received: (from paul@localhost) by isl.cf.ac.uk (8.6.9/8.6.9) id RAA29572; Sat, 20 May 1995 17:27:36 +0100 From: Paul Richards Message-Id: <199505201627.RAA29572@isl.cf.ac.uk> Subject: Re: alias ( secondary IP ) for Ethernet Ifaces in FreeBSD To: taob@gate.sinica.edu.tw (Brian Tao) Date: Sat, 20 May 1995 17:27:35 +0100 (BST) Cc: freebsd-hackers@FreeBSD.org In-Reply-To: from "Brian Tao" at May 19, 95 08:23:50 pm X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1713 Sender: hackers-owner@FreeBSD.org Precedence: bulk In reply to Brian Tao who said > > On Wed, 17 May 1995, Paul Richards wrote: > > > > Wait until after 2.0.5, I'm going to need this functionality for > > work (setting up a web site that supports virtual domains) and after > > playing around with it I think ifconfig needs to be changed to handle > > it a lot better. The current implementation isn't robust enough. > > What do you mean by that? I've noticed in my testing that on > occasion, trying to connect to an alias address from a remote Lynx > client would result in a "Network error" (connection closed by peer, > or whatever Lynx calls it). However, those appear to be related to > errors in my httpd.conf setup and not necessarily ifconfig. The ifconfig alias syntax is a little cludgy. I'd like a more robust syntax that doesn't let you make mistakes like ifconfig lnc0 131.251.22.1 alias 131.251.122.1 which will set your broadcast address to 131.251.122.1 which is wrong. I'd also like to be able to treat an alias as a separate interface and do things like ifconfig lnc0:1 and get the alias info like you can under Solaris. > > I just remembered something... a host with multiple aliases cannot > reach itself via those additional addresses. Is this a bug? I can > ping/telnet to any of the aliases from a different machine, but not > from the same machine to itself (via an alias). You need to specify a netmask for the aliases so that the routing code can distinguish between them, you can access the aliases from the host then. -- Paul Richards, Bluebird Computer Systems. FreeBSD core team member. Internet: paul@FreeBSD.org, http://www.isl.cf.ac.uk/ Phone: +44 1222 874000 x6646 (work), +44 1222 457651 (home)