You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in sockets using PacketBuffer (udp, icmp, raw) the receive path calls dequeue_padding() before doing the actual recieve. However, can_recv() doesn't do so, which means it's possible it returns true but then actually trying to receive yields no received data.
The text was updated successfully, but these errors were encountered:
@Dirbaio have you found a solution to that problem yet? It persists into the 0.12.0 version. Would be much appreciated if you could share a workaround.
What doesn't click with me is the second sentence, the recv does not yield data even though it is calling dequeue_padding() internally. So the issue is not with the RingBuffer, but with the interface?
in sockets using PacketBuffer (udp, icmp, raw) the receive path calls
dequeue_padding()
before doing the actual recieve. However,can_recv()
doesn't do so, which means it's possible it returnstrue
but then actually trying to receive yields no received data.The text was updated successfully, but these errors were encountered: