From owner-freebsd-hackers Tue Oct 10 09:30:45 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id JAA24766 for hackers-outgoing; Tue, 10 Oct 1995 09:30:45 -0700 Received: from brasil.moneng.mei.com (brasil.moneng.mei.com [151.186.20.4]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA24760 for ; Tue, 10 Oct 1995 09:30:40 -0700 Received: (from jgreco@localhost) by brasil.moneng.mei.com (8.7.Beta.1/8.7.Beta.1) id LAA18006; Tue, 10 Oct 1995 11:29:34 -0500 From: Joe Greco Message-Id: <199510101629.LAA18006@brasil.moneng.mei.com> Subject: Re: aliases and INADRR_ANY To: paul@netcraft.co.uk Date: Tue, 10 Oct 1995 11:29:32 -0500 (CDT) Cc: hackers@freebsd.org In-Reply-To: <199510101611.RAA17454@alpha.netcraft.co.uk> from "Paul Richards" at Oct 10, 95 05:11:58 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org Precedence: bulk > Do people expect daemons bound to INADDR_ANY to listen to aliases > that are added after they are started. I would expect that INADDR_ANY would listen to new aliases AND new interfaces. I don't recall whether or not it works this way, but suspect it does at least for the interface scenario. IMHO, alias generally == interface conceptually, so they should behave similarly. I would expect that daemons that bind on a per-interface/alias basis would occasionally rescan the interface list, but I know for a fact not everybody does this. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847