Revision history [back]

Hi there,

I have an embedded target connected directly into the PC using ethernet cable. Target's IP: 10.0.0.62 PC's IP: 10.0.0.99 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.

Hi there,

I have an embedded target connected directly into the PC using ethernet cable. Target's IP: 10.0.0.62 PC's IP: 10.0.0.99 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.

Hi there,

I have an embedded target connected directly into the PC using ethernet cable. Target's IP: 10.0.0.62 PC's IP: 10.0.0.99 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!).

Hi there,

I have an embedded target connected directly into the PC using ethernet cable. Target's IP: 10.0.0.62 PC's IP: 10.0.0.99 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!).