wireshark won't capture udp packets without port binding [closed]

asked 2021-07-05 15:03:08 +0000

OrenS gravatar image

updated 2021-07-06 06:26:51 +0000

Hi there,

I have an embedded target connected directly into the PC using ethernet cable. Target's IP: PC's IP: The target is sending periodic UDP messages to destination port: 60000 every 1 sec.

Until not long ago, I've seen those messages in the Wireshark without binding to that specific port (60000) in the PC.

Now, when running Wireshark I don't see any UDP messages being captured unless I bind to that port using python \ packet sender \ ... (Don't even have to call receive but only bind). When I stop the listener program, I stop seeing new packets in the Wireshark.

I am not sure if it was caused by new policy in our company or new Wireshark version.

I'm using Windows 10, Wireshark version 3.4.2

Any idea how I can configure wireshark \ ethernet adapter to capture UDP packets even without binding to that specific port?

Thanks a lot! Oren.

EDIT: Problem solved - it seems that the symantec anti-virus was blocking ports that we are not binding (so even the wireshark won't show them!).

edit retag flag offensive reopen merge delete

Closed for the following reason the question is answered, right answer was accepted by Jaap
close date 2021-07-05 16:09:43.502175


Note that you can answer your own question.

And, if you've found the answer yourself, as is the case here, you should answer it, so that if anybody else is looking for an answer to a question like this, they can see that this question was answered. That's better than editing the question to put the answer there.

Guy Harris gravatar imageGuy Harris ( 2021-07-05 22:37:23 +0000 )edit

Thanks! The problem was caused by the anti-virus (symantec) which was blocking ports that we are not binding (so even the wireshark won't show them!).

If anyone encounters this issue - better check the antivirus \ filewall logs :)

OrenS gravatar imageOrenS ( 2021-07-06 06:25:28 +0000 )edit