HI Thiago Please confirm if you are suggesting this 1) Use IP_PKTINFO to detect the packet type whether it is MULTICAST or UNICAST. 2) Then start the timer for processing the request 3) If the request is received as unicast packet and gets processed(response sent) then we can ignore the request received in well known socket as multicast packet.
On Wed, Apr 1, 2015 at 9:29 PM, Thiago Macieira <thiago.macieira at intel.com> wrote: > On Wednesday 01 April 2015 17:03:14 Carsten Bormann wrote: > > Hence hacks such as SO_BINDTODEVICE (which appears to be Linux only). > > According to RFC 3542 [1], IPV6_PKTINFO does have an outgoing interface > > index. I haven't done the necessary research here to see how well that > > is implemented. It will probably pay to talk to the DHCP and DNS > > implementer community; they have lots of experience with this issue. > > Works fine on Linux and the code compiled fine on OS X, FreeBSD and > Windows for > me. > > IPv4's equivalent (IP_PKTINFO) is a non-standard extension. It works on OS > X > and Windows, but breaks on FreeBSD due to lack of support. > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center > > _______________________________________________ > iotivity-dev mailing list > iotivity-dev at lists.iotivity.org > https://lists.iotivity.org/mailman/listinfo/iotivity-dev > -- Regards, Chandan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20150401/832f0b0b/attachment.html>
