EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024  Index 1994  1995  1996  1997  1998  1999  2000  2001  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: Proposed change to asyn drvAsynIPPort for UDP sockets
From: Mark Rivers <[email protected]>
To: "'Eric Norum'" <[email protected]>
Cc: EPICS Core-Talk <[email protected]>, EPICS Tech Talk <[email protected]>
Date: Wed, 9 Dec 2015 16:14:23 +0000

Ø  Yes, you need a separate address structure and length to hold the sender address.

 

Done and committed to github, tag R4-28beta3.

 

 

From: Eric Norum [mailto:[email protected]]
Sent: Wednesday, December 09, 2015 9:55 AM
To: Mark Rivers
Cc: Torsten bögershaus; EPICS Core-Talk; Henrique Almeida; EPICS Tech Talk
Subject: Re: Proposed change to asyn drvAsynIPPort for UDP sockets

 

.I missed that.

Yes, you need a separate address structure and length to hold the sender address.

 

On Dec 9, 2015, at 7:33 AM, Mark Rivers <[email protected]> wrote:

 

The problem is that when recvfrom() is called in readIt() and flushIt(), the IP address and port of the remote sender will replace the values in tty->farAddr.oa.sa.  This means that the next time octetWrite() is called, it will call sendto() using the address of the last responder, not the address that was originally specified when creating the port.  I don’t think this is the correct behavior.  The solution is to use a local  osiSockAddr variable to receive the sender’s address information in readIt() and flushIt(), not tty->farAddr.oa.sa.

 

-- 
Eric Norum
[email protected]

 


References:
Proposed change to asyn drvAsynIPPort for UDP sockets Mark Rivers
Re: Proposed change to asyn drvAsynIPPort for UDP sockets Henrique Almeida
RE: Proposed change to asyn drvAsynIPPort for UDP sockets Mark Rivers
Re: Proposed change to asyn drvAsynIPPort for UDP sockets Torsten bögershaus
Re: Proposed change to asyn drvAsynIPPort for UDP sockets Eric Norum
RE: Proposed change to asyn drvAsynIPPort for UDP sockets Mark Rivers
Re: Proposed change to asyn drvAsynIPPort for UDP sockets Eric Norum

Navigate by Date:
Prev: Re: Proposed change to asyn drvAsynIPPort for UDP sockets Torsten bögershaus
Next: Re: Request for information from institutions with Archiver Appliance deployments Michael Davidsaver
Index: 1994  1995  1996  1997  1998  1999  2000  2001  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: Proposed change to asyn drvAsynIPPort for UDP sockets Eric Norum
Next: Re: Proposed change to asyn drvAsynIPPort for UDP sockets Torsten bögershaus
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  <20152016  2017  2018  2019  2020  2021  2022  2023  2024 
ANJ, 16 Dec 2015 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·