[QNX2] ftp/ftpd, inetd.conf, Can I ftp INTO one of these systems?

QNX USERS QNX2 and QNX4
21

I can’t help but throw in a little related anecdote. A few years ago I was writing software for the post office. One day they had a problem in a local facility, a connection mysteriously kept being dropped. The system had a LAN and a WAN. The LAN had the usual 192.168.1.* addresses. It only dropped with the WAN was connected. A duplicate system used the same IP’s on it’s LAN. The post office person I worked with had spent quite a few hours trying to figure out what was wrong. He had gotten as far as finding out how to look at the ARP table. I was called in and I spent about 30 minutes looking at the problem. I then predicted that we would find a cable plugged into the wrong place, putting two LAN IP’s on the same network, which turned out to be the case.

The moral is, check your cable connections carefully.

22

How long ago did you do the Post Office work?

In the late 90s (96-00) I contracted for Siemens-ElectroCom which was building DBCS (Delivery Bar Code Sorters) machines for the USPS. Everything was done in QNX4 (GUI was in QNX4 windows). Just curious whether you were supporting those machines that were done in that time frame (or shortly after I left).

Tim

23

I sent you a message with some details. I believe I did a little bit of work on that system.

24

a few developments;

I did try to ftp into my q2 machine after receiving the new IP address, no change.

I have started making full system archives of the batches of floppy backups that my predecessor had been managing… one of the systems used an earlier revision of the TCP/IP package for the software we use (literally just a .1 version difference) BUT, this particular system apparently had passadmin configured in SOME capacity because I got an error from the backup command saying /config/password could not be copied, and sure enough the file seemed locked for access when I tried to view it…

I commented-out passadmin in one of the startup scripts and was able to open/copy the file after a restart… also, I realized the password file was in the /config/ directory, not /etc/, and I hadn’t tried putting it there when I was briefly playing with passadmin a couple weeks ago. This is the sys.opt.tcp file that gets called out in sys.init, I noticed it calls out a password.tcp file which I have never once encountered yet in these machines… I suppose that tracks because it looks like the script would automatically rename it, but also I hadn’t even noticed /config/password in any of these systems until this particular installation.

back
base 10

" This file used to be a bsys.opt.* file
" If one still exists, remove it
if +f /config/bsys.opt.tcp then
	rm /config/bsys.opt.tcp
endif

" Starting the Clearing House...
/cmds/clrhouse start p=30 > $null >* $null &
sleep 1

"Check for new password data file.
if +f /config/password.tcp then
	chattr /config/password a=-w > $null >* $null 
	rm /config/password > $null >* $null
	if +f /config/password then
		zap /config/password > $null >* $null
	endif
	mv /config/password.tcp /config/password > $null >* $null
	chattr /config/password a=+w > $null >* $null 
endif

" Starting Password Administrator...
/passadmin/passadmin +p l=4 > $null >* $null &
sleep 1

" Starting CI Dynamic Library Administrator...
/cmds/dyna > $null >* $null &
sleep 1

" Start the TCP/IP Protocol Driver...
/etc/cmds/emul.2000 -i IO_BASE:300 -I3 > $null >* $null &
sleep 1

" Starting the Network Daemon...
/etc/cmds/netd /etc/netconf > $null >* $null &
sleep 1

" Starting the InterNet 'Super-Server'...
/etc/cmds/inetd > $null >* $null &
sleep 5

" Starting the Routing Daemon...
/etc/cmds/routed -g > $null >* $null &
sleep 1

" Starting the Telnet Protocol Server...
/etc/cmds/telnetd > $null >* $null &
sleep 1

" Starting the Remove 'who' Server...
"/etc/cmds/rwhod > $null >* $null &
"sleep 1

" Starting the SNMP Daemon...
"/etc/cmds/snmpd > $null >* $null &
"sleep 1

" Hard-coded SMTP Daemon startup...   (Don't use if SMTP-triggered via INETD)
"if +f /usr/lib/sendmail then
"	cd /usr/spool/mqueue
"	rm [lnx]f* >* $null
"	/usr/lib/sendmail -bd -oL16 -v -q2m -C/usr/lib/sendmail.cf &
"	sleep 1
"	The '/das/sys/send_err' program is not available to 'sys.opt.*' scripts.
"	/das/sys/send_err 0 "Sendmail Daemon Started"
"endif

" Starting SLIP...
"/etc/cmds/slipd /dev/slip1 $mdm 9600 > $tty0 >* $tty0 &
"sleep 1

"icheck_reg err_adm
"if ne #? 00000 then
"	The '/das/sys/send_err' program is not available to 'sys.opt.*' scripts.
"	/das/sys/send_err 0 "TCP/IP Module Started"
"endif

" Flush the mail queue (if there is one...)
if +f /usr/spool/mqueue/df* then
	/usr/lib/sendmail -q > $null >* $null &
"	icheck_reg err_adm
"	if ne #? 00000 then
"		The '/das/sys/send_err' program is not available to 'sys.opt.*' scripts.
"		/das/sys/send_err 0 "SMTP Queue Processed"
"	endif
endif

" Start the TCP/IP emulator monitor.
if +f /das/sys/tcp_monitor then
	/das/sys/tcp_monitor &
endif


" Start the autonetd software if the files are there
if +f /das/sys/c86c_admin then
	/das/sys/c86c_admin &
	sleep 5
	if +f /das/sys/autonetd then
		/das/sys/autonetd &
	endif
endif

passadmin gets installed along with the TCP/IP package for this software, so I’m even more inclined to think it plays a role in any kind of remote or external access…

Also… I was actually approved for the Wireshark request, and am waiting for it to go through their workflow queue :o …so that’s neat.
[EDIT]: Wait, not confirmed as of yet… I apparently used the wrong software request pipeline, so I had to resubmit my request through a different process :roll_eyes: Dumb. We’ll see what happens…