I am writing a Qt (5.6) application that communicates with an FPGA over UDP socket. Packets are being streamed to the PC at 2 KHz (all packets identical size, 1272 bytes). Wireshark shows that packets are being sent, and the UDP header is as expected. The problem is, the Qt UDP Socket that I am using is never receiving these packets. The readyRead signal is never called.
Here is a code snippet:
UdpConnection::UdpConnection(QObject* parent)
{
fpgaConnection = QSharedPointer<QUdpSocket>(new QUdpSocket);
qDebug() << connect(fpgaConnection.data(), &QUdpSocket::readyRead, this, &UdpConnection::readyRead);
if (fpgaConnection->bind(QHostAddress("192.168.10.10"), 1920))
{
qDebug() << "Successfully Bound!";
}
else
{
qDebug() << "BINDING FAILURE";
}
fpgaConnection->connectToHost(QHostAddress("192.168.10.200"), 1919);
sendArpRequest();
}
void UdpConnection::readyRead()
{
while (fpgaConnection->hasPendingDatagrams())
{
QByteArray buffer;
buffer.resize(fpgaConnection->pendingDatagramSize());
QHostAddress sender;
quint16 senderPort;
fpgaConnection->readDatagram(buffer.data(), buffer.size(), &sender, &senderPort);
qDebug() << "Message from:" << sender;
qDebug() << "Message port:" << senderPort;
qDebug() << buffer;
}
}
Why is Wireshark able to see these messages, but my program is not?
UPDATE #1 Wireshark has the 2KHz packets as LLC packets. The Ethernet Header shows a correct Destination (my MAC address), Source Address (hard coded in the FPGA), and Length. The IP header has the Source IP as 192.168.10.200 and the Destination IP as 192.168.10.10, UDP Header has Source Port as 1920 and Destination Port as 1919.
UPDATE #2 Wireshark logs: paste.ee/p/98c1H As you can see, the packet is repeated and sent from the FPGA at 2KHz. The ARP transmission and reply can be found as the 5th, 10th, and 11th packet.
UPDATE #3 The IP packets of the incoming packets have a correct checksum that is NOT being set to 0x0000.
I'm not too familiar with Qt but for BSD socket API, I usually use bind to set my receive port but don't use connect for UDP connection especially when using different ports like your 1919 vs 1920 For socket API, use sendto() for sending packets with the target IP/port.
So, try commenting out connectToHost and directly use writeDatagram when sending.
The packet seems not to be a valid UDP Datagram.
Edit:
After fiddling with the packet it seem to be enough to change the type in the ethernet header to to IPv4 (0x0800).
It does show a strange TTL with a value of 0, but that may be sender related.
Original Post:
Instead of your current data you should send like this for having a valid datagram:
Ethernet Headers w/ IPv4 (14Byte): (as in your implementation, but type IPv4 0x0800), Source, Dest, Type
64006a493488 020826283900 0800
IPv4-Headers (20Byte): Version, Other, Size=1298(0512) UDP + 20, Ident, Flags(0x00), FlagOffset(0), TTL(128), Protocol(17 UDP), Checksum, Source = .10.200, Dest = .10.10
45 00 0512 31f0 00 00 80 11 0000 c0a80ac8 c0a80a0a
UDP-Header (8Byte): Source=1919, Dest=1920, Length=1278(04fe) = Data + 8, Checksum 2Byte NOT CALCULATED in example!!!
077f 0780 003e 9672
DataPayload: 1270 Byte of raw data
0a9f....
Using this as datagram you actually should not use connectToHost()
but use the writeDatagram()
and now probably working by signal invoked readyRead()
slot with hasPendingDatagrams()
and readDatagram()
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With