qnet problems

I have three cpu running qrtp
SERVEUR_QNX
val_22084
val_22089

SERVEUR_QNX is running full tcp/ip stack but my problem doesn’t depend on the stack.
val_22084 and val_22089 are running tiny tcp/ip stack.
on all of these I mount -T io-net /lib/dll/npm-qnet.so

if I ls /net on SERVEUR_QNX I see
SERVEUR_QNX

if I ls /net on val_22084 I see
val_22084 val_22089

if I ls /net on val_22089 I see
SERVEUR_QNX val_22084 val_22089

where this problem comes from ?

val_22084 and val_22089 are configured via phlip in manual mode

for SERVEUR_QNX, it seems that slaying io-net to restart it by io-net -del900 -ptcpip prevent it to use informations recorded by phlip - why?

so I use

/usr/bin/ifconfig en0 172.20.1.11
/usr/bin/route add default 172.20.25.200
mount -T io-net /lib/dll/npm-qnet.so

I remember having seen that distant machine names were followed by .icbt.com which is my domain name, but I don’t remember how I got it.


I made a test on val_22089 when I was writing this message:
I used phlip to check the configuration and I saw that this machine didn’t have the default gateway configured.
I setted it.
after that, ls /net gave me
val_22084 val_22089

so, SERVEUR_QNX desappeared.

I tried to remove the gateway, same.

I decided to reboot
after a mount -T io-net /lib/dll/npm-qnet.so

ls was good.
I made the test again with phlip but without problem that time. Strange!

Alain.

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:

I have three cpu running qrtp
SERVEUR_QNX
val_22084
val_22089

SERVEUR_QNX is running full tcp/ip stack but my problem doesn’t depend on the stack.
val_22084 and val_22089 are running tiny tcp/ip stack.
on all of these I mount -T io-net /lib/dll/npm-qnet.so

if I ls /net on SERVEUR_QNX I see
SERVEUR_QNX

if I ls /net on val_22084 I see
val_22084 val_22089

if I ls /net on val_22089 I see
SERVEUR_QNX val_22084 val_22089

where this problem comes from ?

Kind of strange to me.

  1. Are all 3 machines have the same version of QRTP ? All of them
    are connect vie ethernet ? What happened if you do a
    “ls /net/val_22084” on SERVEUR_QNX ?

  2. Make sure when you start QNET, (mount -Tio-net /lib/dll/qnet),
    the hostname is set.

  3. The “phlip” don’t do anything, it writes whatever you set into a
    file (/etc/net.cfg). It is the program “netmanager” who read this
    file and set ips,gateways,hostname… So make sure netmanager is
    ran before you start QNET (otherwise, hostname isn’t set).

Here is a little detail of how QNET start/stop:

  1. Everytime QNET started, it broadcast it’s hostname, everybody
    got this broadcast will REPLY with their own name, thus, both
    QNET known each other. And show up in “/net/”.

  2. If for some reason the broadcast/reply is lost, you still could
    do a “ls /net/xxx” to force QNET do a “node discovery”, try to
    find “xxx” on same network.

  3. While you umount QNET/slay io-net, QNET will then broadcast a
    message saying “I am gone”. Everybody who got this message will
    remove “/net/xxx”, so it will disapear “automaticlly”.

-xtang

val_22084 and val_22089 are configured via phlip in manual mode

for SERVEUR_QNX, it seems that slaying io-net to restart it by io-net -del900 -ptcpip prevent it to use informations recorded by phlip - why?

so I use

/usr/bin/ifconfig en0 172.20.1.11
/usr/bin/route add default 172.20.25.200
mount -T io-net /lib/dll/npm-qnet.so

I remember having seen that distant machine names were followed by .icbt.com which is my domain name, but I don’t remember how I got it.



I made a test on val_22089 when I was writing this message:
I used phlip to check the configuration and I saw that this machine didn’t have the default gateway configured.
I setted it.
after that, ls /net gave me
val_22084 val_22089

so, SERVEUR_QNX desappeared.

I tried to remove the gateway, same.

I decided to reboot
after a mount -T io-net /lib/dll/npm-qnet.so

ls was good.
I made the test again with phlip but without problem that time. Strange!

Alain.