Hi Michael,
On 2012-04-17 [email protected] wrote:
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Pavel Masloff
>
> > Look. I have noticed that even when I am normally starting
> > an IOC on a linux machine, then I get these messages:
> > online_notify.c:CA beacon (send to "172.20.255.255:5065") error was
> > "Connection refused"
>
> These messages are an old old chestnut and a pain in the bum. We get them
> here all the time on our development network, and I understand that
> they're triggered by a misconfigured IOC somewhere on our network
> incorrectly responding to discovery packets (or something like that). I
> would so much like to see the offending machine thrown in the bin, but
> apparently it's too hard to fix or something.
I started seeing these recently from vxWorks 6.8 and in looking further
discovered how to enable them on Linux too. I think we should change the way
that the RSRV sends out beacon packets from calling connect() followed by
send() to just calling sendto(). The former method allows us to detect ICMP
returns, but it's starting to look like we don't really want to do that,
especially since the error gets reported on a later use of that socket by
which time we may have changed the address if we have more than one address in
the EPICS_CA_ADDR_LIST or EPICS_CAS_BEACON_ADDR_LIST.
Any comments on that idea from the more network-savvy developers out there?
- Andrew
--
Never interrupt your enemy when he is making a mistake.
-- Napoleon Bonaparte
- Replies:
- RE: Channel Access problem over SSH Hill, Jeffrey O
- References:
- Channel Access problem over SSH Pavel Masloff
- Re: Channel Access problem over SSH Pavel Masloff
- RE: Channel Access problem over SSH michael.abbott
- Navigate by Date:
- Prev:
Re: log message filter in Asyn Andrew Johnson
- Next:
Re: log message filter in Asyn Eric Norum
- 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: Channel Access problem over SSH michael.abbott
- Next:
RE: Channel Access problem over SSH Hill, Jeffrey O
- 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
|