On 10/6/14 4:24 PM, Andrew Johnson wrote:> Hi Lewis,
>
> http://bazaar.launchpad.net/~epics-core/epics-base/3.15/revision/12508
>
> This was a reimplementation of Freddie's patch, making use of the
> address-list parsing code that was already in Base. If the env var
> contains more than one interface IP it will only use the first one and
> print a warning message (as Freddie's code did).
Hi, Andrew.
OK. I had just searched the code for "EPICS_CAS_INTF_ADDR_LIST" and
didn't find it, so I concluded you hadn't added it yet. I guess the
reason it's not there is because you used the address-list parsing code.
> The CA repeater is part of the CA client library, it is not related to
> either CA server at all.
OK, that's why I suggested a different environment variable would be
needed if it wasn't considered part of the CA server.
> There can only be one CA repeater running on any system, and since all
> clients running on the system need to connect to that single instance
> irrespective of which interfaces they will be searching through, it
> does not need the same kind of configuration variable.
For my use case, I still wish for it. I have a development machine, and
I want everything to be listening on the loopback interface--nothing
else. I wish for an easy way to do that. caRepeater listens on all
interfaces; I just want it to bind to the loopback interface; that's it.
If a new environment variable such as EPICS_CA_REPEATER_INTF_ADDR_LIST
were used, would you be open to that? Or, if you don't like using an
environment variable, what about a command line option to caRepeater to
allow me to specify the bind address (assuming I always start caRepeater
before something that starts it automatically for me)?
Thanks,
Lewis
- Replies:
- Re: Binding an IOC to a single network interface J. Lewis Muir
- Re: Binding an IOC to a single network interface Andrew Johnson
- References:
- Binding an IOC to a single network interface freddie.akeroyd
- Re: Binding an IOC to a single network interface J. Lewis Muir
- Re: Binding an IOC to a single network interface Andrew Johnson
- Navigate by Date:
- Prev:
Re: [EPICS] Support for Staged Installs ? J. Lewis Muir
- Next:
TCP connection status : drvAsynIPPort Patel Jignesh
- 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
- Navigate by Thread:
- Prev:
Re: Binding an IOC to a single network interface Andrew Johnson
- Next:
Re: Binding an IOC to a single network interface J. Lewis Muir
- 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
|