I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
Also, is it possible to implement qnet for WAN? I tried
‘mount -Tio-net -o"bind=ip,host=,mount=:<.mydomain.com>,resolve=dn
s" /lib/dll/npm-qnet.so’ but it did not work. I can only see local machine
name in /net. Not sure if it’s becoz qnet need to use a specified port(we
blocked most of the ports that our application does not use).
Anyway, I’m testing on a 6.0beta system(it’s an embedded os).
“Wen” <xiaowen@axs.com.sg> wrote in message news:a2802s$f9n$1@inn.qnx.com…
I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
“Wen” <xiaowen@axs.com.sg> wrote in message news:a2802s$f9n$1@inn.qnx.com…
I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
“Wen” <xiaowen@axs.com.sg> wrote in message news:a281aq$fsb$1@inn.qnx.com…
Also, is it possible to implement qnet for WAN? I tried
‘mount -Tio-net -o"bind=ip,host=,mount=:<.mydomain.com>,resolve=dn
s" /lib/dll/npm-qnet.so’ but it did not work. I can only see local machine
name in /net. Not sure if it’s becoz qnet need to use a specified port(we
blocked most of the ports that our application does not use).
Anyway, I’m testing on a 6.0beta system(it’s an embedded os).
You should really get 6.1, qnet 6.0 had some problem with qnet
“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …
I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
\
It uses raw IP for src/dst addressing but there is no “port” on which it
travels to.
–
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>
“Mario Charest” <goto@nothingness.com> wrote in message
news:a297c5$bbn$1@inn.qnx.com…
“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
\
In that case,what could be the possible reason that qnet fail in WAN? Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.
Wen
“Adam Mallory” <amallory@qnx.com> wrote in message
news:a29cg4$gdv$1@nntp.qnx.com…
It uses raw IP for src/dst addressing but there is no “port” on which it
travels to.–
Cheers,
AdamQNX 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
“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a297c5$bbn$> 1@inn.qnx.com> …“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
\
Will the presence of router interfere with the connection of qnet? Is there
anything we must enable at the router end?
eg.
LAN
adsl network LAN
[qnx machine]---------------[adsl modem
router]-----------------------[adsl modem router]-------------[qnx machine]
| |
| | |
|
10.0.0.4 10.0.0.3 192.168.1.2
192.168.1.1 10.0.0.1 10.0.0.2
“Wen” <xiaowen@axs.com.sg> wrote in message news:a2fr9c$okl$1@inn.qnx.com…
In that case,what could be the possible reason that qnet fail in WAN?
Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s
supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.Wen
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:a29cg4$gdv$> 1@nntp.qnx.com> …It uses raw IP for src/dst addressing but there is no “port” on which it
travels to.–
Cheers,
AdamQNX 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
“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a297c5$bbn$> 1@inn.qnx.com> …“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the
same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
\
seems that got some distortion to my earlier post, here the diagram again
10.0.0.4 10.0.0.3 192.168.1.2
| LAN | |
[qnx machine]-------------------[adsl modem router]
|
| adsl network
|
[qnx machine]-------------------[adsl modem router]
| LAN |
|
10.0.0.2 10.0.0.1 192.168.1.1
Wen
“Wen” <xiaowen@axs.com.sg> wrote in message news:a2fta1$ppn$1@inn.qnx.com…
Will the presence of router interfere with the connection of qnet? Is
there
anything we must enable at the router end?eg.
LAN
adsl network LAN
[qnx machine]---------------[adsl modem
router]-----------------------[adsl modem router]-------------[qnx
machine]
| |
| | |
|
10.0.0.4 10.0.0.3 192.168.1.2
192.168.1.1 10.0.0.1 10.0.0.2
“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2fr9c$okl$> 1@inn.qnx.com> …
In that case,what could be the possible reason that qnet fail in WAN?
Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s
supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.Wen
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:a29cg4$gdv$> 1@nntp.qnx.com> …It uses raw IP for src/dst addressing but there is no “port” on which
it
travels to.–
Cheers,
AdamQNX 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
“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a297c5$bbn$> 1@inn.qnx.com> …“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the
same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
\
Wen <xiaowen@axs.com.sg> wrote:
In that case,what could be the possible reason that qnet fail in WAN? Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.
In a WAN case, (assume you did bind=ip), you won’t see other
node under /net, as long as they are in different network/subnet.
All the nodes show up in /net while start QNET are discovered by
broadcasting.
Even you did not see a node, you still could access it by doing:
ls /net/qnetnode.cross.wan.com/
as long as “qnetnode.cross.wan.com” could be resolved to an IP,
and you specify “resolver=dns”.
-xtang
Wen
“Adam Mallory” <> amallory@qnx.com> > wrote in message
news:a29cg4$gdv$> 1@nntp.qnx.com> …It uses raw IP for src/dst addressing but there is no “port” on which it
travels to.–
Cheers,
AdamQNX 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
“Mario Charest” <> goto@nothingness.com> > wrote in message
news:a297c5$bbn$> 1@inn.qnx.com> …“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2802s$f9n$> 1@inn.qnx.com> …I would like to find out what r the ports being used by qnet.
Does anyone has any ideas?
I’ll take a shot at this; qnet doesn`t use a ports, it sits at the same
level as TCP or UCP, hence it uses an IP packet, no a TCP or UCP
\
Wen <xiaowen@axs.com.sg> wrote:
In that case,what could be the possible reason that qnet fail in WAN? Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.
The other nodes won’t show up under /net until you contact them. Broadcast
like discovery can’t be done over the WAN. If you do an operation (eg. ls)
on /net/nodename.domain (and you have DNS resolving on as one of the QNET options)
you should see the host under /net
-Adam
That what I did when the node did not show up under /net.(i started qnet
using mount -Tio-net -o"host=hostname,bind=ip,resolve=dns"
/lib/dll/npm-qnet.so) I did a ‘ls’ on /net/<nodename.domain> and got ‘no
route to host’ error.
say if I’m able to ping abc.intranet.com, i should be able to access
/net/abc.intranet.com or i need to type /net/hostname.abc.intranet.com or
/net/hostname.intranet.com? (actually all gave a ‘no route to host’ error
but i’m interested in knowing which way is correct)
In a WAN case, (assume you did bind=ip), you won’t see other
node under /net, as long as they are in different network/subnet.
All the nodes show up in /net while start QNET are discovered by
broadcasting.Even you did not see a node, you still could access it by doing:
ls /net/qnetnode.cross.wan.com/
as long as “qnetnode.cross.wan.com” could be resolved to an IP,
and you specify “resolver=dns”.-xtang
Wen
Done but din work 
<amallory@qnx.com> wrote in message news:a2hbmf$pog$1@inn.qnx.com…
Wen <> xiaowen@axs.com.sg> > wrote:
In that case,what could be the possible reason that qnet fail in WAN?
Wrong
parameters? I’m able to get qnet working in LAN but not WAN… it’s
supposed
to be able to work in both right? In WAN, I can’t see the other machines
other than the local machine in /net.
The other nodes won’t show up under /net until you contact them.
Broadcast
like discovery can’t be done over the WAN. If you do an operation (eg.
ls)
on /net/nodename.domain (and you have DNS resolving on as one of the QNET
options)
you should see the host under /net
-Adam
You must specify /net/.FQDN
FQDN = fully qualified domain name.
–
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>
“Wen” <xiaowen@axs.com.sg> wrote in message news:a2ijjg$nfv$1@inn.qnx.com…
That what I did when the node did not show up under /net.(i started qnet
using mount -Tio-net -o"host=hostname,bind=ip,resolve=dns"
/lib/dll/npm-qnet.so) I did a ‘ls’ on /net/<nodename.domain> and got ‘no
route to host’ error.
say if I’m able to ping abc.intranet.com, i should be able to access
/net/abc.intranet.com or i need to type /net/hostname.abc.intranet.com or
/net/hostname.intranet.com? (actually all gave a ‘no route to host’ error
but i’m interested in knowing which way is correct)
In a WAN case, (assume you did bind=ip), you won’t see other
node under /net, as long as they are in different network/subnet.
All the nodes show up in /net while start QNET are discovered by
broadcasting.Even you did not see a node, you still could access it by doing:
ls /net/qnetnode.cross.wan.com/
as long as “qnetnode.cross.wan.com” could be resolved to an IP,
and you specify “resolver=dns”.-xtang
Wen
Did that but still ‘no route to host’ error…
“Adam Mallory” <amallory@qnx.com> wrote in message
news:a2jr0b$3bk$1@nntp.qnx.com…
You must specify /net/.FQDN
FQDN = fully qualified domain name.
–
Cheers,
AdamQNX 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
“Wen” <> xiaowen@axs.com.sg> > wrote in message
news:a2ijjg$nfv$> 1@inn.qnx.com> …
That what I did when the node did not show up under /net.(i started qnet
using mount -Tio-net -o"host=hostname,bind=ip,resolve=dns"
/lib/dll/npm-qnet.so) I did a ‘ls’ on /net/<nodename.domain> and got
‘no
route to host’ error.
say if I’m able to ping abc.intranet.com, i should be able to access
/net/abc.intranet.com or i need to type /net/hostname.abc.intranet.com
or
/net/hostname.intranet.com? (actually all gave a ‘no route to host’
error
but i’m interested in knowing which way is correct)