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: VCCT and CA sniffer |
From: | Rok Sabjan <[email protected]> |
To: | Chris Payne <[email protected]> |
Cc: | EPICS tech-talk <[email protected]> |
Date: | Thu, 24 Aug 2006 10:52:28 +0200 |
However, in the ISAC Controls system at TRIUMF we use non-standard ports for the main ISAC Control system. Beyond that we also use different ports from our main, non-standard ports for some of the secondary systems (yes, it
can get confusing).
The reasons for these non-standard ports aside, I have a question about how the CA packets will be recognized. Will it be purely based on source/destination port, or some other header in the packet? If it will be based solely on ports, do you foresee the ability to customize the ports associated with the CA protocol in the proposed CA ethereal plug-in?
As a side note, do other labs use non-standard CA ports, or are we on our own here?
Cheers, Rok