Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
UDP broadcast message fails
#7
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.
Reply


Messages In This Thread
UDP broadcast message fails - by Boba TC - 07-18-2019, 03:49 AM
RE: UDP broadcast message fails - by Boba TC - 07-18-2019, 05:51 PM
RE: UDP broadcast message fails - by rlebeau - 07-18-2019, 10:22 PM
RE: UDP broadcast message fails - by Boba TC - 07-19-2019, 02:26 AM
RE: UDP broadcast message fails - by rlebeau - 07-19-2019, 09:55 PM
RE: UDP broadcast message fails - by Boba TC - 07-20-2019, 02:08 AM
RE: UDP broadcast message fails - by Boba TC - 08-17-2019, 04:35 AM
RE: UDP broadcast message fails - by rlebeau - 08-17-2019, 07:22 AM
RE: UDP broadcast message fails - by Boba TC - 07-20-2019, 08:09 PM
RE: UDP broadcast message fails - by rlebeau - 07-23-2019, 09:35 PM
RE: UDP broadcast message fails - by Boba TC - 08-22-2019, 12:53 AM

Forum Jump:


Users browsing this thread: 3 Guest(s)