David Hawley <David.L.Hawley@computer.org> wrote:
Previously, Xiaodan Tang wrote in qdn.public.qnxrtp.os:
Jason A. Farque’ <> email@example.com> > wrote:
xtang is my friend.
My qnet network fired up and is now showing other nodes in the /net
directory, thanks for the help. Apparently it was the conflicting node
names that was causing problems - why is there no warning or error on
something such as this? One interesting thing is that on my embedded PC
There is warning print out on stderr, “Name Reject !” or sth like that.
The usual problem is because io-net’s stderr didn’t assoicate to any
console. If you do a “reopen” before starting io-net in startup script,
you might be see it.
there’s clearly a config file missing because it is listing the other
machine as “nodea.” (note the period) while the full PC is showing the
embedded PC as “nodeb.net.intra”. So now I have to root around and figure
out how to fix that.
The “node name” works like this:
A node name is a “hostname.domain” string. If your machine’s CS_DOMAIN
is NULL, qnet will add a default domain “net.intra” to it.
Under /net, if the nodes’ domain match local domain, only the node’s
name get displayed.
To your problem, since the your embedded PC don’t have CS_DOMAIN set,
it call himself as “nodeb.net.intra” (as seen on nodea).
The reason nodea seen as “nodea.” is because your full pc does have
a CS_DOMAIN as " ". You may want to check your /etc/net.cfg file, or
run phlip on FULL PC (under photon), and fill out the domain part.
Is this stuff documented anywhere? Yes I’ve searched the KB and gone
through the online docs - the information is not sufficient for a neophyte
such as myself to know for sure that I’ve got everything set up correctly.
I may get everything working and looking proper, but how can I be sure that
there’s not some serious performance flaw or misconfiguration of my system?
There used to be a “network administrition document” covering QNET,
but I am not sure if it is still online (and up to date >
I’ve been avidly following this thread since I haven’t been able to set
a domain name on my system. When I run phlip - it refuses to allow
setting a domain. If I edit /etc/net.cfg and edit the domain line - phlip
deletes the line.
The file looks like this:
nto network config file v1.2
route 192.168.1.1 0.0.0.0 0.0.0.0
lookup file bind
Is it some problem with dhcp?
I believe it because your dhcp server either do not send you a
domain, or send you a blank domain. Since you specificly say
you want dhcp, phlip will just trust dhcp, and erase whatever
you type in. (The information phlip displayed, could be read
as “currect setting”, since you are dhcp, you are not allowed
to change anything
Of cause, this is not very nice. The behaver is changed in
later version of RTP.
For now, you can move your en0 to “mode manual”, and set everything