Nope. Am looking at:
It says explicitly:
The QNX network manager (io-net) lets you load multiple protocol shared
objects (e.g. npm-tcpip.so) This means, for example, that you can load
several instances of the TCP/IP stack on the same physical interface, making
it easy to create multiple virtual networks (VLANs). You can even run
multiple, independent instances of the network manager (io-net) itself. As
with all QNX system components, each io-net naturally benefits from complete
memory protection thanks to QNX’s microkernel architecture.
“Adam Mallory” <email@example.com> wrote in message
Which docs are you looking at? Are you sure it isn’t saying multiple
protocol stacks (ie. tcpip and qnet)?
QNX Software Systems Ltd.
[ > firstname.lastname@example.org > ]
With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> email@example.com
“Rommel Dongre” <> firstname.lastname@example.org> > wrote in message
news:aeo0kd$nk7$> email@example.com> …
The QnX documentaion on the web talks about it’s ability to support
multiple TCP/IP stacks on the same physical interface. However, I was
able to find any document explaining how one achives this.
Also, assuming I do set up multiple stacks, do they all see multiple
virtual interfaces (vifs, if present) as one big interface? Or can I
configure 1 stack per vif ?
Help would be greatly appreciated. (An email would be splendid!)