I thought that there was an anouncement in March or April that it was now
released. At any rate, I have found it perfectly safe to use.
There was a little gotcha about requiring the new security system, i.e.
login, passwd and converting /etc/shadow. If you do this you will have to
do it for ALL nodes, not just the ones that use the new TCP/IP.
There are some other architectural changes that were a minor inconvienence
too. There is now a shared library for sockets. But it means that
EVERYTHING that uses sockets has to be recompiled/linked.
Try it, you’ll like it! Just give yourself a good day to get it installed
and configured properly. Also, if possible back up your system before you
start.
Bill Caroselli
“Xiaodan Tang” <xtang@qnx.com> wrote in message
news:9la3ev$q4f$1@nntp.qnx.com…
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote:
I am near certain that 5.0 is now officially released. I got my copy
when
it was still in beta.
Someone from QSSL will have to post a link.
Hello Xiaodan! Help Please!
I just checked, the “latest one” is still the one in beta.tcpip, it is in
condition like “release candidate”, but not offically released > 
Brian, you need to talk to > beta@qnx.com > to have access to it.
-xtang
“Brian Delsey” <> bdelsey@ibigroup.com> > wrote in message
news:9l92ip$7eu$> 1@inn.qnx.com> …
Bill…
Thanks for the clarification… but where do we get the upgrade for and
information about 5.0? The QNX web site claims 4.25 is the latest
released
version.
Brian
“Bill Caroselli (Q-TPS)” <> qtps@earthlink.net> > wrote in message
news:9l91ii$6pk$> 1@inn.qnx.com> …
Um . . . Pardon me, but I think that Xiaodan has it backwards.
I believe that TCP/IP 5.0 DOES support supper-netting and that 4.25
does
not.
I am fairly certain that we used supernetting when I was at Sierra
Design
Group and we had to upgrade to 5.0 to do it.
Bill Caroselli
“Brian Delsey” <> bdelsey@ibigroup.com> > wrote in message
news:9l8v2b$5bt$> 1@inn.qnx.com> …
I am running TCP/IP Version 4.25
“Xiaodan Tang” <> xtang@qnx.com> > wrote in message
news:9l8mcc$u6$> 1@nntp.qnx.com> …
Brian Delsey <> bdelsey@mindspring.com> > wrote:
I’m trying to change the default netmask for an interface using
the
ifconfig
utility. When I try to do this for a netmask that is more
restrictive
than
that of the default for the particular address class (e.g.
class B
address),
everything is OK. However, if I try to set the mask to a value
that
is
less
restrictive, ie. one that opens up the network class, it is not
accepted.
For example, I am using the following class C IP address on
en1:
198.168.16.171
The default netmask for this would normally be 255.255.255.0. I
want
to
change this to 255.255.252.0 but am restricted from doing so.
The
ifconfig
command does not complain when this is done, however, the
change
never
takes
place as verified by a subsequent ifconfig request.
You can’t. Not if you are using Tcpip 5.0.
\