You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: