Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does not
show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface 2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned 309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case the
system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
ping…
“Maurizio Rossi” <mrossi@system-group.it> ha scritto nel messaggio
news:ejv59j$1fc$1@inn.qnx.com…
Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does not
show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface 2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned 309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case the
system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
Hi Maurizio:
It turns out that the combination “bind=ip,resolve=file” is not
currently supported. We’ve got an existing PR against it in our database.
Robert.
Maurizio Rossi wrote:
ping…
“Maurizio Rossi” <> mrossi@system-group.it> > ha scritto nel messaggio
news:ejv59j$1fc$> 1@inn.qnx.com> …
Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does not
show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface 2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned 309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth(): qnet_init() -
complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case the
system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
\
Hi Robert,
there is any other available method for “bind=ip” ?
Regards,
Maurizio Rossi
“Robert Craig” <rcraig_at_qnx@nowhere.com> ha scritto nel messaggio
news:ekf4gr$k7s$1@inn.qnx.com…
Hi Maurizio:
It turns out that the combination “bind=ip,resolve=file” is not currently
supported. We’ve got an existing PR against it in our database.
Robert.
Maurizio Rossi wrote:
ping…
“Maurizio Rossi” <> mrossi@system-group.it> > ha scritto nel messaggio
news:ejv59j$1fc$> 1@inn.qnx.com> …
Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does
not show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface 2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned 309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case the
system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
\
Yup… There’s a “resolve=dns” that can be used with IP instead.
Robert.
Maurizio Rossi wrote:
Hi Robert,
there is any other available method for “bind=ip” ?
Regards,
Maurizio Rossi
“Robert Craig” <> rcraig_at_qnx@nowhere.com> > ha scritto nel messaggio
news:ekf4gr$k7s$> 1@inn.qnx.com> …
Hi Maurizio:
It turns out that the combination “bind=ip,resolve=file” is not currently
supported. We’ve got an existing PR against it in our database.
Robert.
Maurizio Rossi wrote:
ping…
“Maurizio Rossi” <> mrossi@system-group.it> > ha scritto nel messaggio
news:ejv59j$1fc$> 1@inn.qnx.com> …
Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does
not show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface 2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned 309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case the
system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
\
Hi Robert,
I’m not an expert in “dns”.
What software/utilities must be used on a network of QNX6 systems to use
QNET and “resolve=dns” option?
Best regards,
Maurizio Rossi
“Robert Craig” <rcraig_at_qnx@nowhere.com> ha scritto nel messaggio
news:eki2hj$kin$1@inn.qnx.com…
Yup… There’s a “resolve=dns” that can be used with IP instead.
Robert.
Maurizio Rossi wrote:
Hi Robert,
there is any other available method for “bind=ip” ?
Regards,
Maurizio Rossi
“Robert Craig” <> rcraig_at_qnx@nowhere.com> > ha scritto nel messaggio
news:ekf4gr$k7s$> 1@inn.qnx.com> …
Hi Maurizio:
It turns out that the combination “bind=ip,resolve=file” is not currently
supported. We’ve got an existing PR against it in our database.
Robert.
Maurizio Rossi wrote:
ping…
“Maurizio Rossi” <> mrossi@system-group.it> > ha scritto nel messaggio
news:ejv59j$1fc$> 1@inn.qnx.com> …
Hi all,
I’m testing QNET (npm-qnet-l4.so) on QNX 6.3 SP3.
When I use the “bind=ip,resolve=file” option the “/net” directory does
not show up.
The “npm-qnet-l4.so” in the system log leaves these messages:
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - calling
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_DL_ADVERT: new interface: ip0: index 0 cell 0 endpt 0 iface
2
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: no existing interface for ND_LOCAL_NODE
Nov 21 16:08:50 7 15 0 npm-qnet(L4): ip_ionet_rx_ctrl():
_IO_NET_MSG_ADDR_ADD: ndb_query_add_name(pippo.mydomain.net) returned
309
Nov 21 16:08:50 7 15 0 npm-qnet(L4): qnet_birth():
qnet_init() - complete: 0
The getconf utility reports:
HOSTNAME=pippo
DOMAIN=mydomain.net
The “/etc/qnet_hosts” file contains:
pippo.mydomain.net 10.100.2.1
I have tried also different options with “bind=ip” but in every case
the system long has the following message recorded:
npm-qnet(L4): ip_ionet_rx_ctrl(): _IO_NET_MSG_ADDR_ADD:
ndb_query_add_name(pippo.mydomain.net) returned 309
Without the “bind=ip” option QNET works.
There is something special about the “bind=ip” option or I’m missing
something?
Regards,
Maurizio Rossi
\