inetd failure?

QNX Newsgroups (Archives) qdn.public.bsp
1

I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

2

Is devc-pty started? Also, is /bin/login present on your target?

Cheers,
-Brian

+================================================+
Brian K. Hlady bhlady@qnx.com
Technical Account Manager (613) 591 0836
QNX Software Systems, Ltd. extension 9268
+================================================+

“Richard Bonomo,6289 Chamberlin,263-4683,” <bonomo@sal.wisc.edu> wrote in
message news:b1ck48$jpf$1@inn.qnx.com…

I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

3

“Richard Bonomo,6289 Chamberlin,263-4683,” <bonomo@sal.wisc.edu> wrote in
message news:b1ck48$jpf$1@inn.qnx.com…

I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

Make sure you have files /etc/services and /etc/inetd.conf.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

4

/bin/login is present
/devc-pty was not started, so I am now starting it
(and the pertinent devices do appear) before starting
inetd. This has no effect so far (same error messages
and failure…)

Rich


Brian K. Hlady wrote:

Is devc-pty started? Also, is /bin/login present on your target?

Cheers,
-Brian

+================================================+
Brian K. Hlady > bhlady@qnx.com
Technical Account Manager (613) 591 0836
QNX Software Systems, Ltd. extension 9268
+================================================+

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

5

Is it possible for you to post your build file, and inetd.conf, please?

Cheers,
-Brian

“Richard Bonomo,6289 Chamberlin,263-4683,” <bonomo@sal.wisc.edu> wrote in
message news:b1e7n5$h72$1@inn.qnx.com…

/bin/login is present
/devc-pty was not started, so I am now starting it
(and the pertinent devices do appear) before starting
inetd. This has no effect so far (same error messages
and failure…)

Rich


Brian K. Hlady wrote:


Is devc-pty started? Also, is /bin/login present on your target?

Cheers,
-Brian

+================================================+
Brian K. Hlady > bhlady@qnx.com
Technical Account Manager (613) 591 0836
QNX Software Systems, Ltd. extension 9268
+================================================+

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

6

Brian K. Hlady wrote:

Is it possible for you to post your build file, and inetd.conf, please?

Cheers,
-Brian

Dear Brian,

OK, here is a bunch of stuff. Not everything (by a long
shot) is in the build file. More information is posted here
after the build file. Also, I am starting some things by hand
during the initial set up and testing phase (see the sin output
at the end…)

Thanks!

Rich

First the base build file:

###########################################################################

Neutrino on an PC BIOS compatible system

This is for building a bootable neutrino image that will run from its

own filesystem partition on M-Systems DiskOnChip.

Note that the default image links at 4M. If you have 4M or less,

uncomment the line below

[image=1m]

###########################################################################

[virtual=x86,bios +compress] boot = {
startup-bios -Nst5ka
PATH=/proc/boot:/bin
:/sbin LD_LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll procnto
}

[+script] startup-script = {

Start up some consoles

devc-con -n 1 &
reopen /dev/con1
display_msg “”
display_msg Welcome to Neutrino on the ST5000

Disk drivers (The default one and some fun others for your pleasure…)

display_msg Start the DiskOnChip driver
devb-doc doc addr=0xe8000 blk automount=hd0t77:/

Wait for a bin for the rest of the commands (up to 30 secs)

waitfor /bin 30

Some common servers

display_msg Start common servers
pipe &
mqueue &
devc-ser8250 -b 38400 -e -f &
waitfor /dev/ser1 30

These env variables inherited by all the programs which follow

SYSNAME=nto
HOME=/
TERM=qansi
PATH=/proc/boot:/bin:/sbin:/usr/bin:/home/jwp
LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll
LD_LIBRARY_PATH=/proc/boot:/dev/shmem:/lib:/lib/dll
TCL_LIBRARY=/home/jwp/
tcl_library=/home/jwp/

Start the network -rlb

display_msg Start the network
io-net -d ne2000 -p qnet -p ttcpip if=en0:144.92.179.68:255.255.255.0 &

Start tinit

display_msg Start tinit
/sbin/tinit TCL_LIBRARY=/home/jwp/ tcl_library=/home/jwp/

Start the main shell

display_msg Start the main shell
reopen /dev/con1
[+session] sh

[+session] login -p

}

Cheat and make the /temp point to the shared memory area…

[type=link] /tmp=/dev/shmem

Redirect console messages for syslog

[type=link] /dev/console=/dev/con1

Programs require the runtime linker (ldqnx.so) to be at a fixed location

[type=link] /usr/lib/ldqnx.so.2=/proc/boot/libc.so

We use the “c” shared lib (which also contains the runtime linker)

libc.so

Include the socket library

libsocket.so

Include the hard disk files so we can access files on the disk

libcam.so
io-blk.so

filesystem required shared libs

cam-disk.so
fs-qnx4.so

The files above this line can be shared by mutiple processes

Executables must currently be below this line

[data=copy]

Include DiskOnChip driver.

…/doc.6.2/devb-doc

Include a console driver

devc-con

/etc/config/ttys {
ser2 “/bin/sh” ansi on
}

listing of selected directories and files on target

bin
dev
etc
lib
net
proc
sbin
usr

directory bin

cat
chgrp
chmod
chown
cp
dd
df
du
echo
false
hostname
kill
ln
login
logout
ls
mkdir
more
mount
mv
ps
pwd
rm
sh
shutdown
sin
slay
stty
true
umount

directory dev

con1
hd0
hd0t77
io-net
kbd
mem
netmgr
null
pipe
ptyp0
ptyp1
ptyp2
ptyp3
ptyp4
ptyp5
ptyp6
ptyp7
ser1
ser2
shmem
socket
text
tty
ttyp0
ttyp1
ttyp2
ttyp3
ttyp4
ttyp5
ttyp6
ttyp7
zero

directory etc

config
inetd.conf
services

directory lib

dll
libc.a
libc.so
libc.so.1
libc.so.2
libcS.a
libcam.so
libcam.so.1
libcam.so.2
libcpp.a
libcpp.so
libcpp.so.2
libcpp.so.2a
libcppS.a
libm.so
libm.so.2
libsocket.so
libsocket.so.2

directroy lib/dll

devn-ne2000.so
npm-qnet.so
npm-tcpip-v4.so
npm-tcpip-v6.so
npm-tcpip.so
npm-ttcpip.so

directory proc

1
10
12300
2
3
4
5
6
7
8
8203
9
boot
ipstats
qnetstats

directory sbin

devc-pty
devc-ser8250
ifconfig
io-net
mqueue
pipe
tinit

directory usr

bin
lib
sbin
bin
lib
sbin

directory usr/sbin

ftpd
inetd
telnetd

output of sin


procnto 1 0 0 0 0 4331226
devc-con 2 44K 56K 4K 516K 568
devb-doc 3 128K 5253K 32K 608K 12968
pipe 4 16K 52K 20K 912K 75
mqueue 5 12K 36K 4K 516K 67
devc-ser8250 6 28K 56K 4K 516K 81
io-net 7 56K 460K 48K 1581K 23872
tinit 8 8K 36K 8K 516K 73
sh 9 148K 72K 8K 516K 158
sh 10 148K 72K 4K 516K 81
devc-pty 8203 28K 68K 4K 516K 88
inetd 12300 36K 68K 8K 516K 121
sin 53261 84K 44K 8K 516K 92

7

Brian K. Hlady wrote:

Is it possible for you to post your build file, and inetd.conf, please?

Cheers,
-Brian

Here is the inetd.conf file. It is the vanilla one copied from the host…

@(#)inetd.conf 1.23 90/01/03 SMI

Configuration file for inetd.

To re-configure the running inetd process, edit this file, then

send the inetd process a SIGHUP.

Internet services syntax:

<service_name> <socket_type> <server_pathname>

# # Time service is used for clock syncronization. # #time stream tcp nowait root internal #time dgram udp wait root internal

Ftp and telnet are standard Internet services.

ftp stream tcp nowait root /usr/sbin/ftpd in.ftpd -l
telnet stream tcp nowait root /usr/sbin/telnetd in.telnetd

Shell, login, exec are BSD protocols.

#shell stream tcp nowait root /usr/sbin/rshd in.rshd
#login stream tcp nowait root /usr/sbin/rlogind in.rlogind
#exec stream tcp nowait root /usr/sbin/rexecd in.rexecd

Tftp service is provided primarily for booting. Most sites run this

only on machines acting as “boot servers”.

#tftp dgram udp wait root /usr/sbin/tftpd in.tftpd

Systat and netstat give out user information which man be

valuable to potential “system crackers.” Many sites choose to disable

some or all of these services to improve security.

#systat stream tcp nowait root /bin/ps ps -auwwx
#netstat stream tcp nowait root /usr/bin/netstat netstat -f inet

IPv6 services.

The only difference with the above is “tcp6” instead of “tcp”.

Be sure to enable both “tcp” and “tcp6” when you need service for

both IPv4/v6.

#ftp stream tcp6 nowait root /usr/sbin/ftpd ftpd
-ll
telnet stream tcp6 nowait root /usr/sbin/telnetd telnetd
#shell stream tcp6 nowait root /usr/sbin/rshd rshd -L
#login stream tcp6 nowait root /usr/sbin/rlogind rlogind
-L
#tftp dgram udp6 wait root /usr/sbin/tftpd tftpd
-l -s /tftpboot

\

Neutrino specific services

#pidin stream tcp nowait root /bin/pidin pidin
#pidinmem stream tcp nowait root /bin/pidin pidin mem
#pidinarg stream tcp nowait root /bin/pidin pidin arg
#pidinenv stream tcp nowait root /bin/pidin pidin env
#pidinsig stream tcp nowait root /bin/pidin pidin sig
#phrelay stream tcp nowait root /usr/bin/phrelay phrelay -x

Echo, discard, daytime, and chargen are used primarily for testing.

#echo stream tcp nowait root internal
#echo dgram udp wait root internal
discard stream tcp nowait root internal
discard dgram udp wait root internal
#daytime stream tcp nowait root internal
#daytime dgram udp wait root internal
#chargen stream tcp nowait root internal
#chargen dgram udp wait root internal

8

Mario Charest wrote:

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.

Those are both present.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

9

Richard Bonomo,6289 Chamberlin,263-4683, <bonomo@sal.wisc.edu> wrote in
message news:b1eccp$li7$3@inn.qnx.com…

Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

10

Xiaodan Tang wrote:

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

11

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt, but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <bonomo@sal.wisc.edu> wrote in
message news:b1ej09$t01$1@inn.qnx.com…

Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

12

Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt, but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang

telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

13

Good, then it’s not problems of telnetd or config file. But some how inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different position of
the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <bonomo@sal.wisc.edu> wrote in
message news:b1esh2$9jq$1@inn.qnx.com…

Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

14

If that is the problem, why does telnetd -debug not work when it uses
the default port?

I have already posted configuration information in my last responses
to Brian Hlady on this newsgroup (you should be able to see them). I’ll
see if I can capture the output of inted -d and post it
on this sub-thread.

Thanks!

Rich

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different position
of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

15

It is NOT working with default port, BUT WORKING with port like “3000” ?

Hm, are you starting it as root ? Did you kill inetd (and probably do a
netstat -na)
to make sure no one is listening on port 23 before you do a “telnetd -debug
23” ?

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <bonomo@sal.wisc.edu> wrote in
message news:b1mnlv$156$1@inn.qnx.com…

If that is the problem, why does telnetd -debug not work when it uses
the default port?

I have already posted configuration information in my last responses
to Brian Hlady on this newsgroup (you should be able to see them). I’ll
see if I can capture the output of inted -d and post it
on this sub-thread.

Thanks!

Rich

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how
inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different position
of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or
some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu
wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,”
bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and
ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd.
This
did not change anything…

Rich B.

16

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different position
of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

2nd followup:

I was not able to capture the output of inetd -d, so here is
a transcription of what the relevant lines appear to be:

*** partial quote from inetd -d output, and error messages by telnet client:
<first, inetd output>
ADD : telnet proto=tcp wait:max=0.40, user:group=root, builtin=0
server=/usr/sbin/telnetd policy=

<another line, almost identical, for tcp6>

FREE: telnet proto=tcp6, wait:max=0.40, user:group=root, builtin=0
server=/usr/sbin/telnetd policy=

<when I tried to telnet in from another QNX6 host, inetd produced this:>
someone wants telnet
accept, ctrl 3
36076 reaped, status 0x100
<on the host running the telnet client, this appears>
Trying
Connected to
Connection closed by foreign host.
************ end of transcriptions

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.

17

Xiaodan Tang wrote:

It is NOT working with default port, BUT WORKING with port like “3000” ?

Hm, are you starting it as root ? Did you kill inetd (and probably do a
netstat -na)
to make sure no one is listening on port 23 before you do a “telnetd
-debug 23” ?

Well, it DID work once, with port 3000, when you had me try it last
week. Now it fails for either port 3000 or 23 with either “connection
refused” or “all network ports are in use” if I run telnetd -debug
directly.

The system boots with no network servers (inted, telnetd, ftpd, etc.)
running. “sin” verifies this. If I run netstat, I get a “no namelist”
error. This is probably because we are running ttcpip. (I did try the
full stack, and got the same errors with ftp, telnet, and inetd.)

Rich

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1mnlv$156$> 1@inn.qnx.com> …
If that is the problem, why does telnetd -debug not work when it uses
the default port?

I have already posted configuration information in my last responses
to Brian Hlady on this newsgroup (you should be able to see them). I’ll
see if I can capture the output of inted -d and post it
on this sub-thread.

Thanks!

Rich

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how
inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different
position of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or
some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to
prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu
wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,”
bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and
ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd.
This
did not change anything…

Rich B.

18

Oops! Sorry! telnet is working in debug mode with the default
port. The devc-pty driver had not been restarted after a reboot.
It does not work via inetd, though…

Xiaodan Tang wrote:

It is NOT working with default port, BUT WORKING with port like “3000” ?

Hm, are you starting it as root ? Did you kill inetd (and probably do a
netstat -na)
to make sure no one is listening on port 23 before you do a “telnetd
-debug 23” ?

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1mnlv$156$> 1@inn.qnx.com> …
If that is the problem, why does telnetd -debug not work when it uses
the default port?

I have already posted configuration information in my last responses
to Brian Hlady on this newsgroup (you should be able to see them). I’ll
see if I can capture the output of inted -d and post it
on this sub-thread.

Thanks!

Rich

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how
inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different
position of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or
some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to
prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu
wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:


“Richard Bonomo,6289 Chamberlin,263-4683,”
bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and
ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd.
This
did not change anything…

Rich B.

19

VICTORY!!

It seems much of the problem may have arisen from the
/etc directory not being a conventional dirctory. When
I first tried this, I had to copy the /etc directory and
so some moving and renaming before I could copy configuration
files into it. The ls command shed no light, but apparently
since this directory was initially created by a “link” directive
in the image, it could not be manipulated as a regular directory.
So, instead, I added additional link commands to the build file.
I also had the password and shadow files copied over instead
of creating them specially on the target, along with the /etc/ftpusers
files. These things did the trick.

Perhaps some warning should be put in the documentation about directories
created as a byproduct of “link” directives…

Thanks for your initial responses to me.

Rich

Brian K. Hlady wrote:

Is it possible for you to post your build file, and inetd.conf, please?

Cheers,
-Brian

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote in
message news:b1e7n5$h72$> 1@inn.qnx.com> …
/bin/login is present
/devc-pty was not started, so I am now starting it
(and the pertinent devices do appear) before starting
inetd. This has no effect so far (same error messages
and failure…)

Rich


Brian K. Hlady wrote:


Is devc-pty started? Also, is /bin/login present on your target?

Cheers,
-Brian

+================================================+
Brian K. Hlady > bhlady@qnx.com
Technical Account Manager (613) 591 0836
QNX Software Systems, Ltd. extension 9268
+================================================+

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu> > wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly established.

If I fire up inetd on host system and connect from the target,
things are just fine. The one difference I have noted is that
inetd -d on the host system has a line indicating "excle "
(I hope I spelled that correctly), whereas the target’s
inetd -d output does not generate that particular line when login
attempts were made. I tried brining over the libc.so library
to see if that would take care of it, but no go.

It seems I must be missing SOMETHING, but I have not been able
to figure out what this is from the documentation nor from the
error messages (there aren’t any).

Any ideas?

Richard B.

20

Xiaodan Tang wrote:

Good, then it’s not problems of telnetd or config file. But some how inetd
can’t spawn the telnetd.
Only thing I can think of is the /etc/inetd.conf have different position
of the binary. (Like it is trying
to spawn /sbin/telnetd, but you have telnetd in /usr/sbin/telnetd or some
thing like that…)

It would be helpful to see your /etc/inetd.conf file, and the inetd -d
output (from the time you start
it), and the failure message from telnet.

-xtang

Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1esh2$9jq$> 1@inn.qnx.com> …
Xiaodan Tang wrote:

Quick test. (for telnetd).

On your target, run “telnetd -debug 3000” (it won’t return to prompt,
but
it’s ok).
From another host, “telnet <target_ip> 3000”.

Does the telnet works ? If it is not, does it say anything ?

-xtang


telnet works in this mode; no “debugging” output shows up on the
host or the target.

Rich


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote in
message news:b1ej09$t01$> 1@inn.qnx.com> …
Xiaodan Tang wrote:


Richard Bonomo,6289 Chamberlin,263-4683, <> bonomo@sal.wisc.edu> > wrote
in
message news:b1eccp$li7$> 3@inn.qnx.com> …
Mario Charest wrote:
VICTORY

see the note I posted to the other sub-thread…
Rich

“Richard Bonomo,6289 Chamberlin,263-4683,” <> bonomo@sal.wisc.edu
wrote
in
message news:b1ck48$jpf$> 1@inn.qnx.com> …
I recently determined that it would be wise to be able to
connected to a target system I am setting up via telnet and ftp.
(I don’t think that ssh is available yet…)

I put inetd, inetd.conf, ftpd, and telnetd on the target
system, and inetd starts up without errors (inetd -d output
seems OK), but so far every attempt to connect has failed.
The connection is closed as soon as it is supposedly
established.


Make sure you have files /etc/services and /etc/inetd.conf.



Those are both present.

You also /etc/protocols depends on what service program running.

-xtang

I copies /etc/protocols over from the host, and restarted inetd. This
did not change anything…

Rich B.