Hi All,
I've found the solution and wanted to share it for future reference.
It turned out that the device which was sending the broadcast had a
different netmask than the receiving device.
This difference in netmask resulted in a wrong calculated broadcast ip.
Wire Shark displays this,
Hi All,
I'm currently at a customer site and I need to receive data sent with
UDP broadcast.
I've done this quite often without problems, but at the moment I have a
problem of which I'm not sure where to look.
(As always) I've set up my receiving socket like this:
fUDPServer :=
And yes, I've disabled the auto responder :) sorry for that...
Merijn
On 6/21/2010 17:11, Merijn Bosma wrote:
Hi Agnus,
Thanks for the fast reply. The Wire Shark log line is about data sent
by somebody else to me, I didn't send it myself.
Merijn
On 6/22/2010 17:07, Angus Robertson -
Hi Agnus,
Thanks for the fast reply. The Wire Shark log line is about data sent by
somebody else to me, I didn't send it myself.
Merijn
On 6/22/2010 17:07, Angus Robertson - Magenta Systems Ltd wrote:
Here a log line of Wire Shark in which you can see Wire Shark does
receive this data: 564
