Let's look at a few examples of how you'd use the network manager.

Note: The QNX Neutrino native network manager lsm-qnet.so is actually a shared object that installs into the executable io-pkt*.
Local networks
If you're using the QNX Neutrino RTOS on a small LAN, you can use just the default en_ionet resolver. When a node name that's currently unknown is being resolved, the resolver will broadcast the name request over the LAN, and the node that has the name will respond with an identification message. Once the name's been resolved, it's cached for future reference.

Since en_ionet is the default resolver when you start lsm-qnet.so, you can simply issue commands like:

ls /net/lab2/

If you have a machine called lab2 on your LAN, you'll see the contents of its root directory.

Remote networks
Qnet uses DNS (Domain Name System) when resolving remote names. To use lsm-qnet.so with DNS, you specify this resolver on mount's command line:
Note: For security reasons, you should have a firewall set up on your network before connecting to the Internet. For more information, see pf-faq at ftp://ftp3.usa.openbsd.org/pub/OpenBSD/doc/ in the OpenBSD documentation.
mount -Tio-pkt -o"mount=:,resolve=dns,mount=.com:.net:.edu" /lib/dll/lsm-qnet.so

In this example, Qnet will use both its native en_ionet resolver (indicated by the first mount= command) and DNS for resolving remote names.

Note that we've specified several types of domain names (mount=.com:.net:.edu) as mountpoints, simply to ensure better remote name resolution.

Now you could enter a command such as:

ls /net/qnet.qnx.com/repository

and you'd get a listing of the repository directory at the qnet.qnx.com site.