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: | Post numbers used by CA client |
From: | Stephen Molloy <[email protected]> |
To: | "[email protected]" <[email protected]> |
Date: | Mon, 4 Jul 2016 14:43:00 +0000 |
Hi all,
I’m trying to build a Docker container for quick set-up and tear-down of EPICS instances, and I’ve run into a problem. A CA client outside the container, but on the same host, cannot see any PV’s served from inside the container.
Looking at the network traffic with Wireshark, I can see that the server uses ports 5064 & 5065 as expected, but the ports used by the client seem to be relatively random. If I could predict them, or (even better) force them to be specific ports, then
I could expose those ports in the Docker container and (hopefully) the client and server could communicate properly.
Or perhaps this isn’t the problem, and there is some other network issue getting in my way.
(I’ve successfully run several EPICS installations on this network and from this computer, so I am confident that this is an issue with the Docker set-up.)
Hopefully I’m on the right track with my thinking, and hopefully someone can let me know how to proceed from here?
In case you’re interested, I’m documenting my work on my blog — http://www.smolloy.com/2016/07/easy-epics-implementation-with-docker/
Thanks (again) for your time,
Steve
|