Experimental Physics and
Industrial Control System

"Hill, Jeffrey O" <[email protected]> · Tue, 17 Apr 2012 17:33:20 +0000

> > 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.
> 

Since in the new server these, local interface dedicated, UDP sockets are 
bound to a local network interface (with the bind function), but not to 
a destination address (with the connect function), then we will no-longer 
see these oddly mapped (IP ICMP to posix errno) beacon warning messages. 

The EPICS Administrator is nevertheless encouraged to occasionally use 
wireshark, or some similar program, to monitor the ICMP error responses.

Jeff

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System