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 2025 | 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 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: PVA connection problem |
From: | Ralph Lange via Tech-talk <tech-talk at aps.anl.gov> |
To: | EPICS Tech Talk <tech-talk at aps.anl.gov> |
Date: | Fri, 15 Sep 2023 09:24:06 +0200 |
Hello Tech-talk,I'm running into an issue trying to communicate between 2 VMs using pva. In VM1 I have a softIOC running with PVAccess enabled with the following standard configuration.epics> pvasr
pvAccess Server v7.1.6
Active configuration (w/ defaults)
EPICS_PVAS_INTF_ADDR_LIST = 0.0.0.0:5075
EPICS_PVAS_BEACON_ADDR_LIST =
EPICS_PVAS_AUTO_BEACON_ADDR_LIST = YES
EPICS_PVAS_BEACON_PERIOD = 15
EPICS_PVAS_BROADCAST_PORT = 5076
EPICS_PVAS_SERVER_PORT = 5075
EPICS_PVAS_PROVIDER_NAMES = QSRVepics> pval
testSCS:TX
testSCS:RX
testSCS:gcbTx
testSCS:page0epics>[...]The firewall config for the VMs is the followingVM1:$ sudo firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: enp0s3
sources:
services: cockpit dhcpv6-client ssh
ports: 8888/tcp 8888/udp 5064/tcp 5065/tcp 5064/udp 5065/udp
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:[...]For security reasons I need to be able to find a configuration for the firewall that works with PVAccess. Any idea what I could be missing?