I have to set up a link between multiple QNX networks and a central QNX
system over TCP/IP through X.25 Routers.
Help!
Do I have to do all messaging & transfers in TCP/IP, or is there a way to
configure the system so that all the QNX Nodes can see each other as nodes,
such that “cp //1/xxx file://2/xxx” would still work over the TCP/IP link,
and maybe even be able to use QNX send/receive between globally registered
processes.
All sugestions greatly appreciated.
-Paul
paul@jenosys.com
Quick answer: TCP/IP only
Long answer: Someone was talking about encapsulating FLEET within IP. I dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for that
matter).
-Warren
“Paul Russell” <paul@jenosys.com> wrote in message
news:8plq4v$p7g$1@inn.qnx.com…
| I have to set up a link between multiple QNX networks and a central QNX
| system over TCP/IP through X.25 Routers.
|
| Help!
|
| Do I have to do all messaging & transfers in TCP/IP, or is there a way to
| configure the system so that all the QNX Nodes can see each other as nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the TCP/IP
link,
| and maybe even be able to use QNX send/receive between globally registered
| processes.
|
| All sugestions greatly appreciated.
|
| -Paul
| paul@jenosys.com
It’s rumoured not to work well, because the WAN timeouts confuse FLEET,
but look for “infleet” at ftp.qnx.com, or however that new-fangled web
QDN thing puts stuff.
Sam
Previously, Warren Peece wrote in qdn.public.qnx4:
Quick answer: TCP/IP only
Long answer: Someone was talking about encapsulating FLEET within IP. I dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for that
matter).-Warren
“Paul Russell” <> paul@jenosys.com> > wrote in message
news:8plq4v$p7g$> 1@inn.qnx.com> …
| I have to set up a link between multiple QNX networks and a central QNX
| system over TCP/IP through X.25 Routers.
|
| Help!
|
| Do I have to do all messaging & transfers in TCP/IP, or is there a way to
| configure the system so that all the QNX Nodes can see each other as nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the TCP/IP
link,
| and maybe even be able to use QNX send/receive between globally registered
| processes.
|
| All sugestions greatly appreciated.
|
| -Paul
| > paul@jenosys.com
\
–
Sam Roberts (sam@cogent.ca), Cogent Real-Time Systems (www.cogent.ca)
“Warren Peece” <warren@nospam.com> wrote in message
news:8plrc6$qa5$1@inn.qnx.com…
Quick answer: TCP/IP only
Long answer: Someone was talking about encapsulating FLEET within IP. I
dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for
that
matter).
It is called infleet and available on QNX ftp site. If you link is fast
enough
it should work ok. On slow link FLEET doesn’t perform very well (wasn’t
design for that)
-Warren
“Paul Russell” <> paul@jenosys.com> > wrote in message
news:8plq4v$p7g$> 1@inn.qnx.com> …
| I have to set up a link between multiple QNX networks and a central QNX
| system over TCP/IP through X.25 Routers.
|
| Help!
|
| Do I have to do all messaging & transfers in TCP/IP, or is there a way
to
| configure the system so that all the QNX Nodes can see each other as
nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the
TCP/IP
link,
| and maybe even be able to use QNX send/receive between globally
registered
| processes.
|
| All sugestions greatly appreciated.
|
| -Paul
| > paul@jenosys.com
“Sam Roberts” <sam@cogent.ca> wrote in message
news:Voyager.000912144136.1385A@sam.cogent.ca…
It’s rumoured not to work well, because the WAN timeouts confuse FLEET,
but look for “infleet” at ftp.qnx.com, or however that new-fangled web
QDN thing puts stuff.
Yep, ftp://ftp.qnx.com is still OK, as the old archives will continue to be
available for existing customers.
or for anonymous access to updates:
ftp://updates.qnx.com (without entering in a userid/password or register
products for access to updates)
or
just follow http://support.qnx.com/download/updates/index.html
Sam
Previously, Warren Peece wrote in qdn.public.qnx4:
Quick answer: TCP/IP onlyLong answer: Someone was talking about encapsulating FLEET within IP. I
dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for
that
matter).-Warren
“Paul Russell” <> paul@jenosys.com> > wrote in message
news:8plq4v$p7g$> 1@inn.qnx.com> …
| I have to set up a link between multiple QNX networks and a central
QNX
| system over TCP/IP through X.25 Routers.
|
| Help!
|
| Do I have to do all messaging & transfers in TCP/IP, or is there a way
to
| configure the system so that all the QNX Nodes can see each other as
nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the
TCP/IP
link,
| and maybe even be able to use QNX send/receive between globally
registered
| processes.
|
| All sugestions greatly appreciated.
|
| -Paul
| > paul@jenosys.com
\Sam Roberts (> sam@cogent.ca> ), Cogent Real-Time Systems (> www.cogent.ca> )
Thankyou all for the pointers on infleet. Off I go to try it…
Paul
Mario Charest <mcz@videotron.ca> wrote in message
news:8plt0u$r7f$1@inn.qnx.com…
“Warren Peece” <> warren@nospam.com> > wrote in message
news:8plrc6$qa5$> 1@inn.qnx.com> …
Quick answer: TCP/IP onlyLong answer: Someone was talking about encapsulating FLEET within IP. I
dunno
where that’s at but I haven’t heard that it’s done (or even ongoing, for
that
matter).It is called infleet and available on QNX ftp site. If you link is fast
enough
it should work ok. On slow link FLEET doesn’t perform very well (wasn’t
design for that)
-Warren
“Paul Russell” <> paul@jenosys.com> > wrote in message
news:8plq4v$p7g$> 1@inn.qnx.com> …
| I have to set up a link between multiple QNX networks and a central
QNX
| system over TCP/IP through X.25 Routers.
|
| Help!
|
| Do I have to do all messaging & transfers in TCP/IP, or is there a way
to
| configure the system so that all the QNX Nodes can see each other as
nodes,
| such that “cp file://1/xxx file://2/xxx” would still work over the
TCP/IP
link,
| and maybe even be able to use QNX send/receive between globally
registered
| processes.
|
| All sugestions greatly appreciated.
|
| -Paul
| > paul@jenosys.com
\