-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
recognize incoming multicast packages #8
Comments
if someone came up with an idea on how to fix that without monkey-patching asyncio, that would be much appreciated; i don't see an elegant solution right now. |
Has there been any work on this topic since this issue-report was last touched? Receiving multicast traffic should not be difficult with the lowlevel socket API... you need one socket to bound to the unicast address (to receive unicast and to send unicast/multicast) and one bound to the multicast IP (to receive multicast). |
Here is a code snippet I used for experimenting with coapthon (3) until I discovered it does not support messages without ACKs: The main issue with this approach is that you cannot easily bind to "0.0.0.0" (because you would get the multicast there too), but you have to register pair of sockets per interface.
|
Much of this has definitely been solved, I'm going through the code to ensure no points of this are left (especially since aiocoap has been using |
Yes, works for me (after the no_response thing in #170 is fixed). |
aiocoap currently does not handle incoming multicast packages specially (but it should).
there are two ways around:
there is a guide to the latter at http://blog.powerdns.com/2012/10/08/on-binding-datagram-udp-sockets-to-the-any-addresses/ -- but as asyncio uses recvfrom and not recvmsg, it might be difficult to wire that up correctly.
The text was updated successfully, but these errors were encountered: