search

tradle / react-native-udp

node's dgram for react-native
MIT License
340 stars 155 forks source link

How to acquire MulticastLock when listening for broadcasted UDP messages? #253

Open paulwellnerbou opened 7 months ago

paulwellnerbou commented 7 months ago

We use this project to listen for broadcasted UDP messages. Those UDP messages are broadcasted to the whole network (using 255.255.255.255 IP mask.

For some Android devices, this works fine, for others it does not. I created a blank native App to analyse this problem further, and it seems that it works, when the MulticastLock is acquired.

I scanned the source code, it seems that the MulticastLock is acquired when adding a membership.

But I did not find out how to use this, and how to add a membership as a UDP listening App. Which multicastAddress I am supposed to put there?

Do you have an example or some hints how to do this? Is this already implemented in 4.1.7?

github-actions[bot] commented 6 months ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

paulwellnerbou commented 6 months ago

This is still pending, and it would be great to get a response.

github-actions[bot] commented 5 months ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

paulwellnerbou commented 5 months ago

I would still love to get some feedback about this.

github-actions[bot] commented 4 months ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

paulwellnerbou commented 4 months ago

I would still love to get some feedback about this.

github-actions[bot] commented 2 months ago

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

paulwellnerbou commented 2 months ago

I would still love to get some feedback about this.