My predecessor started a couple threads about QNX2 network related stuff in the past, but I’ve since dug deeper and figured out more about these systems than those before me, so I’m here with my own questions… (my post got larger than I intended, so I am sticking to one subject and will eventually ask some of my other questions in a separate thread)
Let me preface this by saying
- I am not certain who made the networking stack/software/whatev but there is a file
snmpconf
that readsSpiderTCP TCP/IP (release 5.1) for QNX version 2.15, 1.3.6.1.4.1.24.4.1.1.4
Note, our systems are QNX 2.21 - It seems fairly robust, and appears to have parallels to unix/linux style network components and configuration files (unless QNX actually came like this by default, of which I am unaware), but sadly I am not intuitively familiar with other *nix environments
- NIC is just a LinkSys Ether16 base 10 ISA card
- I do not suspect hardware failure anywhere along the network nor do I believe there is any filtering or blocked ports/services within the scope of what I am trying to do
Primarily, I am trying to determine if I might be able to ftp INTO one of these machines.
These systems have had the capacity to connect to OTHER systems via ftp for ages; we have a server on our network to which we routinely push data through the main software that we use, as well as a command line (or shell, i suppose?) text-based ftp program for general file transfer.
I’ve spent a decent amount of time online reading about how to configure the different files to enable/configure different components, but all of the stuff I have seen has been for QNX 4 or straight up Unix and Linux, so I don’t know quite how much of that is mirrored on these systems.
Here is a list of files in /etc/
and /etc/cmds/
According to @Tim in this post, ftpd should be loaded when there’s an incoming ftp request/attempt, and so should telnetd if someone has telnetted into a system.
I am certainly able to telnet into the system, and telnetd is definitely running when I check the tsk command.
If I open inetd.conf
, this is its contents:
#
# INETD.CONF :: Inetd configuration file
#
#
ftp stream tcp nowait autonet /etc/cmds/ftpd ftpd
echo stream tcp nowait autonet internal internal
discard stream tcp nowait autonet internal internal
daytime stream tcp nowait autonet internal internal
chargen stream tcp nowait autonet internal internal
time stream tcp nowait autonet internal internal
smtp stream tcp nowait autonet /usr/lib/sendmail sendmail -bc
rshd stream tcp nowait autonet /etc/cmds/rshd rshd -bc
finger stream tcp nowait autonet /etc/cmds/fingerd fingerd -b
As I understand it, this file dictates how incoming network requests are handled… my untrained eye would say it looks as though it might expect to receive incoming ftp requests
But for whatever reason, if I try to ftp INTO one of these systems, it either just doesn’t connect, or QNX supposedly refuses the connection. (the refusal comes on port 20 where as the completely failed connection is on port 21)
One of the pages I found online outlines this file, but in a GNU system
But more importantly, this page from c. 2005 outlines the BSD version and talks about password and user files and a lot of extra components that I haven’t yet seen on one of these QNX machines;
https://web.archive.org/web/20200809112713/https://netbsd.gw.com/cgi-bin/man-cgi?ftpd++NetBSD-4.0
now, again, I understand that these things will most certainly not be one-to-one with the QNX systems I’m dealing with, but it makes me wonder if this could actually work if I were to make those extra configuration files.
I mean, it looks like these systems at least have the foundation for incoming ftp access…
I’ve just sorta hit a wall and I’m not sure where to go from here, and I don’t know whether this is a pointless effort in the first place.
does anyone have any insight or perhaps a direction to point me in?