From owner-freebsd-hackers Thu Nov 7 11:35:25 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA12719 for hackers-outgoing; Thu, 7 Nov 1996 11:35:25 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA12707 for ; Thu, 7 Nov 1996 11:35:24 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id KAA17683 for ; Thu, 7 Nov 1996 10:35:55 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA10376; Thu, 7 Nov 1996 11:27:25 -0700 From: Terry Lambert Message-Id: <199611071827.LAA10376@phaeton.artisoft.com> Subject: Re: still no response To: proff@suburbia.net (Julian Assange) Date: Thu, 7 Nov 1996 11:27:24 -0700 (MST) Cc: julian@whistle.com, hackers@freebsd.org In-Reply-To: <199611070318.OAA21381@suburbia.net> from "Julian Assange" at Nov 7, 96 02:18:52 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > +Lines starting with '/' in the configuration file are special directives to > +.Nm inetd . > +At present the following directives are supported: > +.Bd -literal > +/bind iface1|ANY...iface_n bind following service entries to > + these interfaces > +/bind+ iface1...iface_n as above, but add specified ifaces to > + the previous bind list > +.Ed > +.Pp > +If the iface name begins with "<", then the iface name is treated > +as a file with interface addresses listed as the first word per line. > +If the iface name is multi-homed in the DNS, then all addresses belonging > +to that iface name will be bound. Some notes on the "inetd.conf" "bind" changes... 1) Why not add an "-i" option to inetd ans start multiple inetd's? Clearly, the intent of the "<" syntax is to have seperate conf files per bound interface. 2) Why introduce state? Since a configuration for a single interface can span several pages of data, this is confusing. Did you consider an "interface:service" instead of "service" syntax instead? A single strtok() call could find the ':'. 3) Why are you binding by network number (or host name, which will be translated to network number and may in fact fail if this is run on a multi-homed host)? If you bound by interface name instead, it would be unambiguous... 4) Support for virtual hosting in inetd has already been implemented by Van Jacobsen (last I heard)... any reason to not use his code instead? I believe it requires the ability to determine the interface following an accept before the spawn via an ioctl() on the socket... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.