Remote access via modem setup

I’m trying to setup remote access via modem. I have an external modem
attached to /dev/ser1 (com1) to which qtalk can communicate nicely. I can
even dial into qtalk and transfer keystrokes to/from another machine.
“modem”, however, runs for about 30s before quietly stopping. I’ve tried
several variants of the modem command, inside and out of “tinit” in the
sysinit.1 file. The last attempt looked like this:

modem -b57600 -D - </dev/ser1 >/dev/ser1

This redirected command-line version was suggested in the docs as a good
test for a one-shot dial-up. I’ve tried using -b28800, -b19200, -b9600 as
well.

Notably: the modem program doesn’t appear to emit the ATZ initialization
command. One would think that the -D - option would display this. Neither
does there appear to be any activity on the tx/rx LEDs on the modem,
although “ATZ” at 57600 doesn’t take a lot of time. The modem does answer
calls. This could be its default behavior.

Are there any other initialization commands I need (stty)? If not, are there
any other diagnostics that might shed some light?

TIA,

Harry Qualls,
Tree-D, Inc.

I can’t honestly tell you how anything works in the ways of modems and qnx, but
I know that this is how I setup my computer and it seems to work fine. The modem
is an internal one setup for /dev/ser3

tinit -T /dev/con* -t /dev/con1 -c “modem -b 115200 -L” -t /dev/ser3 &

hope it helps.


Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.

try using on -t /dev/ser1 or tinit.
you want modem to be running on the device in use.

here’s what we do here:

in the sysinit we have:

/bin/tinit -f /etc/config/tinit.1.mdm &

and the /etc/config/tinit.1.mdm file contains…

-m 45
-c “/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t mdm1
-c “/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t mdm2

our ser ports are labelled /dev/mdm[1-8]

you can run login in place of our -c option.

make sure as well that your ser port and modem is setup okay with DTR
notification etc… the docs on the modem utility go into good detail on
this.

as a last resort, the src to modem is posted in our free software section.
it can help you debug and see how far you are getting.


Harry Qualls <hfq@tree-d.com> wrote:

I’m trying to setup remote access via modem. I have an external modem
attached to /dev/ser1 (com1) to which qtalk can communicate nicely. I can
even dial into qtalk and transfer keystrokes to/from another machine.
“modem”, however, runs for about 30s before quietly stopping. I’ve tried
several variants of the modem command, inside and out of “tinit” in the
sysinit.1 file. The last attempt looked like this:

modem -b57600 -D - </dev/ser1 >/dev/ser1

This redirected command-line version was suggested in the docs as a good
test for a one-shot dial-up. I’ve tried using -b28800, -b19200, -b9600 as
well.

Notably: the modem program doesn’t appear to emit the ATZ initialization
command. One would think that the -D - option would display this. Neither
does there appear to be any activity on the tx/rx LEDs on the modem,
although “ATZ” at 57600 doesn’t take a lot of time. The modem does answer
calls. This could be its default behavior.

Are there any other initialization commands I need (stty)? If not, are there
any other diagnostics that might shed some light?

TIA,

Harry Qualls,
Tree-D, Inc.


Randy Martin randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579

Remote logins are now working. Trying:

tinit -c “modem -b57600 -L” -t /dev/ser1 -t /dev/con1 -T /dev/con[2-6] &

did not work. This variant never displays a login prompt on /dev/con1.
Trying:

tinit -t /dev/con1 -T /dev/con[2-6] -c “modem -b57600 -L” -t /dev/ser1 &

did work. So did the above without the -L option to modem.

Thanks for the suggestions.

“Chris Nasr” <cnasr@mechtronix.ca> wrote in message
news:3AEF1C9A.47AA0D@mechtronix.ca

I can’t honestly tell you how anything works in the ways of modems and
qnx, but
I know that this is how I setup my computer and it seems to work fine. The
modem
is an internal one setup for /dev/ser3

tinit -T /dev/con* -t /dev/con1 -c “modem -b 115200 -L” -t /dev/ser3 &

hope it helps.


Chris Nasr
cnasr[at]mechtronix[dot]ca
Mechtronix Systems Inc.

Harry Qualls wrote:

Remote logins are now working. Trying:

tinit -c “modem -b57600 -L” -t /dev/ser1 -t /dev/con1 -T /dev/con[2-6] &

did not work. This variant never displays a login prompt on /dev/con1.

There is an explanation:
The -c option applies to all subsequent devices.
So “modem” will be executed on /dev/con1 in stead of the default
login.
By moving the -c to just before the /dev/ser1 you restored the
default “login” to be executed on /dev/con1.

Trying:

tinit -t /dev/con1 -T /dev/con[2-6] -c “modem -b57600 -L” -t /dev/ser1 &

did work. So did the above without the -L option to modem.

Thanks for the tips. We’ve got a login via a modem. Now I want to go one
step further. The system we would be logging into runs Photon 1.14. The
default sysinit file created during QNX installation qualifies the Photon
startup with a test for ph.node. Since this file exists the tinit command in
the else portion of the test doesn’t execute. Thus no -c “modem” etc adn
thus no remoe login.

I moved a modified version of the tinit command containing only the modem
portion of the startup immediately above the /etc/config/bin/ph.$NODE
statement. I can again log in remotely. I cannot, however, ever get a Photon
session. Typing “exec /qnx4/photon/bin/phrelay” disconnects me and sometimes
the text “Could not” remains. I presume phrelay requires Photon shared libs
which are not available since Photon is not running (on this session).
Photon is booted and waiting for a login on the remote machine.

What I’d ultimately want to accomplish is to be able to remotely control the
target machine Photon to Photon AND to be able to tranfer files. Does anyone
know the correct setup?

“Randy Martin” <randy@qnx.com> wrote in message
news:9cn6br$bf$1@nntp.qnx.com

try using on -t /dev/ser1 or tinit.
you want modem to be running on the device in use.

here’s what we do here:

in the sysinit we have:

/bin/tinit -f /etc/config/tinit.1.mdm &

and the /etc/config/tinit.1.mdm file contains…

-m 45
-c “/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm1
-c “/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm2

our ser ports are labelled /dev/mdm[1-8]

you can run login in place of our -c option.

make sure as well that your ser port and modem is setup okay with DTR
notification etc… the docs on the modem utility go into good detail on
this.

as a last resort, the src to modem is posted in our free software section.
it can help you debug and see how far you are getting.


Harry Qualls <> hfq@tree-d.com> > wrote:
I’m trying to setup remote access via modem. I have an external modem
attached to /dev/ser1 (com1) to which qtalk can communicate nicely. I
can
even dial into qtalk and transfer keystrokes to/from another machine.
“modem”, however, runs for about 30s before quietly stopping. I’ve tried
several variants of the modem command, inside and out of “tinit” in the
sysinit.1 file. The last attempt looked like this:

modem -b57600 -D - </dev/ser1 >/dev/ser1

This redirected command-line version was suggested in the docs as a good
test for a one-shot dial-up. I’ve tried using -b28800, -b19200, -b9600
as
well.

Notably: the modem program doesn’t appear to emit the ATZ initialization
command. One would think that the -D - option would display this.
Neither
does there appear to be any activity on the tx/rx LEDs on the modem,
although “ATZ” at 57600 doesn’t take a lot of time. The modem does
answer
calls. This could be its default behavior.

Are there any other initialization commands I need (stty)? If not, are
there
any other diagnostics that might shed some light?

TIA,

Harry Qualls,
Tree-D, Inc.



\

Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579

Are you calling from another QNX machine or from a Microsoft machine?
We call into our QNX systems from Microsoft systems and the tinit line
starts modem, which in turn starts pppd. Then in ‘/etc/services’ we have
the
entry for Photon ‘phrelay 4868/tcp’. So when we run Phindows pppd kicks
of phrelay. Does this help or raise more questions?

Harry Qualls <hfq@tree-d.com> wrote in message
news:9cpgj8$lig$1@inn.qnx.com

Thanks for the tips. We’ve got a login via a modem. Now I want to go one
step further. The system we would be logging into runs Photon 1.14. The
default sysinit file created during QNX installation qualifies the Photon
startup with a test for ph.node. Since this file exists the tinit command
in
the else portion of the test doesn’t execute. Thus no -c “modem” etc adn
thus no remoe login.

I moved a modified version of the tinit command containing only the modem
portion of the startup immediately above the /etc/config/bin/ph.$NODE
statement. I can again log in remotely. I cannot, however, ever get a
Photon
session. Typing “exec /qnx4/photon/bin/phrelay” disconnects me and
sometimes
the text “Could not” remains. I presume phrelay requires Photon shared
libs
which are not available since Photon is not running (on this session).
Photon is booted and waiting for a login on the remote machine.

What I’d ultimately want to accomplish is to be able to remotely control
the
target machine Photon to Photon AND to be able to tranfer files. Does
anyone
know the correct setup?

“Randy Martin” <> randy@qnx.com> > wrote in message
news:9cn6br$bf$> 1@nntp.qnx.com> …
try using on -t /dev/ser1 or tinit.
you want modem to be running on the device in use.

here’s what we do here:

in the sysinit we have:

/bin/tinit -f /etc/config/tinit.1.mdm &

and the /etc/config/tinit.1.mdm file contains…

-m 45
-c
“/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm1
-c
“/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm2

our ser ports are labelled /dev/mdm[1-8]

you can run login in place of our -c option.

make sure as well that your ser port and modem is setup okay with DTR
notification etc… the docs on the modem utility go into good detail on
this.

as a last resort, the src to modem is posted in our free software
section.
it can help you debug and see how far you are getting.


Harry Qualls <> hfq@tree-d.com> > wrote:
I’m trying to setup remote access via modem. I have an external modem
attached to /dev/ser1 (com1) to which qtalk can communicate nicely. I
can
even dial into qtalk and transfer keystrokes to/from another machine.
“modem”, however, runs for about 30s before quietly stopping. I’ve
tried
several variants of the modem command, inside and out of “tinit” in
the
sysinit.1 file. The last attempt looked like this:

modem -b57600 -D - </dev/ser1 >/dev/ser1

This redirected command-line version was suggested in the docs as a
good
test for a one-shot dial-up. I’ve tried using -b28800, -b19200, -b9600
as
well.

Notably: the modem program doesn’t appear to emit the ATZ
initialization
command. One would think that the -D - option would display this.
Neither
does there appear to be any activity on the tx/rx LEDs on the modem,
although “ATZ” at 57600 doesn’t take a lot of time. The modem does
answer
calls. This could be its default behavior.

Are there any other initialization commands I need (stty)? If not, are
there
any other diagnostics that might shed some light?

TIA,

Harry Qualls,
Tree-D, Inc.



\

Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579

Thanks for the reply.

We intended to communicate QNX/Photon to QNX/Photon over a dail-up line. We
wanted to accomplish two things: remotely participate in the existing QNX
network (as node 12 in an 11-node network with 12 licenses); and remotely
monitor another node with phditto. Since my original post we have determined
the following:

We can dial into a QNX host using a modem command that initiates Net.fd. The
host kicks off a predefined .profile script for a dial-in only user as
suggested by a post in the QNX KB. This script starts Net.fd on the host and
voila we have a network (albeit serial) connection! There are some quirks,
for example, the alive command fails to see any other nodes. Basic network
functions between the remote (node 12) and host (node 1) function correctly.
The network does not “bridge” to the other 10 nodes. There is some
discussion as to whether it should (see Net.fd posts in this group). So one
doesn’t get full network functionality with the configuration we’ve defined.
The performance between the two serially connected nodes was close to the
stated modem connection speeds which made file transfers and remote file
editing possible.

As for phditto-ing from node 1 to node12 - forget it. The performance was
unacceptable at our connection speed (26400) and we’ve been told it’s also
unacceptable at 115200.

Credit is certainly due to QNX for the fact that the serial network
connection works as well as it does: a minor triumph of modularity. The
documentation about what it takes to make it happen could be better (like
some example setups).

Anyone interested in how we got this to work should feel free to email me.

“Ivan Bannon” <ivan.bannon@rjginc.com> wrote in message
news:9dubf1$hh8$1@inn.qnx.com

Are you calling from another QNX machine or from a Microsoft machine?
We call into our QNX systems from Microsoft systems and the tinit line
starts modem, which in turn starts pppd. Then in ‘/etc/services’ we have
the
entry for Photon ‘phrelay 4868/tcp’. So when we run Phindows pppd kicks
of phrelay. Does this help or raise more questions?

Harry Qualls <> hfq@tree-d.com> > wrote in message
news:9cpgj8$lig$> 1@inn.qnx.com> …
Thanks for the tips. We’ve got a login via a modem. Now I want to go one
step further. The system we would be logging into runs Photon 1.14. The
default sysinit file created during QNX installation qualifies the
Photon
startup with a test for ph.node. Since this file exists the tinit
command
in
the else portion of the test doesn’t execute. Thus no -c “modem” etc adn
thus no remoe login.

I moved a modified version of the tinit command containing only the
modem
portion of the startup immediately above the /etc/config/bin/ph.$NODE
statement. I can again log in remotely. I cannot, however, ever get a
Photon
session. Typing “exec /qnx4/photon/bin/phrelay” disconnects me and
sometimes
the text “Could not” remains. I presume phrelay requires Photon shared
libs
which are not available since Photon is not running (on this session).
Photon is booted and waiting for a login on the remote machine.

What I’d ultimately want to accomplish is to be able to remotely control
the
target machine Photon to Photon AND to be able to tranfer files. Does
anyone
know the correct setup?

“Randy Martin” <> randy@qnx.com> > wrote in message
news:9cn6br$bf$> 1@nntp.qnx.com> …
try using on -t /dev/ser1 or tinit.
you want modem to be running on the device in use.

here’s what we do here:

in the sysinit we have:

/bin/tinit -f /etc/config/tinit.1.mdm &

and the /etc/config/tinit.1.mdm file contains…

-m 45
-c
“/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm1
-c
“/bin/modem -c/usr/local/bin/quics_start -D/dev/tty10 -Lb57600 -s1” -t
mdm2

our ser ports are labelled /dev/mdm[1-8]

you can run login in place of our -c option.

make sure as well that your ser port and modem is setup okay with DTR
notification etc… the docs on the modem utility go into good detail
on
this.

as a last resort, the src to modem is posted in our free software
section.
it can help you debug and see how far you are getting.


Harry Qualls <> hfq@tree-d.com> > wrote:
I’m trying to setup remote access via modem. I have an external
modem
attached to /dev/ser1 (com1) to which qtalk can communicate nicely.
I
can
even dial into qtalk and transfer keystrokes to/from another
machine.
“modem”, however, runs for about 30s before quietly stopping. I’ve
tried
several variants of the modem command, inside and out of “tinit” in
the
sysinit.1 file. The last attempt looked like this:

modem -b57600 -D - </dev/ser1 >/dev/ser1

This redirected command-line version was suggested in the docs as a
good
test for a one-shot dial-up. I’ve tried
using -b28800, -b19200, -b9600
as
well.

Notably: the modem program doesn’t appear to emit the ATZ
initialization
command. One would think that the -D - option would display this.
Neither
does there appear to be any activity on the tx/rx LEDs on the modem,
although “ATZ” at 57600 doesn’t take a lot of time. The modem does
answer
calls. This could be its default behavior.

Are there any other initialization commands I need (stty)? If not,
are
there
any other diagnostics that might shed some light?

TIA,

Harry Qualls,
Tree-D, Inc.



\

Randy Martin > randy@qnx.com
Manager of FAE Group, North America
QNX Software Systems > www.qnx.com
175 Terence Matthews Crescent, Kanata, Ontario, Canada K2M 1W8
Tel: 613-591-0931 Fax: 613-591-3579

\