Failed to connect to Host after Host DC

[Riksha]

Hi,

even though I could share data on LAN by searching directly for the IP, no member of the LAN was shown neither in the peertree nor in the webinterface.
The hello-messages were the same, so were broadcastadd and ip.
Broadcastadd has been changed to the first 9 numbers of the ip and an added 0.

After host A has left the LAN and then reconnected, noone could find him even when trying to connect to the ip. Host A could find everyone.

Restarting the "Client" Lanshark to host A made Host A reachable again.

[Jonas Wagner (veers)]

Are you sure the broadcast address was correct?
Ips ending with 0 are generally the "network numbers".
RFC 919 says:
   For example, 36.0.0.0 means "network number 36" while 36.255.255.255
   means "all hosts on network number 36".

Normally using 255.255.255.255 should just work and is the best way to do it.
Did you try that?

cheers!
Jonas

[Riksha (marshmallow7)]

Ah, that worked! Thank you
I replaced the 0 with a 255.
Sorry for reporting this "seemed-to-be-bug" problem here.
255.255.255.255 doesnt work in my situation.
Greets

[Jonas Wagner (veers)]

No worries! It's better to report a wrong bug than not to report a real bug!