07-20-2019, 08:09 PM
I guess no attachments are allowed. Basically, wire shark was reporting an exception due to a malformed packet: the second frame had unacceptably high length.
Now, with explicit binding to the default broadcast address, the shark is happy and I can see the message text on the wire. So, here comes PART II:
how do I catch this message on my LAN? I create another application (would be called a server side) with TIdUDPServer component and I bind it to that same
address and port. The applications reports an exception on start-up saying 'Could not bind socket. Address and port are already in use'. With 'netstat -q'
I do not see any UDP sockets bound/listening to/on that particular address:port combination. Please advise. Many thanks in advance. Boba TC.
Now, with explicit binding to the default broadcast address, the shark is happy and I can see the message text on the wire. So, here comes PART II:
how do I catch this message on my LAN? I create another application (would be called a server side) with TIdUDPServer component and I bind it to that same
address and port. The applications reports an exception on start-up saying 'Could not bind socket. Address and port are already in use'. With 'netstat -q'
I do not see any UDP sockets bound/listening to/on that particular address:port combination. Please advise. Many thanks in advance. Boba TC.