EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: Fwd: Wrong beacon source IP address
From: Andrew Johnson <[email protected]>
To: <[email protected]>
Date: Fri, 18 Dec 2015 12:43:57 -0600
On 12/18/2015 07:43 AM, Michael Davidsaver wrote:
> 
> Agreed.  Beacons should appear to come from the appropriate source 
> address.  I should note that RSRV tries to put the correct
> interface address in the message body (and succeeds in at least
> some cases).
> 
> http://bazaar.launchpad.net/~epics-core/epics-base/3.16/view/head:/src/ioc/rsrv/online_notify.c#L263
>
>
> 
>> What are the consequences? Are there any?
> 
> I doubt there are any real consequences either to the present 
> behavior, or to fixing it.

The "Background:" description in Ralph's second message is helpful to
understand what's going on, but it doesn't cover the whole story.

Remember that beacons are received by the CA Repeater running on the
client machine and forwarded to all its CA clients. The repeater
should be listening on all interfaces [aside: it doesn't know anything
about dynamic interfaces, there's another bug someone might want to
think about], so it *will* get multiple copies of any IOC beacons
where both the client machine and IOC have interfaces on more than one
common subnets.

A CA client program running on such a workstation will usually have
EPICS_CA_ADDR_LIST set to only a subset of the interfaces to avoid the
multiple PV warnings, but I'm pretty sure the client library will
still be forwarded the beacons that arrive on all the network
interfaces that the repeater is listening on.

By the IOC always using its first IP address in all its beacons it
reduces the work done by the above CA clients — they only need one
indication from each IOC that it's healthy, so making these duplicates
that can be very quickly discarded is better than getting a separate
beacon for each interface the IOC is connected to.

Thus I do not believe that this behaviour is a bug at all, and it
should not be "fixed". It might be worth adding a note about this to
the protocol documentation.

- Andrew

-- 
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has
always got there first, and is waiting for it.
    -- Terry Pratchett, Reaper Man

Replies:
Re: Fwd: Wrong beacon source IP address Michael Davidsaver
References:
Fwd: Wrong beacon source IP address Ralph Lange
Re: Fwd: Wrong beacon source IP address Michael Davidsaver

Navigate by Date:
Prev: Re: caget delays Michael Davidsaver
Next: Fwd: Re: Wrong beacon source IP address Ralph Lange
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
Navigate by Thread:
Prev: Re: Fwd: Wrong beacon source IP address Michael Davidsaver
Next: Re: Fwd: Wrong beacon source IP address Michael Davidsaver
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 18 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·