Date: Thu, 28 May 1998 17:14:04 +0100 From: njs3@doc.ic.ac.uk (Niall Smart) To: Max Euston <meuston@jmrodgers.com>, "'Niall Smart'" <njs3@doc.ic.ac.uk>, "freebsd-bugs@FreeBSD.ORG" <freebsd-bugs@FreeBSD.ORG> Subject: RE: kern/6774: bind(3)/libc improvement Message-ID: <E0yf5Jc-0002IG-00@oak66.doc.ic.ac.uk> In-Reply-To: Max Euston <meuston@jmrodgers.com> "RE: kern/6774: bind(3)/libc improvement" (May 28, 12:09pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On May 28, 12:09pm, Max Euston wrote: } Subject: RE: kern/6774: bind(3)/libc improvement > On Thursday, May 28, 1998 11:58 AM, Niall Smart [SMTP:njs3@doc.ic.ac.uk] > wrote: > > On May 28, 9:50am, Max Euston wrote: > [snip] > > > I haven't used it, but man inetd says: > > > > > > -a Specify a specific IP address to bind to. > > > > Hrm, wasn't aware of that, I think a better way is to specify for each > > service which addresses it should listen on. Perhaps you could do > > this using multiple inetd's and configuration files, but thats messy. > > Then again, changing inetd.conf's syntax isn't exactly desirable either, > > probably. > > I agree, multiple inetd & inetd.conf files could be messy, but I wanted to > do this on a "gateway" machine to allow only certain services on certain > interfaces (I currently use ipfw, but the rules can get to be a little > complex). If I find any elegant solutions, I will let you know. Well, the elegant solution seems to be to supplement inetd.conf's syntax to support specifying which address to bind to. Are you using ipfw to prevent packets recieved on one interface from being passed to a service bound on another interface? Niall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E0yf5Jc-0002IG-00>