Re;tcp/ip and fleet working together

QNX Newsgroups (Archives) qdn.public.qnx4
1

Hi,

We have an existing 5 node QNX system on one lan with native QNX ethernet
(fleet). Now we would like to connect one of those nodes with a wintel box
to extract some relevant information. So far we have a working prototipe
using tcp/ip; one node has qnx os and the other has windows os. Ok.
Now that we are thinking how to procced with the existing 5 node system,
have the question how to make the os distinguish the brand new NIC -which
have to work with tcp/ip- from the existing NIC which is working with fleet.

Since the QNX system is working in an industrial process, we would like to
make the things right in a window time that we are going to have.


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52 (81) 8340·0006
Fax: +52 (81) 8340·0014

2

Can you re-explain what you are trying to do?

I think you want to connect a Windows box to access your QNX network. Is
that right?

Access how? As a terminal? Access the filesystem?

Or do you want to write a program to send messages back and forth between
QNX and Windows?

“Oscar E. Soto” <osoto@eurotech.com.mx> wrote in message
news:ak0h13$2o9$1@inn.qnx.com…

Hi,

We have an existing 5 node QNX system on one lan with native QNX ethernet
(fleet). Now we would like to connect one of those nodes with a wintel box
to extract some relevant information. So far we have a working prototipe
using tcp/ip; one node has qnx os and the other has windows os. Ok.
Now that we are thinking how to procced with the existing 5 node system,
have the question how to make the os distinguish the brand new NIC -which
have to work with tcp/ip- from the existing NIC which is working with
fleet.

Since the QNX system is working in an industrial process, we would like to
make the things right in a window time that we are going to have.


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52 (81) 8340·0006
Fax: +52 (81) 8340·0014

3

Thanks for your help, Bill. I hope this clarify what my question is (so
far)…

Actually what I try to do is to pass some variables back and forth between
qnx and windows machines. We do not need to see the other´s machine file
system, neither connect a terminal.
For testing purposes here in the office, I have set up a qnx machine and a
windows machine in a ethernet tcp/ip network. I can ping one each other and
seems have the proper setup (I can telnet qnx machine from windows command
box). But the real need is to connect the windows pc to a specific QNX node
within a existing 5 node QNX network. Without going further I have the
following question.

So far here in the office, I have on my QNX machine just 1 NIC working with
tcp/ip. What would happen with a QNX machine which already has a NIC
working with fleet and has to accept a new (another) NIC but working with
tcp/ip in a separate network? I am confuse about how to tell the os which
NIC belongs to what network. I know what to do if I have 2 NIC´s in a node
to work in two separate QNX (fleet) networks, but I do not know what to do
when 1 NIC is for fleet network and the other NIC is for tcp/ip.

Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> escribió en el mensaje
news:ak0hmb$33o$1@inn.qnx.com…

Can you re-explain what you are trying to do?

I think you want to connect a Windows box to access your QNX network. Is
that right?

Access how? As a terminal? Access the filesystem?

Or do you want to write a program to send messages back and forth between
QNX and Windows?

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak0h13$2o9$> 1@inn.qnx.com> …
Hi,

We have an existing 5 node QNX system on one lan with native QNX
ethernet
(fleet). Now we would like to connect one of those nodes with a wintel
box
to extract some relevant information. So far we have a working prototipe
using tcp/ip; one node has qnx os and the other has windows os. Ok.
Now that we are thinking how to procced with the existing 5 node
system,
have the question how to make the os distinguish the brand new
NIC -which
have to work with tcp/ip- from the existing NIC which is working with
fleet.

Since the QNX system is working in an industrial process, we would like
to
make the things right in a window time that we are going to have.


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52 (81) 8340·0006
Fax: +52 (81) 8340·0014

\

4

OK. When you load the Net.whatever driver, if there is more than one NIC
you must use the -l (letter el not number) to indicate which device is NIC 1
and which is NIC 2.

From here you can configure fleet which looks at the /etc/config/netmap
file. The first column indicates the logical lan number or NIC card.

To configure TCP/IP you must use ifconfig and give the second NIC a unique
IP address. But why do you need a second NIC at all? You can run both
TCP/IP & fleet on the same NIC.

If on the other hand you want to access a different qnx node than the one
you are already running TCP/IP on you will need a second TCP/IP runtime
license.

“Oscar E. Soto” <osoto@eurotech.com.mx> wrote in message
news:ak0mis$679$1@inn.qnx.com…

Thanks for your help, Bill. I hope this clarify what my question is (so
far)…

Actually what I try to do is to pass some variables back and forth between
qnx and windows machines. We do not need to see the other´s machine file
system, neither connect a terminal.
For testing purposes here in the office, I have set up a qnx machine and a
windows machine in a ethernet tcp/ip network. I can ping one each other
and
seems have the proper setup (I can telnet qnx machine from windows
command
box). But the real need is to connect the windows pc to a specific QNX
node
within a existing 5 node QNX network. Without going further I have the
following question.

So far here in the office, I have on my QNX machine just 1 NIC working
with
tcp/ip. What would happen with a QNX machine which already has a NIC
working with fleet and has to accept a new (another) NIC but working with
tcp/ip in a separate network? I am confuse about how to tell the os which
NIC belongs to what network. I know what to do if I have 2 NIC´s in a node
to work in two separate QNX (fleet) networks, but I do not know what to do
when 1 NIC is for fleet network and the other NIC is for tcp/ip.

Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak0hmb$33o$> 1@inn.qnx.com> …
Can you re-explain what you are trying to do?

I think you want to connect a Windows box to access your QNX network.
Is
that right?

Access how? As a terminal? Access the filesystem?

Or do you want to write a program to send messages back and forth
between
QNX and Windows?

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak0h13$2o9$> 1@inn.qnx.com> …
Hi,

We have an existing 5 node QNX system on one lan with native QNX
ethernet
(fleet). Now we would like to connect one of those nodes with a wintel
box
to extract some relevant information. So far we have a working
prototipe
using tcp/ip; one node has qnx os and the other has windows os. Ok.
Now that we are thinking how to procced with the existing 5 node
system,
have the question how to make the os distinguish the brand new
NIC -which
have to work with tcp/ip- from the existing NIC which is working with
fleet.

Since the QNX system is working in an industrial process, we would
like
to
make the things right in a window time that we are going to have.


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52 (81) 8340·0006
Fax: +52 (81) 8340·0014





\

5

Thanks!.
I was not sure wheter or not was possible for a NIC to work with tcp/ip and
fleet “at the same time”. However, my customer wants to keep isolated their
process network (qnx) from their administrative network (windows).


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014


“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> escribió en el mensaje
news:ak0nuj$710$1@inn.qnx.com…

OK. When you load the Net.whatever driver, if there is more than one NIC
you must use the -l (letter el not number) to indicate which device is NIC
1
and which is NIC 2.

From here you can configure fleet which looks at the /etc/config/netmap
file. The first column indicates the logical lan number or NIC card.

To configure TCP/IP you must use ifconfig and give the second NIC a unique
IP address. But why do you need a second NIC at all? You can run both
TCP/IP & fleet on the same NIC.

If on the other hand you want to access a different qnx node than the one
you are already running TCP/IP on you will need a second TCP/IP runtime
license.

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak0mis$679$> 1@inn.qnx.com> …
Thanks for your help, Bill. I hope this clarify what my question is (so
far)…

Actually what I try to do is to pass some variables back and forth
between
qnx and windows machines. We do not need to see the other´s machine file
system, neither connect a terminal.
For testing purposes here in the office, I have set up a qnx machine and
a
windows machine in a ethernet tcp/ip network. I can ping one each other
and
seems have the proper setup (I can telnet qnx machine from windows
command
box). But the real need is to connect the windows pc to a specific QNX
node
within a existing 5 node QNX network. Without going further I have the
following question.

So far here in the office, I have on my QNX machine just 1 NIC working
with
tcp/ip. What would happen with a QNX machine which already has a NIC
working with fleet and has to accept a new (another) NIC but working
with
tcp/ip in a separate network? I am confuse about how to tell the os
which
NIC belongs to what network. I know what to do if I have 2 NIC´s in a
node
to work in two separate QNX (fleet) networks, but I do not know what to
do
when 1 NIC is for fleet network and the other NIC is for tcp/ip.

Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak0hmb$33o$> 1@inn.qnx.com> …
Can you re-explain what you are trying to do?

I think you want to connect a Windows box to access your QNX network.
Is
that right?

Access how? As a terminal? Access the filesystem?

Or do you want to write a program to send messages back and forth
between
QNX and Windows?

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak0h13$2o9$> 1@inn.qnx.com> …
Hi,

We have an existing 5 node QNX system on one lan with native QNX
ethernet
(fleet). Now we would like to connect one of those nodes with a
wintel
box
to extract some relevant information. So far we have a working
prototipe
using tcp/ip; one node has qnx os and the other has windows os. Ok.
Now that we are thinking how to procced with the existing 5 node
system,
have the question how to make the os distinguish the brand new
NIC -which
have to work with tcp/ip- from the existing NIC which is working
with
fleet.

Since the QNX system is working in an industrial process, we would
like
to
make the things right in a window time that we are going to have.


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52 (81) 8340·0006
Fax: +52 (81) 8340·0014







\

6

OK. That’s a reasonable thought.

So do you have all of your problems solved?

“Oscar E. Soto” <osoto@eurotech.com.mx> wrote in message
news:ak100k$d9u$1@inn.qnx.com…

Thanks!.
I was not sure wheter or not was possible for a NIC to work with tcp/ip
and
fleet “at the same time”. However, my customer wants to keep isolated
their
process network (qnx) from their administrative network (windows).


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014


“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak0nuj$710$> 1@inn.qnx.com> …
OK. When you load the Net.whatever driver, if there is more than one
NIC
you must use the -l (letter el not number) to indicate which device is
NIC
1
and which is NIC 2.

From here you can configure fleet which looks at the /etc/config/netmap
file. The first column indicates the logical lan number or NIC card.

To configure TCP/IP you must use ifconfig and give the second NIC a
unique
IP address. But why do you need a second NIC at all? You can run both
TCP/IP & fleet on the same NIC.

If on the other hand you want to access a different qnx node than the
one
you are already running TCP/IP on you will need a second TCP/IP runtime
license.

7

Thanks for asking. So far I am so so.
I am using a piece of software developed by Cogent which is called Cascade
Connect to pass the variables back and forth. to present a DDE interface in
Windows side.

By the way, I am testing some qnx libraries called data server library;
ds_something(), when I compile my program, the linker gives me:

ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the prototype for
those functions exists in ds.h but the functions are not in the libraries.
Is that right?. These data server libraries come with tcp/ip libraries. Do
you have a clue how to solve this??



Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> escribió en el mensaje
news:ak12mt$f9l$1@inn.qnx.com…

OK. That’s a reasonable thought.

So do you have all of your problems solved?

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak100k$d9u$> 1@inn.qnx.com> …
Thanks!.
I was not sure wheter or not was possible for a NIC to work with tcp/ip
and
fleet “at the same time”. However, my customer wants to keep isolated
their
process network (qnx) from their administrative network (windows).


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014


“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak0nuj$710$> 1@inn.qnx.com> …
OK. When you load the Net.whatever driver, if there is more than one
NIC
you must use the -l (letter el not number) to indicate which device is
NIC
1
and which is NIC 2.

From here you can configure fleet which looks at the
/etc/config/netmap
file. The first column indicates the logical lan number or NIC card.

To configure TCP/IP you must use ifconfig and give the second NIC a
unique
IP address. But why do you need a second NIC at all? You can run
both
TCP/IP & fleet on the same NIC.

If on the other hand you want to access a different qnx node than the
one
you are already running TCP/IP on you will need a second TCP/IP
runtime
license.

8

I don’t know. I’ve used the data server functions under QNX6 but not QNX 4.

Someone from QSSL will have to say where the library for the data server
(ds_*() ) functions are.

“Oscar E. Soto” <osoto@eurotech.com.mx> wrote in message
news:ak5fn4$mgu$1@inn.qnx.com…

Thanks for asking. So far I am so so.
I am using a piece of software developed by Cogent which is called Cascade
Connect to pass the variables back and forth. to present a DDE interface
in
Windows side.

By the way, I am testing some qnx libraries called data server library;
ds_something(), when I compile my program, the linker gives me:

ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the prototype
for
those functions exists in ds.h but the functions are not in the libraries.
Is that right?. These data server libraries come with tcp/ip libraries. Do
you have a clue how to solve this??



Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak12mt$f9l$> 1@inn.qnx.com> …
OK. That’s a reasonable thought.

So do you have all of your problems solved?

“Oscar E. Soto” <> osoto@eurotech.com.mx> > wrote in message
news:ak100k$d9u$> 1@inn.qnx.com> …
Thanks!.
I was not sure wheter or not was possible for a NIC to work with
tcp/ip
and
fleet “at the same time”. However, my customer wants to keep isolated
their
process network (qnx) from their administrative network (windows).


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014


“Bill Caroselli (Q-TPS)” <> QTPS@EarthLink.net> > escribió en el mensaje
news:ak0nuj$710$> 1@inn.qnx.com> …
OK. When you load the Net.whatever driver, if there is more than
one
NIC
you must use the -l (letter el not number) to indicate which device
is
NIC
1
and which is NIC 2.

From here you can configure fleet which looks at the
/etc/config/netmap
file. The first column indicates the logical lan number or NIC
card.

To configure TCP/IP you must use ifconfig and give the second NIC a
unique
IP address. But why do you need a second NIC at all? You can run
both
TCP/IP & fleet on the same NIC.

If on the other hand you want to access a different qnx node than
the
one
you are already running TCP/IP on you will need a second TCP/IP
runtime
license.

\

9

Oscar E. Soto <osoto@eurotech.com.mx> wrote in message
news:ak5fn4$mgu$1@inn.qnx.com…

ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the prototype
for
those functions exists in ds.h but the functions are not in the libraries.
Is that right?. These data server libraries come with tcp/ip libraries. Do
you have a clue how to solve this??

You need to link against the data server library: For example:

cc -o main main.c -lds

–

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

10

Thanks guys!


Oscar E. Soto Hinojosa

Control Adaptable SA de CV
Tel: +52(81) 8340·0006
Fax: +52(81) 8340·0014

“Adam Mallory” <amallory@qnx.com> escribió en el mensaje
news:ak5qe0$rck$1@nntp.qnx.com…

Oscar E. Soto <> osoto@eurotech.com.mx> > wrote in message
news:ak5fn4$mgu$> 1@inn.qnx.com> …
ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the prototype
for
those functions exists in ds.h but the functions are not in the
libraries.
Is that right?. These data server libraries come with tcp/ip libraries.
Do
you have a clue how to solve this??

You need to link against the data server library: For example:

cc -o main main.c -lds

–

Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

11

I don’t have this on my system. Where can I get it for QNX4?

“Adam Mallory” <amallory@qnx.com> wrote in message
news:ak5qe0$rck$1@nntp.qnx.com…

Oscar E. Soto <> osoto@eurotech.com.mx> > wrote in message
news:ak5fn4$mgu$> 1@inn.qnx.com> …
ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the prototype
for
those functions exists in ds.h but the functions are not in the
libraries.
Is that right?. These data server libraries come with tcp/ip libraries.
Do
you have a clue how to solve this??

You need to link against the data server library: For example:

cc -o main main.c -lds

–

Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

12

Sorry. I do have ds3r.lib and ds3s.lib.

“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> wrote in message
news:ak5ssl$21r$1@inn.qnx.com…

I don’t have this on my system. Where can I get it for QNX4?

“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:ak5qe0$rck$> 1@nntp.qnx.com> …
Oscar E. Soto <> osoto@eurotech.com.mx> > wrote in message
news:ak5fn4$mgu$> 1@inn.qnx.com> …
ds_register_ is an undefined reference
ds_create_ is an undefined reference
ds_set_ is an undefined reference

The header ds.h is included in my source file. Looks like the
prototype
for
those functions exists in ds.h but the functions are not in the
libraries.
Is that right?. These data server libraries come with tcp/ip
libraries.
Do
you have a clue how to solve this??

You need to link against the data server library: For example:

cc -o main main.c -lds

–

Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

\

13

Bill Caroselli (Q-TPS) <QTPS@EarthLink.net> wrote in message
news:ak5svu$222$1@inn.qnx.com…

Sorry. I do have ds3r.lib and ds3s.lib.

More coffee Bill? :wink:

\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

14

Touché! ;~}

(Sorry. Don’t know how to type accent marks. Don’t care either.)

“Adam Mallory” <amallory@qnx.com> wrote in message
news:ak62c3$731$1@nntp.qnx.com…

Bill Caroselli (Q-TPS) <> QTPS@EarthLink.net> > wrote in message
news:ak5svu$222$> 1@inn.qnx.com> …
Sorry. I do have ds3r.lib and ds3s.lib.

More coffee Bill? > :wink:

\

Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

15

“Bill Caroselli (Q-TPS)” <QTPS@EarthLink.net> wrote in message
news:ak6766$97i$1@inn.qnx.com…

Touché! ;~}

(Sorry. Don’t know how to type accent marks. Don’t care either.)

The spell checker did that one for me.