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
Describe the bug need_notify_loss in CUDT::processData() will be set to false for the first received packet (because the group recv state is transiting to RUNNING).
To Reproduce
Callers broadcast inorder messages to receivers.
The first packet is dropped by iptable.
The following packets are received and the receiver ack with largest_received_seq+1 since the first lost packet is ignored by !need_notify_loss.
Group::recv() fail to read a inorder message since the first packet is lost forever.
Expected behavior
I know that if TLPKTDROP is enabled, it should be fine, but in message mode, all lost packets with TTL=-1 should not be ignored.
gou4shi1
changed the title
[BUG] initial lost packets may be ignored in group message mode
[BUG] Initially lost packets may be ignored in group message mode
Jan 27, 2022
Describe the bug
need_notify_loss
inCUDT::processData()
will be set tofalse
for the first received packet (because the group recv state is transiting to RUNNING).To Reproduce
iptable
.!need_notify_loss
.Group::recv()
fail to read a inorder message since the first packet is lost forever.Expected behavior
I know that if
TLPKTDROP
is enabled, it should be fine, but in message mode, all lost packets withTTL=-1
should not be ignored.Desktop:
The text was updated successfully, but these errors were encountered: