Len Melo <firstname.lastname@example.org> wrote:
I want to restrict inbound network access only to a QNX node. According to
the documentation for Proc32, the “-L2” option does the trick.
Oddly, the documentation and the usemessage for Proc32 disagree on this:
-L2 Disallow inbound network access, but allow unrestricted
Use message says:
-L2 Only allow inbound network access.
Which is the exact opposite of what the docs say.
I’m not sure which is the actual intention of the code.
(In a quick look through the code, -L2 sets a different flag from -L, so
it shouldn’t give the same behaviour. But, I haven’t yet found where this
BTW, when reporting something like this, it is VERY important to tell us
what version of Proc32 you are running – the output from “sin ver”, the
line for Proc32, is a very good idea to post. If I’m looking at source
to a later version than you’re running, it won’t do either of us much good.
When I rebuild the boot image to use the “-L2” option with Proc32, it
disables outbound network access instead of inbound network access. It
seems like the “-L2” option is the same as the “-L” option.
Here is the actual line in my boot image for Proc32:
$ /boot/sys/Proc32 -l 14 -L2
I’ve tried the “-L” and “-L1” options and they do what the documentation
Is option “-L2” just a typo??
Don’t know yet.
QNX Training Services