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: | Channel Access questions |
From: | "Goff, Steven J" <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Wed, 20 May 2015 15:48:18 +0000 |
Hello, I have two questions about channel Access. First Question: Our configurations has a client workstation with two Ethernet ports – 192.168.1.235 and 192.168.2.235. A server with two Ethernet ports 192.168.1.70 and 192.168.2.70. I want channel access to totally ignore the 192.168.1.X subnet. I thought all I would have to do is set EPICS_CA_ADDR_LIST=”192.168.2.70” and EPICS_CA_AUTO_ADDR_LIST=”NO” on the client side. And EPICS_CAS_AUTO_BEACON_ADDR_LIST=”NO” and EPICS_CAS_BEACON_ADDR_LIST=”192.168.2.255” on the server side.
Those did not work as well as some other variations I tried. However using wireshark all the search request from the client are using the 192.168.1.x subnet? What am I doing wrong? Second Question: Using wireshark after my client connects I see a lot of TCP responses from the server to the client of CA_PROTO_EVENT_ADD. I don’t understand these, can someone explain? Thanks |