|
Home > Archive > Unix administration > January 2004 > inetd question
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| Dieter Montanez 2004-01-23, 5:08 pm |
| How can i restrict inetd services in "inetd.conf " to specific interfaces ?
| |
| those who know me have no need of my name 2004-01-23, 5:08 pm |
| in comp.unix.admin i read:
quote:
>How can i restrict inetd services in "inetd.conf " to specific interfaces ?
consult your documentation.
--
a signature
| |
| Lew Pitcher 2004-01-23, 5:08 pm |
| Dieter Montanez wrote:quote:
> How can i restrict inetd services in "inetd.conf " to specific interfaces ?
From inetd(8)
Upon execution, inetd reads its configuration information from a configu-
ration file which, by default, is /etc/inetd.conf. There must be an
entry for each field of the configuration file, with entries for each
field separated by a tab or a space. Comments are denoted by a ``#'' at
the beginning of a line. There must be an entry for each field. The
fields of the configuration file are as follows:
service name
socket type
protocol
wait/nowait[.max]
user[.group] or user[:group]
server program
server program arguments
....
For internet services, the first field of the line may also have a host
address specifier prefixed to it, separated from the service name by a
colon. If this is done, the string before the colon in the first field
indicates what local address inetd should use when listening for that
service. Multiple local addresses can be specified on the same line,
separated by commas. Numeric IP addresses in dotted-quad notation can be
used as well as symbolic hostnames. Symbolic hostnames are looked up
using gethostbyname(). If a hostname has multiple address mappings,
inetd creates a socket to listen on each address.
The single character ``*'' indicates INADDR_ANY, meaning ``all local
addresses''.
So, apparently, you just prefix the service name with the IP addresses you
want it to activate from. That is to say, in /etc/inetd.conf, change
time dgram udp wait root internal
to
127.0.0.1:time dgram udp wait root internal
Use the IP addresses of the interfaces that you want inetd to listen to.
--
Lew Pitcher
Master Codewright and JOAT-in-training
Registered Linux User #112576 (http://counter.li.org/)
Slackware - Because I know what I'm doing.
| |
| Ian Zimmerman 2004-01-23, 5:08 pm |
|
Dieter> How can i restrict inetd services in "inetd.conf " to specific
Dieter> interfaces ?
There are different inetd's out there. The "default" Linux one (from
netkit package) has no way. The OpenBSD one has, just read the manpage.
--
"Rap music is our punishment for neglecting music education."
An anonymous teacher
| |
| Michael Paoli 2004-01-23, 5:08 pm |
| You may also want to consider using xinetd instead of inetd.
http://www.xinetd.org/
Dieter Montanez <dieter@plantcomputers.com> wrote in message news:<c%iqb.33983$BX.23666@bignews5.bellsouth.net>...quote:
> How can i restrict inetd services in "inetd.conf " to specific interfaces ?
|
|
|
|
|