The built-in fixed broadcast address public static final String SERVER_SEARCH = "239.0.0.1"; does not work reliably. I propose to use the following method to find the broadcast address: private InetAddress getBroadcastAddress() { try { for (NetworkInterface ni : Collections.list(NetworkInterface.getNetworkInterfaces())) { if (ni.isUp()) { for (InterfaceAddress addr : ni.getInterfaceAddresses()) { if (!addr.getAddress().isLoopbackAddress()) { return addr.getBroadcast(); } } } } } catch (SocketException ex) { // ignore } throw new RuntimeException("no broadcast address found"); } In the class "TcpServersFinder" the method buildSearchPacket could use this method: private DatagramPacket buildSearchPacket() { String aSearchCommand = Protocol.Commands .prepareCommand(Protocol.Commands.SEARCH_SERVERS); DatagramPacket aSearchPacket = new DatagramPacket( aSearchCommand.getBytes(), aSearchCommand.length()); aSearchPacket.setAddress(getBroadcastAddress()); aSearchPacket.setPort(Protocol.Ports.SERVER_SEARCH); return aSearchPacket; }
This solution is also not fully working: the broadcast should be sent to all network interfaces. I tried the following: - connect computer to android via mobile hotspot If the android is also connected to the internet via the mobile network then the broadcast is sent to the mobile network (where it is suppressed). If the mobile network ob the android is disabled, then the connected computer is found.
Could you please create a patch a submit it to gerrit as explained here https://wiki.documentfoundation.org/Development/gerrit/SubmitPatch ?
Creating a patch is possible. Maybe we should first discuss the options: * current solution uses multicast (seems to have problems in some networks, e.g. mobile hotspot) * my solution uses some API call to get a broadcast address For me it is not clear if my solution is really better.
Could you please then write an email to the dev mailing list ? https://wiki.documentfoundation.org/Development/Mailing_List
Hi Michael, Any update here?
(In reply to Xisco Faulí from comment #4) > Could you please then write an email to the dev mailing list ? > https://wiki.documentfoundation.org/Development/Mailing_List Hi Michael Mehl, have you sent the email to the dev list in order to get the topic discussed?
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping-20181105
Dear Bug Submitter, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-20181203