QNX4 Networking

I have connected an 3COM 3509 Network card into PC hardware made by
XYCOM. Part of the sysinit.1 file is as follows:

Net &
Net.ether3509 -p300 -l1 &
netmap -f

ifconfig en1 displayed the following:

en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST>
inet 10.108.112.250 netmask ff000000 broadcast 10.255.255.255

I am able to ping the loalhost and perform a self ping successfully. I
cannot however, ping another PC or get pinged by another PC over the
network. Any suggestions?

Regards,

Dan Szymanski

“Daniel Szymanski” <szymanski@sanyo-machine.com> wrote in message
news:3CA24FFE.E7FD5176@sanyo-machine.com

I have connected an 3COM 3509 Network card into PC hardware made by
XYCOM. Part of the sysinit.1 file is as follows:

Net &
Net.ether3509 -p300 -l1 &

I’ve never heard of Net.ether3509, Net.ether509 maybe)

You didn’t specify the interrupt (-i ) that is probably your problem.

netmap -f

Don’t need netmap -f if all you will be doing is TCP/IP.
That for QNX own networking protocol only.

ifconfig en1 displayed the following:

en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST
inet 10.108.112.250 netmask ff000000 broadcast 10.255.255.255

I am able to ping the loalhost and perform a self ping successfully. I
cannot however, ping another PC or get pinged by another PC over the
network. Any suggestions?

Regards,

Dan Szymanski

Daniel Szymanski wrote:

I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned. This is the
first time I have had any problems in using it with QNX.

Actually no. The 3com 509 is the one card for which there is a QNX
driver, but QSSL explicitly recommends against using (due to the fact
that it has such a pathetically small buffer IIRC).

QNX used to ship with a rather humourous technote regarding the 509 (in
/etc/technotes) but I suspect the lawyers and marketeers have long since
done away with that technote…

Rennie

Sorry, I mistyped (should be Net.ether509). I thought that it was not
necessary to use interrupts unless more than one card was being used in the
PC (according to the utilities reference anyway). In any event, I tried
i11, i10, i5 to no avail. I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned. This is the
first time I have had any problems in using it with QNX.

Mario Charest wrote:

“Daniel Szymanski” <> szymanski@sanyo-machine.com> > wrote in message
news:> 3CA24FFE.E7FD5176@sanyo-machine.com> …
I have connected an 3COM 3509 Network card into PC hardware made by
XYCOM. Part of the sysinit.1 file is as follows:

Net &
Net.ether3509 -p300 -l1 &

I’ve never heard of Net.ether3509, Net.ether509 maybe)

You didn’t specify the interrupt (-i ) that is probably your problem.

netmap -f

Don’t need netmap -f if all you will be doing is TCP/IP.
That for QNX own networking protocol only.


ifconfig en1 displayed the following:

en1: flags=8863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,MULTICAST
inet 10.108.112.250 netmask ff000000 broadcast 10.255.255.255

I am able to ping the loalhost and perform a self ping successfully. I
cannot however, ping another PC or get pinged by another PC over the
network. Any suggestions?

Regards,

Dan Szymanski

“Rennie Allen” <rallen@csical.com> wrote in message
news:3CA24590.70903@csical.com

Daniel Szymanski wrote:

I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned. This
is the
first time I have had any problems in using it with QNX.


Actually no. The 3com 509 is the one card for which there is a QNX
driver, but QSSL explicitly recommends against using (due to the fact
that it has such a pathetically small buffer IIRC).

QNX used to ship with a rather humourous technote regarding the 509 (in
/etc/technotes) but I suspect the lawyers and marketeers have long since
done away with that technote…

Yeah, if you want to be successfull you have to not tell the thruth ;-(

Rennie

Some addtional information and questions:

Is there a utility for QNX 4 that can survey your PC and determine available
interrupts and I/O port addresses?

Specifically, for a NIC, I ran nettrap and it returned what should (or could)
be used, this included the I/O port, but not the interrupt address. I have
plug and play disabled on my NIC, and have manually set the I/O and inte INT,
but still have the problem explained above. I do not think it is guaranteed
that everything returned by nettrap is in fact available, is it? Is there
another way to confirm what is?

Thank you,

Dan Szymanski


Mario Charest wrote:

“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3CA24590.70903@csical.com> …
Daniel Szymanski wrote:

I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned. This
is the
first time I have had any problems in using it with QNX.


Actually no. The 3com 509 is the one card for which there is a QNX
driver, but QSSL explicitly recommends against using (due to the fact
that it has such a pathetically small buffer IIRC).

QNX used to ship with a rather humourous technote regarding the 509 (in
/etc/technotes) but I suspect the lawyers and marketeers have long since
done away with that technote…

Yeah, if you want to be successfull you have to not tell the thruth ;-(


Rennie

“Daniel Szymanski” <szymanski@sanyo-machine.com> wrote in message
news:3CA8C512.2A84708E@sanyo-machine.com

Some addtional information and questions:

Is there a utility for QNX 4 that can survey your PC and determine
available
interrupts and I/O port addresses?

Not really. There is a free isapnp driver available on QNX ftp site, it can
help
deal with ISA devices, but that driver doesn’t interact with any of the QNX
drivers.

Specifically, for a NIC, I ran nettrap and it returned what should (or
could)
be used, this included the I/O port, but not the interrupt address.

It return what it things is the current resources use by the card,
I beleive on some hardware it can’t find the interrupt (or lets
the driver detect it)


I have
plug and play disabled on my NIC, and have manually set the I/O and inte
INT,
but still have the problem explained above. I do not think it is
guaranteed
that everything returned by nettrap is in fact available, is it?

< Is there another way to confirm what is?

No, you have to look at the hardware in your machine an resolved
all conflict yourself.

Thank you,

Dan Szymanski


Mario Charest wrote:

“Rennie Allen” <> rallen@csical.com> > wrote in message
news:> 3CA24590.70903@csical.com> …
Daniel Szymanski wrote:

I thought that this 3COM card was “the mother of
all network cards” as far a compatibility with QNX is concerned.
This
is the
first time I have had any problems in using it with QNX.


Actually no. The 3com 509 is the one card for which there is a QNX
driver, but QSSL explicitly recommends against using (due to the
fact
that it has such a pathetically small buffer IIRC).

QNX used to ship with a rather humourous technote regarding the 509
(in
/etc/technotes) but I suspect the lawyers and marketeers have long
since
done away with that technote…

Yeah, if you want to be successfull you have to not tell the thruth ;-(


Rennie