I see in your sample code that you are using recvfrom(), but with a NULL address. If you instead pass a pointer to a struct sockaddr_tipc and an address_len of sizeof(struct sockaddr_tipc), a successful recvfrom() will set it to the address of the sender, which you can turn around and pass to sendto() in order to reply. I'm using this in my own code, and so far it has worked fine.
Gary Duzan IT Architect Senior GT.M Core Team T: +1.484.302.3226 E: gary.du...@fisglobal.com FIS | Advancing the way the world pays, banks and invests™ ________________________________ From: Rune Torgersen <ru...@innovsys.com> Sent: Friday, June 23, 2023 4:07 PM To: Jon Maloy <jma...@redhat.com>; tipc-discussion@lists.sourceforge.net <tipc-discussion@lists.sourceforge.net> Subject: Re: [tipc-discussion] TIPC out-of-order publish message > -----Original Message----- > From: Jon Maloy <jma...@redhat.com> > On 2023-06-22 09:30, Rune Torgersen wrote: > > I can easily make it happen with known service addresses too. > > > > We have shortlived processes that does a query: > > > > Open 226 1 > > Send query to 226 2. > > 226 2 sends response back to 226 1. - Message gets dropped. > > Is there any reason why you don't use the received messages original > socket address instead of its service address? Basically because we did not know you could do that. Will have to look into that. Is there any example code for that? _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Ftipc-discussion&data=05%7C01%7Cgary.duzan%40fisglobal.com%7Cdb99e789c7df49b57f3c08db742596b3%7Ce3ff91d834c84b15a0b418910a6ac575%7C0%7C0%7C638231477021853799%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=EwRsvge2GyFWYIoLAMhh2KT%2BV3x0x0Oe4FGxxfxQPTo%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/tipc-discussion> The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. _______________________________________________ tipc-discussion mailing list tipc-discussion@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tipc-discussion
