latmmo.blogg.se

1. #WIRESHARK CAPTURE PACKETS FROM ONE APPLICATION DRIVERS#
2. #WIRESHARK CAPTURE PACKETS FROM ONE APPLICATION PC#

It's the same whether I'm talking to a Linux machine or a Win7 machine, neither OS likes my FPGA packets. I know my packets length is correct, firewall is off, checksums are correct, everything from a good PC-to-PC packet is identical in a FPGA-to-PC packet.

#WIRESHARK CAPTURE PACKETS FROM ONE APPLICATION PC#

I can take one of those packets, spoof it byte for byte in the FPGA, and the PC still drops it.

The weird thing is, I have an app for sending some dummy UDP packets from one PC to another, and those packets make it through. They show up in netstat as valid IPv4 packets, but not as valid UDP packets.

#WIRESHARK CAPTURE PACKETS FROM ONE APPLICATION DRIVERS#

However, for some reason, these packets are being rejected somewhere between the wireshark drivers and the application. Correct checksums, correct IP and MAC addresses, everything. Here's the problem: I'm sending UDP packets out at a rate of about 4 Mbit/sec, and they show up on wireshark on the PC side just fine. Up until now I've always used the WinPCAP libraries on the PC side to receive the data, but this time I need to be able to use the OS's network libraries. This isn't my first rodeo, I've been moving data this way on numerous projects for years, so I'm pretty familiar with the ethernet protocols and how the TSE works. It's a point to point connection, no switch involved. I'm on the Stratix IV Dev board, and I'm doing this by interfacing some custom logic directly with the TSE core (no NIOS, I'm not allowed to use that). I'm working on an application that takes data from a sensor, packetizes it into 1KB packets with the associated ethernet headers, and sends it to a PC via the TSE.