Hi Jeff,
On 2012-04-17 Hill, Jeffrey O wrote:
> > I think we should change the way that the RSRV sends out beacon packets
> > from calling connect() followed by send() to just calling sendto().
>
> As I recall, the determining factor is the "connect"ed state of the
> UDP socket, and not which call send/recv/sendto/recvfrom/etc are used,
True; my suggestion is that by not calling connect() at all we would never see
the ICMP errors, which I don't believe we're reporting correctly anyway. IIRC
RSRV always reports the error giving the IP address that it just connected to,
whereas an ICMP error must come from an older UDP packet which may have been
from a different address if we have more than one in the beacon list.
> BTW, in the new server I have allocated a dedicated UDP socket for
> each of the network interfaces that are discovered on the local host,
> and during initialization the list of beacon destination addresses is
> traversed with each of them being assigned to one of these dedicated
> UDP sockets. This avoids any need to connect a UDP socket to a
> destination at any time except, using as I recall a temporary UDP
> socket to determine a local interface used for the beacon's destination,
> during initialization.
Sounds like a better setup, although if you still report errors that wouldn't
help on subnets that have a (possibly incorrectly configured) machine which is
sending ICMP responses to broadcast packets.
- 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 Andrew Johnson
- RE: Channel Access problem over SSH Hill, Jeffrey O
- Navigate by Date:
- Prev:
Re: hardware register access Andrew Johnson
- Next:
RE: log message filter in Asyn matthew.pearson
- 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 Hill, Jeffrey O
- 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
|