jeff smithanik <email@example.com> wrote:
Adam Mallory wrote:
“jeff smithanik” <> firstname.lastname@example.org> > wrote in message
news:> 3C448262.email@example.com> …
We are trying to network two computers together via ethernet, both
running QNX 6.1. One worked just fine, autodetecting the appropriate
driver with no problem. The other computer, an old PII with a 3COM
3C509B ehternet card, gave us problems. It would not autodetect the
driver, so we created an rc.local file as it is described in the online
help. The computer now sees the outside world (voyager works, ping
operates as expected), but when we type ls /net (the equivalent of the
alive command from QNX 4) into the terminal, nothing comes up. When we
do this on the other machine, its own name comes up, but the other one
is still not visible.
Did you include qnet in your io-net command line?
io-net -d -ptcpip -pqnet
----our rc.local file is now as follows on the PC:
mount -T io-net devn-el509.so
mount -T io-net -o ioport=0x300, irq=11,
if=en0:184.108.40.206:255.255.255.0 npm-tcpip.so npm-qnet.so
netmanager -r all
Your rc.local should like this:
mount -T io-net -o ioport=0x300,irq=11 devn-el509.so
mount -T io-net -o if=en0:220.127.116.11:255.255.255.0 npm-ttcpip.so
mount -T io-net npm-qnet.so
netmanager -r all
The different is:
- you need to kill orignal io-net, otherwise you got 2 io-net running.
- “ioport=0x300,irq=11” is driver option (I am not sure you need them),
so must give them to driver.
- “if=…” is tiny tcpip stack (ttcpip) option, if you want to mount
npm-tcpip.so, then mount it without option, and use ifconfig to set
- each module must mount seperatly, so npm-qnet.so should have its own
On the problem machine, we type ifconfig en0 into the terminal and get:
ifconfig:SIOGIFMETRIC en0: operation not supported
en0: flags=8843<UP,BROADCAST, RUNNING, SIMPLEX, MULTICAST
ifnet 18.104.22.168 netmask 0xfffffff00 broadcast 22.214.171.124
On the machine that works, ifconfig en0 returns the same last two lines,
but not the first line.
This probably because you’re running the small stack, use the -ptcpip
option, not -pttcpip
--------this seemed to work - ifconfig en0 renders identical output on both
machines now (no “OPERATION NOT SUPPORTED” business)
In short, we can connect to the outside world, but can not be seen by
other computers, or even itself it seems.
Run inetd on one computer, and then telnet to it from the other - does it
--------I did this, on both computers. I can telnet to either computer from
the other - both work the same. BUT still, ls /net gives no output on the
pc, while on the other machine, it returns the name we have given it.
Thank-you very much for your advice - it is much appreciated.