telnet + login to a DOC based system...

Hi…


I wonder, what configuration tree does the combination telnet + terminal

  • login uses? I have a problem when I telnet to a DiskOnChip based
    system. When I telnet to this particular system all seems to be ok, only
    I do not get the login prompt. It seems to me that there is some last
    something missing. I should point out that when I sit in front of
    this system, I do get the login prompt and all works fine. In other
    words, I can login into the system through the keyboard. However, I do
    not get the login prompt when I telnet to the board from another machine
    (I can however telnet to itself, to the same machine).

To be specific, I have /etc/passwd, /etc/hosts, /usr/sbin/inetd,
/etc/inetd.conf, /etc/services, /usr/local/terminfo, /etc/termcap,
io-net is working properly (I have /net working, I can telnet/ftp out of
the DOC). All seems to be there (inetd is up and running), but yet the
login section can not finish its transaction. This particular board is
an Adastra board which uses devn-pcnet. Any clues? As far as I know
devn-pcnet.so does not have a bug, correct?

I should say that if I put the very same DOC in a different system (an
Ampro pc104 which uses devn-smc9000.so), then all is fine. This
indicates to me that either:

a. devn-pcnet.so has a bug? Unlikely?
b. the adastra board has a curious hardware bug? Unlikely as well.
c. am I missing some configuration file, or some other miscellaneous
thing?? Seems more likely.

Any suggestion is appreciated. Thanks.

Best Regards…

Miguel.

my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.

Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

“Miguel Simon” <simon@ou.edu> wrote in message
news:3CB361B8.58CDEBE6@ou.edu

Hi…


I wonder, what configuration tree does the combination telnet + terminal

  • login uses? I have a problem when I telnet to a DiskOnChip based
    system. When I telnet to this particular system all seems to be ok, only
    I do not get the login prompt. It seems to me that there is some last
    something missing. I should point out that when I sit in front of
    this system, I do get the login prompt and all works fine. In other
    words, I can login into the system through the keyboard. However, I do
    not get the login prompt when I telnet to the board from another machine
    (I can however telnet to itself, to the same machine).

To be specific, I have /etc/passwd, /etc/hosts, /usr/sbin/inetd,
/etc/inetd.conf, /etc/services, /usr/local/terminfo, /etc/termcap,
io-net is working properly (I have /net working, I can telnet/ftp out of
the DOC). All seems to be there (inetd is up and running), but yet the
login section can not finish its transaction. This particular board is
an Adastra board which uses devn-pcnet. Any clues? As far as I know
devn-pcnet.so does not have a bug, correct?

Do you have devc-pty started? I think you should have /etc/profile
and /etc/protocols.


I should say that if I put the very same DOC in a different system (an
Ampro pc104 which uses devn-smc9000.so), then all is fine. This
indicates to me that either:

Well that seems to point at devn-pcnet then :wink:

a. devn-pcnet.so has a bug? Unlikely?
b. the adastra board has a curious hardware bug? Unlikely as well.
c. am I missing some configuration file, or some other miscellaneous
thing?? Seems more likely.

Any suggestion is appreciated. Thanks.

Best Regards…

Miguel.

my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.

Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Hi Mario…

Mario Charest wrote:

“Miguel Simon” <> simon@ou.edu> > wrote in message


To be specific, I have /etc/passwd, /etc/hosts, /usr/sbin/inetd,
/etc/inetd.conf, /etc/services, /usr/local/terminfo, /etc/termcap,
io-net is working properly (I have /net working, I can telnet/ftp out of
the DOC). All seems to be there (inetd is up and running), but yet the
login section can not finish its transaction. This particular board is
an Adastra board which uses devn-pcnet. Any clues? As far as I know
devn-pcnet.so does not have a bug, correct?

Do you have devc-pty started? I think you should have /etc/profile
and /etc/protocols.

Yes. devc-pty is going, and /etc/profile + /etc/prtocols are present.

I should say that if I put the very same DOC in a different system (an
Ampro pc104 which uses devn-smc9000.so), then all is fine. This
indicates to me that either:

Well that seems to point at devn-pcnet then > :wink:


a. devn-pcnet.so has a bug? Unlikely?

I tend to agree. However, I wonder what is the official word from
QSSL?? Does devn-pcnet have a bug?? What data would I need to collect
to see if this is the case?


Thaks Mario.

Regards…

Miguel.



\


my opinions are mine, only mine, solely mine, and they are not related
in any possible way to the institution(s) in which I study and work.

Miguel Simon
Research Engineer
School of Aerospace and Mechanical Engineering
University of Oklahoma
http://www.amerobotics.ou.edu/
http://www.saic.com

Miguel Simon <simon@ou.edu> wrote in news:3CB3D096.8FD974C3@ou.edu:

a. devn-pcnet.so has a bug? Unlikely?

I tend to agree. However, I wonder what is the official word from
QSSL?? Does devn-pcnet have a bug?? What data would I need to collect
to see if this is the case?

My first thought would be to eliminate the network card from the equation.
Run PPP over a serial port and see if you can telnet in that way. If all
works, you have likely narrowed it down to the driver.

More experiments would be to do a nicinfo/netstat on the target (since you
can sit at it), while telneting in. Are their errors reported by the NIC
card stats etc during this stalling phase? Perhaps try pinging a machine
from the target to see if this “eases” the stall, while tring to telnet
into it.


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>