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: Ralph Lange <[email protected]>
To: [email protected]
Cc: [email protected]
Date: Sat, 19 Dec 2015 10:20:01 +0100
On December 18, 2015 11:39:30 PM GMT+01:00, Andrew Johnson <[email protected]> wrote:
>I mis-read Anze's original description, and it now sounds to me like
>there may be a bug in his network stack. Is it really possible to send
>out a broadcast UDP message that has a different IP source address than
>the address of the network interface you're sending it out from? I
>would
>expect something like that to only be possible if you're running as
>root.
>
>Could this me something to do with the configuration of his virtual
>network ports, or with his Wireshark setup? I would like to see this
>experiment repeated on a machine that has multiple real interfaces,
>because it doesn't make sense to me.
>
>- Andrew

Hi Andrew,

While you point out an interesting issue, I don't think it is really relevant for the CA problem Anze sees.

The UDP sender address gets overwritten with the address inside the payload, and that payload address (explicitly set by the IOC, root not required) seems to be always the same, independent from the network the beacon message is sent to.

The client (at least the Java one) possibly can't match the beacon sender to any of its connections, and wrongly classifies the beacon as not being relevant.
This probably has the effect that the IOC going down is not detected properly by the client. It should not affect reconnection for a (re)appearing IOC, as reconnection attempts should always happen on all networks the client uses.

@Anze: a properly detected missing beacon is signaled by the client after ~35 seconds (twice the beacon period plus 5 seconds timeout for a TCP ping). Sending SIGSTOP/SIGCONT to the IOC is a good way to simulate a network-down and recover situation. Can you check this in your setup, for both network interfaces (matching the beacon content and not) and using the Java and C++ implementations?

Cheers,
~Ralph

Replies:
Re: Wrong beacon source IP address Johnson, Andrew N.
References:
Fwd: Wrong beacon source IP address Ralph Lange
Re: Fwd: Wrong beacon source IP address Michael Davidsaver
Re: Fwd: Wrong beacon source IP address Andrew Johnson
Re: Fwd: Wrong beacon source IP address Michael Davidsaver
Re: Fwd: Wrong beacon source IP address Andrew Johnson

Navigate by Date:
Prev: Re: Fwd: Wrong beacon source IP address Andrew Johnson
Next: Re: Wrong beacon source IP address Johnson, Andrew N.
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 Andrew Johnson
Next: Re: Wrong beacon source IP address Johnson, Andrew N.
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 19 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·