The QNX4 interface naming convention for network interfaces is not what I am
failing to understand -
it is the equivalent of the “dev” option in the Linux route command. The
route command under QNX4
is not exactly the same - it doesn’t use the dev specifier ( as I mentioned
When I issue the command:
route add -net 126.96.36.199 -netmask 255.255.255.0 dev en1
I get the following error message: “dev: bad value” ( since dev is NOT a
valid option ).
So, since my initial viewing of the documentation didn’t indicate to me what
was the equivalent to the
“dev” option, then I would like to know what the equivalent way to do this
under QNX since it lacks
“Adam Mallory” <amalloryNOSPAM@NOSPAMqnx.com> wrote in message
route add -net 188.8.131.52 netmask 240.0.0.0 dev eth0
Now, given that I am trying to do this on an imaginary, internal network
192.168.0.*), and that I am trying to configure this with QNX 4.25 and
TCP/IP v.5.0, I was trying to figure out how to convert this to the QNX4
route command. The “dev eth0” command doesn’t appear to be
the QNX4 worlds, so how would one add an entry so that the mrouted
will be able to run?
The route command should be the same, except interface names under QNX4
other *NIX’s) are sometimes different. In this case eth0 should be en0
en1 most likely). Do and ifconfig -a to show all your interfaces, and
QNX Software Systems Ltd.
[ > email@example.com > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> firstname.lastname@example.org