Hi, I'm trying to capture packets from my embedded board (IP 192.168.66.190, port 1025) using UDP. It's working fine in Windows XP, but it doesn't work in Windows 7. Wireshark is still able to detect the packets coming in, but there is nothing when a UDP listener is started on the same port. asked 10 Apr '13, 03:31 ktchiam |
3 Answers:
That's a Windows question really, since Wireshark is able to capture them. answered 10 Apr '13, 03:54 Jaap ♦ |
Try turning the Windows Firewall off. If that fixes the issue and you want the firewall back on (as you should do generally) then you'll need to add an exception to the firewall for your app to allow the UDP traffic in. answered 10 Apr '13, 04:19 grahamb ♦ |
Probably because the packets are somehow 'damaged' and windows drops them. Take a look at the IP stats of windows. Do the counters for 'errors' increase while you are seeing the packets in Wireshark, but not in your application?
Regards answered 10 Apr ‘13, 06:06 Kurt Knochner ♦ edited 10 Apr ‘13, 06:08 |
Sorry that it's kind of Windows related, but since Wireshark can capture the packets, may be someone would know why.
I've turned off the firewall, but it still doesn't work. I've also opened up another client to send UDP packets to 1025 and it can be received. It just won't receive packets coming from my ethernet port.
Wireshark, or to be technically accurate WinPCap, captures traffic in a very different manner than a normal app would receive it.
When you say you've opened up another client to send UDP packets and they are received, was that client on the same host as the listener app, or another host?
Does your app bind it's listener to the required IP address or does it listen on all?