[Bug 1971737] Re: EPICS 3.13 clients cannot connect to EPICS 7 or 3.16

[mdavidsaver via Core-talk <core-talk at aps.anl.gov>]

> ... I have no package capture but I have added printf debugging to
camessage. ...

Could you record some?  I would help me (and others) to avoid further
unintended breakage if there were some "as built" records of CA from the
era before IOCs could run on Linux.  Otherwise, I'm left using the
conditionals in the source code to guess how packets were structured.

> ... There are plans to remove them in the SLS-2 upgrade in a few years
...

Were I in your place, I would move these ancient IOCs behind a cagateway
(built against 3.14) and then try my best to forget about them.

Alternately, maybe we can collect donations next week to start a 3.13
retirement fund?

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1971737

Title:
  EPICS 3.13 clients cannot connect to EPICS 7 or 3.16

Status in EPICS Base:
  New

Bug description:
  Since commit 95fd255d "rsrv: ignore CA client version older than v4.4"
  from Jul 30 2016, EPICS 3.13 clients cannot connect any more, even
  though their CA version is V4.8.

  The reason is that camessage drops the incoming CA_PROTO_SEARCH
  messages because the 3.13 client has not yet sent a CA_PROTO_VERSION
  message and thus the code reads client->minor_version_number as 0.

  This is a huge hindrance for upgrading 3.14 IOCs to EPICS 7 when there
  are still 3.13 IOC (which cannot be upgraded yet) in the network which
  need to connect.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1971737/+subscriptions