-
Notifications
You must be signed in to change notification settings - Fork 94
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
When bound to an IP, LAN broadcasts are no longer recieved #71
Comments
I think an enhancement to RakNetServer::bindInternal to recognize when binding to a specific IP, instead of 0.0.0.0 (i.e. bind all), and including that IP's broadcast IP in channelFutures[]. This would potentially require a thread to handle the one additional broadcast IP. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As per a discussion in Discord when the BedrockServer is bound to an IP instead of 0.0.0.0 it will no longer see broadcast packets and thus not pick up on LAN broadcasts.
A possible solution is to bind to 0.0.0.0 using a MulticastSocket (as opposed to a DatagramSocket) which allows multiple listeners which will receive all broadcast traffic when a specific IP is set in addition to the IP to receive unicast traffic.
The text was updated successfully, but these errors were encountered: