[Wylug-help] Possible TCP wrapper problem - inetd daemon - cannot connect
RichardNevilleRichard@origin-unknown.fsnet.co.uk
RichardNevilleRichard at origin-unknown.fsnet.co.uk
Wed, 23 Aug 2000 21:36:42 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_0051_01C00D4A.3A8AF4A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Hi,
Possible TCP wrapper problem -
inetd daemon - cannot connect
I've installed red hat linux 6.2 (KDE).
I added the following to "/etc/hosts"
192.168.1.2 richspc localhost.localdomain localhost
192.168.1.1 riscpc
I then installed the inetd daemon "rpm -Uvh inetd-0.16-4.i386.rpm"
to enable services like ftp, telnet and talk etc.
I checked the "/etc/inetd.conf" file and everything
seems fine (see attached). I also rebooted to ensure
that the inetd daemon was started for sure.
In order to test the ftp server, I thought I'd ftp to
myself - "ftp richspc". Although I get the message
"Connected to richspc", the connection is eventually
dropped as service unavailable. I initally thought this
was due to the TCP wrapper, so I added the IP addresses
to "/etc/hosts.allow" (see attached) and restarted the inetd
daemon "killall -HUP inetd". After no success I rebooted.
Again I was able to connect, but the connection was dropped.
I looked in the /var/log/secure file and the last message was:
Aug 23 20:33:11 richspc in.ftpd[669]: connect from richspc
Aug 23 20:33:11 richspc in.ftpd[669]: error: cannot execute
/usr/sbin/in.ftpd: No such file or directory
Does anyone know if there anything else I would need to install
to resolve this problem, I'm really stuck here as I don't know what
to try next.
I used to use SuSE linux and could test the inetd daemon by
connecting to myself, is RedHat different ?
Thanks in advance for help.
Richard.
richard@origin-unknown.fsnet.co.uk
------=_NextPart_000_0051_01C00D4A.3A8AF4A0
Content-Type: application/octet-stream;
name="inetd.conf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="inetd.conf"
#=0A=
# inetd.conf This file describes the services that will be available=0A=
# through the INETD TCP/IP super server. To re-configure=0A=
# the running INETD process, edit this file, then send the=0A=
# INETD process a SIGHUP signal.=0A=
#=0A=
# Version: @(#)/etc/inetd.conf 3.10 05/27/93=0A=
#=0A=
# Authors: Original taken from BSD UNIX 4.3/TAHOE.=0A=
# Fred N. van Kempen, <waltje@uwalt.nl.mugnet.org>=0A=
#=0A=
# Modified for Debian Linux by Ian A. Murdock <imurdock@shell.portal.com>=0A=
#=0A=
# Modified for RHS Linux by Marc Ewing <marc@redhat.com>=0A=
#=0A=
# <service_name> <sock_type> <proto> <flags> <user> <server_path> <args>=0A=
#=0A=
# Echo, discard, daytime, and chargen are used primarily for testing.=0A=
#=0A=
# To re-read this file after changes, just do a 'killall -HUP inetd'=0A=
#=0A=
#echo stream tcp nowait root internal=0A=
#echo dgram udp wait root internal=0A=
#discard stream tcp nowait root internal=0A=
#discard dgram udp wait root internal=0A=
#daytime stream tcp nowait root internal=0A=
#daytime dgram udp wait root internal=0A=
#chargen stream tcp nowait root internal=0A=
#chargen dgram udp wait root internal=0A=
#time stream tcp nowait root internal=0A=
#time dgram udp wait root internal=0A=
#=0A=
# These are standard services.=0A=
#=0A=
ftp stream tcp nowait root /usr/sbin/tcpd in.ftpd -l -a=0A=
telnet stream tcp nowait root /usr/sbin/tcpd in.telnetd=0A=
#=0A=
# Shell, login, exec, comsat and talk are BSD protocols.=0A=
#=0A=
shell stream tcp nowait root /usr/sbin/tcpd in.rshd=0A=
login stream tcp nowait root /usr/sbin/tcpd in.rlogind=0A=
#exec stream tcp nowait root /usr/sbin/tcpd in.rexecd=0A=
#comsat dgram udp wait root /usr/sbin/tcpd in.comsat=0A=
talk dgram udp wait nobody.tty /usr/sbin/tcpd in.talkd=0A=
ntalk dgram udp wait nobody.tty /usr/sbin/tcpd in.ntalkd=0A=
#dtalk stream tcp wait nobody.tty /usr/sbin/tcpd in.dtalkd=0A=
#=0A=
# Pop and imap mail services et al=0A=
#=0A=
#pop-2 stream tcp nowait root /usr/sbin/tcpd ipop2d=0A=
#pop-3 stream tcp nowait root /usr/sbin/tcpd ipop3d=0A=
#imap stream tcp nowait root /usr/sbin/tcpd imapd=0A=
#=0A=
# The Internet UUCP service.=0A=
#=0A=
#uucp stream tcp nowait uucp /usr/sbin/tcpd /usr/lib/uucp/uucico -l=0A=
#=0A=
# Tftp service is provided primarily for booting. Most sites=0A=
# run this only on machines acting as "boot servers." Do not uncomment=0A=
# this unless you *need* it.=0A=
#=0A=
#tftp dgram udp wait root /usr/sbin/tcpd in.tftpd=0A=
#bootps dgram udp wait root /usr/sbin/tcpd bootpd=0A=
#=0A=
# Finger, systat and netstat give out user information which may be=0A=
# valuable to potential "system crackers." Many sites choose to disable=0A=
# some or all of these services to improve security.=0A=
#=0A=
finger stream tcp nowait nobody /usr/sbin/tcpd in.fingerd=0A=
#cfinger stream tcp nowait root /usr/sbin/tcpd in.cfingerd=0A=
#systat stream tcp nowait guest /usr/sbin/tcpd /bin/ps -auwwx=0A=
#netstat stream tcp nowait guest /usr/sbin/tcpd /bin/netstat -f inet=0A=
#=0A=
# Authentication=0A=
#=0A=
# identd is run standalone now=0A=
#=0A=
#auth stream tcp wait root /usr/sbin/in.identd in.identd -e -o=0A=
#=0A=
# End of inetd.conf=0A=
=0A=
linuxconf stream tcp wait root /bin/linuxconf linuxconf --http=0A=
------=_NextPart_000_0051_01C00D4A.3A8AF4A0
Content-Type: application/octet-stream;
name="hosts.allow"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="hosts.allow"
#=0A=
# hosts.allow This file describes the names of the hosts which are=0A=
# allowed to use the local INET services, as decided=0A=
# by the '/usr/sbin/tcpd' server.=0A=
#=0A=
ALL: LOCAL, 192.168.1.2, 192.168.1.1=0A=
------=_NextPart_000_0051_01C00D4A.3A8AF4A0
Content-Type: application/octet-stream;
name="hosts.deny"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="hosts.deny"
#=0A=
# hosts.deny This file describes the names of the hosts which are=0A=
# *not* allowed to use the local INET services, as decided=0A=
# by the '/usr/sbin/tcpd' server.=0A=
#=0A=
# The portmap line is redundant, but it is left to remind you that=0A=
# the new secure portmap uses hosts.deny and hosts.allow. In particular=0A=
# you should know that NFS uses portmap!=0A=
=0A=
=0A=
=0A=
=0A=
------=_NextPart_000_0051_01C00D4A.3A8AF4A0
Content-Type: application/octet-stream;
name="Secure.dat"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Secure.dat"
Aug 22 14:09:09 richspc login: LOGIN ON tty1 BY richard=0A=
Aug 22 14:09:14 richspc login: ROOT LOGIN ON tty2=0A=
Aug 22 14:09:26 richspc login: LOGIN ON tty3 BY guest=0A=
Aug 22 15:44:53 richspc login: ROOT LOGIN ON tty1=0A=
Aug 22 16:01:50 richspc login: LOGIN ON tty2 BY richard=0A=
Aug 22 16:05:36 richspc login: LOGIN ON tty2 BY richard=0A=
Aug 22 16:07:51 richspc login: LOGIN ON tty2 BY richard=0A=
Aug 22 16:10:16 richspc login: LOGIN ON tty1 BY richard=0A=
Aug 22 16:12:24 richspc login: ROOT LOGIN ON tty1=0A=
Aug 22 16:13:41 richspc login: LOGIN ON tty2 BY richard=0A=
Aug 22 16:20:06 richspc login: LOGIN ON tty1 BY richard=0A=
Aug 22 16:24:39 richspc login: ROOT LOGIN ON tty1=0A=
Aug 22 16:25:49 richspc login: LOGIN ON tty1 BY richard=0A=
Aug 22 16:30:12 richspc login: LOGIN ON tty1 BY richard=0A=
Aug 23 19:08:16 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:11:31 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:11:38 richspc in.ftpd[666]: connect from 127.0.0.1=0A=
Aug 23 19:11:38 richspc in.ftpd[666]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 19:21:17 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:23:06 richspc login: ROOT LOGIN ON tty2=0A=
Aug 23 19:28:13 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:32:04 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:48:21 richspc in.ftpd[668]: refused connect from 192.168.1.2=0A=
Aug 23 19:51:25 richspc in.ftpd[765]: warning: /etc/hosts.allow, line 7: =
missing ":" separator=0A=
Aug 23 19:51:25 richspc in.ftpd[765]: refused connect from 192.168.1.2=0A=
Aug 23 19:52:27 richspc in.ftpd[768]: warning: /etc/hosts.allow, line 5: =
missing newline or line too long=0A=
Aug 23 19:52:27 richspc in.ftpd[768]: refused connect from 192.168.1.2=0A=
Aug 23 19:54:41 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 19:54:48 richspc in.ftpd[665]: warning: /etc/hosts.allow, line 5: =
missing newline or line too long=0A=
Aug 23 19:54:48 richspc in.ftpd[665]: refused connect from 192.168.1.2=0A=
Aug 23 20:04:15 richspc in.ftpd[784]: connect from richspc=0A=
Aug 23 20:04:15 richspc in.ftpd[784]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 20:10:13 richspc in.ftpd[799]: connect from richspc=0A=
Aug 23 20:10:13 richspc in.ftpd[799]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 20:12:28 richspc in.ftpd[811]: connect from richspc=0A=
Aug 23 20:12:28 richspc in.ftpd[811]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 20:22:47 richspc in.ftpd[822]: connect from richspc=0A=
Aug 23 20:22:47 richspc in.ftpd[822]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 20:29:41 richspc in.ftpd[832]: warning: /etc/hosts.allow, line 7: =
missing ":" separator=0A=
Aug 23 20:29:41 richspc in.ftpd[832]: refused connect from 192.168.1.2=0A=
Aug 23 20:30:18 richspc in.ftpd[838]: warning: /etc/hosts.allow, line 7: =
missing ":" separator=0A=
Aug 23 20:30:18 richspc in.ftpd[838]: connect from 192.168.1.2=0A=
Aug 23 20:30:18 richspc in.ftpd[838]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
Aug 23 20:32:46 richspc login: ROOT LOGIN ON tty1=0A=
Aug 23 20:33:11 richspc in.ftpd[669]: connect from richspc=0A=
Aug 23 20:33:11 richspc in.ftpd[669]: error: cannot execute =
/usr/sbin/in.ftpd: No such file or directory=0A=
------=_NextPart_000_0051_01C00D4A.3A8AF4A0--