Skip to content
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

Support for non-multicast network #191

Open
Chupaka opened this issue Jan 19, 2021 · 0 comments
Open

Support for non-multicast network #191

Chupaka opened this issue Jan 19, 2021 · 0 comments

Comments

@Chupaka
Copy link

Chupaka commented Jan 19, 2021

Hello.

I'm solving a problem with hosting Home Assistant instance in a cloud. As multicast is not supported on the way there, I convert multicast packets to unicast on my home router (by using DST-NAT) and send them to Home Assistant server via PPP link.

The problem is that on server side, simply converting destination address back to multicast one (224.0.0.50) is not working for Home Assistant to actually receive the packet, so the only solution I found is binding the socket not to the multicast address (224.0.0.50) but to 0.0.0.0 using sock.bind(('', port)) (which is default for Windows and a fallback for other cases) instead of sock.bind((MULTICAST_ADDRESS, port)).

What are the pros (like "working gateway pushes over non-multicast networks") and cons of binding to 0.0.0.0 instead of 224.0.0.50? I'd like to upstream a solution for this use case, as a friend of mine also faced this problem previously.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant