[Info-vax] VSI and Process Software announcement

[Dirk Munk]

Jan-Erik Soderholm wrote:
> Den 2016-09-21 kl. 19:20, skrev David Froble:
>> Jan-Erik Soderholm wrote:
>>> Den 2016-09-21 kl. 16:26, skrev Kerry Main:
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Info-vax [mailto:info-vax-bounces at rbnsn.com] On Behalf
>>>>> Of Dirk Munk via Info-vax
>>>>> Sent: 21-Sep-16 9:17 AM
>>>>> To: info-vax at rbnsn.com
>>>>> Cc: Dirk Munk <munk at home.nl>
>>>>> Subject: Re: [Info-vax] VSI and Process Software announcement
>>>>>
>>>>> clairgrant71 at gmail.com wrote:
>>>>>>
>>>>> http://www.prweb.com/releases/2016/09/prweb13699173.htm
>>>>>>
>>>>>> VSI has licensed the intellectual property from Process
>>>>> Software to be
>>>>>> the foundation for our own TCPIP stack moving forward.
>>>>>>
>>>>>
>>>>> Excellent news!
>>>>>
>>>>
>>>> Indeed .. as a long time Multinet user, this is great news!
>>>>
>>>> Richard M should also be happy: (IPSEC full support)
>>>>
>>>> extract from link:
>>>> "Some of the major updates include: OpenSSL 1.0.2, SSH (V1 & V2),
>>>> DHCP v3, IPv6 (complete application protocols supported), IPSEC
>>>> (full support), Bind 9.9, Kerberos 5, and advanced features such
>>>> as IPS, paired network interface support, and improved
>>>> performance monitoring capabilities."
>>>>
>>>> :-)
>>>>
>>>> Btw, a sleeper feature that may not be all that well known is the
>>>> embedded IPS (intrusion prevention system) Multinet feature
>>>> mentioned above:
>>>>
>>>> A whitepaper from 2009 -
>>>> http://www.process.com/psc/fileadmin/user_upload/whitepapers/mult
>>>> inet/using_ips.pdf
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Kerry Main
>>>> Kerry dot main at starkgaming dot com
>>>>
>>>
>>> Right, here is one very simple question... :-)
>>>
>>> I have browsed the Multinet documention, but could not
>>> find the answer (maybe becuse the answer is "no" :-) ).
>>>
>>> We create a lot of TNAnnnn: devices by doing like:
>>>
>>> $ telnet /create nn.nn.nn.nn pppp nnnn -
>>>          /prot=none -
>>>          /time=(noidle,recon=00:00:02)
>>>
>>> This creates a TNAnnnn: device pointing to the IP
>>> address nn.nn.nn.nn and port pppp. Usually a port
>>> on a Lantronix terminal server, or some port that
>>> a PLC (with embedded ethernet) is listening to.
>>>
>>> Then our applications communicate over that device
>>> using the usual QIOW calls. Or in some cases (like
>>> label printers) by COPY commands from DCL routines.
>>>
>>> This works very well and is very stable. The whole
>>> issues around network reconnects after an network
>>> outage or a restart of the equipment is handled by
>>> the TCPIP stack, the applications doesn't care.
>>>
>>> Anyway, I could not find a way to create similar
>>> network devices using Multinet. At least not using
>>> the telnet part of Multinet.
>>>
>>> Of course they can have other names than TNAnnnn,
>>> but it would sure be nice to have the same function.
>>>
>>> So, is this possible using Multinet?
>>>
>>> Jan-Erik.
>>
>> Well, I didn't see anything that said they were just going to replace
>> TCP/IP with the Multinet product.  I did see "license IP", which for me
>> sort of indicates a modified or new TCP/IP.  Perhaps what you need
>> will be
>> in the new product.  Note that "early 2017" sort of implies that it's not
>> done yet.
>
> Yes, I thought of that. We do not know how rellevant the current
> Multinet docs are for the "new TCPIP" for VMS... :-)
>
>
I hope VSI will also build NIC drivers with off-load engines for TCP, 
IPsec, iSCSI etc.
At least I assume Multinet has no such drivers.