1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 <2023> 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: PVA connection problem |
From: | Michael Davidsaver via Tech-talk <tech-talk at aps.anl.gov> |
To: | Jure Varlec <jure.varlec at cosylab.com> |
Cc: | tech-talk at aps.anl.gov |
Date: | Fri, 15 Sep 2023 14:10:30 +0200 |
On 9/15/23 11:20, Jure Varlec via Tech-talk wrote:
On 9/15/23 09:24, Ralph Lange via Tech-talk wrote:Sorry for asking the obvious: Have you tried adding the PVA ports 5075/5076 in the same way as the CA ports 5064/5065? Cheers, ~RalphBut note that, depending on the firewall's connection tracking, just adding these ports may not be sufficient to talk to IOCs because of an issue in pvAccessCPP. Ask me how I know ... https://github.com/epics-base/pvAccessCPP/issues/159
Thank you for giving me an opportunity to mention that PVXS address both issues :) Concerning #159 , a PVXS server search replies will come from the search port (5076/udp by default), so a stateful firewall can more easily associate search request with reply. Also, PVXS servers use EPICS_PVAS_SERVER_PORT to choose a fixed TCP port other than 5075, which can help in situations with a firewall and more than one IOC. https://mdavidsaver.github.io/pvxs/