Date: Mon, 3 May 1999 17:50:49 -0500 From: Dan Nelson <dnelson@emsphone.com> To: Pete Nelson <webmaster@ci.stpaul.mn.us> Cc: questions@FreeBSD.ORG Subject: Re: binding inetd to a single interface Message-ID: <19990503175049.A42198@dan.emsphone.com> In-Reply-To: <372E18AC.E18EB509@ci.saint-paul.mn.us>; from "Pete Nelson" on Mon May 3 16:44:12 GMT 1999 References: <372E18AC.E18EB509@ci.saint-paul.mn.us>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (May 03), Pete Nelson said:
> I've been searching for inetd documentation that goes beyond basic.
> I've learned a lot of interesting things, most of which I didn't know
> before, but I still haven't found the answer I'm searching for.
>
> I've got a linux (sorry) box with several virtual webservers. The
> original plan was not to have a web server on the main interface, but
> have that interface be the only one that responds to inetd services.
> Is there a way that I can tell inetd to bind to that IP, and not to
> the rest of the virtual hosts? What gets particularly annoying, my
> logs show all services as going to the very last interface on the
> system, no matter which IP you request. Personnally, I'd really like
> my logs to show the host that the user asked to connect to.
>
> Any suggestions?
man inetd?
inetd [-d] [-l] [-c maximum] [-C rate] [-a address] [-p filename]
[-R rate] [configuration file]
-a Specify a specific IP address to bind to.
If you need small changes, simply edit the inetd sources in
/usr/src/usr.sbin/inetd. Or take a look at xinetd in ports.
-Dan Nelson
dnelson@emsphone.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990503175049.A42198>