Sorry if this is an obvious question but I am not real
familiar with the interworkings of QNX. We have an
application that runs on QNX and am familiar with
it and how IT relates to the OS.
We have recently set up another node for this app in a
remote location and I would like to be able to dial in
to that system.
I have a user account set up on that system, what do I need
to set up in the sysinit.1 file to be waiting for my call?
Thanks for any info.
David
“David C.” <davidc@eatel.net> wrote in message
news:9qa5bs$pfs$1@inn.qnx.com…
Sorry if this is an obvious question but I am not real
familiar with the interworkings of QNX. We have an
application that runs on QNX and am familiar with
it and how IT relates to the OS.We have recently set up another node for this app in a
remote location and I would like to be able to dial in
to that system.I have a user account set up on that system, what do I need
to set up in the sysinit.1 file to be waiting for my call?
Look at documentation of utility modem and tinit. Or look at
http://qdn.qnx.com/support/docs/qnx4/user_guide/chardev.html
At the bottom of the page there is a an example.
You could also setup a pppd server, that’s a little complex
but allow a Windows machine to connect to it.
Thanks for any info.
David
“Mario Charest” <mcharest@voidzinformatic.com> wrote in message
news:9qagn0$24p$1@inn.qnx.com…
“David C.” <> davidc@eatel.net> > wrote in message
news:9qa5bs$pfs$> 1@inn.qnx.com> …
Sorry if this is an obvious question but I am not real
familiar with the interworkings of QNX. We have an
application that runs on QNX and am familiar with
it and how IT relates to the OS.We have recently set up another node for this app in a
remote location and I would like to be able to dial in
to that system.I have a user account set up on that system, what do I need
to set up in the sysinit.1 file to be waiting for my call?
Look at documentation of utility modem and tinit. Or look at
http://qdn.qnx.com/support/docs/qnx4/user_guide/chardev.html
At the bottom of the page there is a an example.You could also setup a pppd server, that’s a little complex
but allow a Windows machine to connect to it.
Sorry, the above method does allow a Windows machine
to connect the the QNX machine throws a terminal program.
The pppd I was a talking about allows Windows, to telnet,ftp into
the QNX machine.
It’s possible to connect two QNX machines via modem as if they
were on the same network, but it can be painfully slow
Thanks for any info.
David
\
Look at documentation of utility modem and tinit. Or look at
http://qdn.qnx.com/support/docs/qnx4/user_guide/chardev.html
At the bottom of the page there is a an example.You could also setup a pppd server, that’s a little complex
but allow a Windows machine to connect to it.Sorry, the above method does allow a Windows machine
to connect the the QNX machine throws a terminal program.The pppd I was a talking about allows Windows, to telnet,ftp into
the QNX machine.It’s possible to connect two QNX machines via modem as if they
were on the same network, but it can be painfully slow
Thanks I will have a look. Connecting two QNX machines and it
being slow is fine for what I would use it for.
David
Hi David
I have used a dial-up modem to support QNX networking. I does essentially
work but it is worse than just slow. It is unreliable.
What happens is that since the QNX network needs to be a real-time network,
many packets will time-out over the dial-up connection even though they
would have otherwise worked.
“David C.” <davidc@eatel.net> wrote in message
news:9qba4m$f03$1@inn.qnx.com…
Look at documentation of utility modem and tinit. Or look at
http://qdn.qnx.com/support/docs/qnx4/user_guide/chardev.html
At the bottom of the page there is a an example.You could also setup a pppd server, that’s a little complex
but allow a Windows machine to connect to it.Sorry, the above method does allow a Windows machine
to connect the the QNX machine throws a terminal program.The pppd I was a talking about allows Windows, to telnet,ftp into
the QNX machine.It’s possible to connect two QNX machines via modem as if they
were on the same network, but it can be painfully slow
Thanks I will have a look. Connecting two QNX machines and it
being slow is fine for what I would use it for.David
“Alex Cellarius” <acellarius@systems104.co.za> wrote in message
news:1103_1003176357@pentiumii…
On Mon, 15 Oct 2001 07:13:12 -0700, “Bill Caroselli (Q-TPS)”
qtps@earthlink.net> > wrote:
Hi DavidI have used a dial-up modem to support QNX networking. I does
essentially
work but it is worse than just slow. It is unreliable.What happens is that since the QNX network needs to be a real-time
network,
many packets will time-out over the dial-up connection even though they
would have otherwise worked.Bill, I think you mean Net.fd, and if so, would have to agree.
I would also suggest the tinit/modem route, offering a straight
QNX login to the system. TCP/IP would be unnecessary, if
you are going QNX to QNX.Yes I was speaking of Net.fd. I thought that that was what he was
specifically looking for.
If you/he/she just need terminal access then by far, tinit/modem is the way
to go.
Dave, keep in mind that if you do use tinit and modem you can still
upload/download files with qcp which works very well going from QNX to QNX.
On Mon, 15 Oct 2001 07:13:12 -0700, “Bill Caroselli (Q-TPS)” <qtps@earthlink.net> wrote:
Hi David
I have used a dial-up modem to support QNX networking. I does essentially
work but it is worse than just slow. It is unreliable.What happens is that since the QNX network needs to be a real-time network,
many packets will time-out over the dial-up connection even though they
would have otherwise worked.
Bill, I think you mean Net.fd, and if so, would have to agree.
I would also suggest the tinit/modem route, offering a straight
QNX login to the system. TCP/IP would be unnecessary, if
you are going QNX to QNX.
Yes I was speaking of Net.fd. I thought that that was what he was
specifically looking for.If you/he/she just need terminal access then by far, tinit/modem is the
way
to go.Dave, keep in mind that if you do use tinit and modem you can still
upload/download files with qcp which works very well going from QNX to
QNX.
Thanks Bill et all,
Will try the terminal approach and if I need more will
cross that bridge later.
One question about tinit:
An app that is running on our QNX system has a line inserted in the
sysinit file for tinit which, I assume, uses all 6 consoles. Is it a matter
of
just changing that to " tinit cons[1-5] " and then the sixth would be avail
for a modem?
Thanks…
Dave
tinit can support any number of devices. (Or if there is a limit, it is
quite high and I’ve never hit it. I’ve seen tinit lines that monitor 10
consoles, 16 modems and 64 psyudo ttys.) Just add the modem device after
all of the consoles. Also, you will want to add the modem command for your
modem. I.E.
tinit -t /dev/con[1-6] -c "modem {modem options} -t /dev/ser1 &
Basically says that if a byte is received on any console 1 to 6 and there is
no other program monitoring that port then load login (the default command)
on that port. Then set modem as the default command and if a byte is
received on /dev/ser1 to load modem on that port.
There are many options to both tinit and modem. Read the docs for both to
decide what works best for you.
BTW, -t indicates a device to monitor for input, -T says just go ahead and
load this program. This is useful to know.
–
Bill Caroselli – 1(530) 510-7292
Q-TPS Consulting
QTPS@EarthLink.net
“David C.” <davidc@eatel.net> wrote in message
news:9qic14$nod$1@inn.qnx.com…
Thanks Bill et all,
Will try the terminal approach and if I need more will
cross that bridge later.One question about tinit:
An app that is running on our QNX system has a line inserted in the
sysinit file for tinit which, I assume, uses all 6 consoles. Is it a
matter
of
just changing that to " tinit cons[1-5] " and then the sixth would be
avail
for a modem?