forked from Minki/linux
l2tp: fix data packet sequence number handling
If enabled, L2TP data packets have sequence numbers which a receiver can use to drop out of sequence frames or try to reorder them. The first frame has sequence number 0, but the L2TP code currently expects it to be 1. This results in the first data frame being handled as out of sequence. This one-line patch fixes the problem. Signed-off-by: James Chapman <jchapman@katalix.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
38d40b3f4e
commit
d301e32568
@ -1762,7 +1762,7 @@ struct l2tp_session *l2tp_session_create(int priv_size, struct l2tp_tunnel *tunn
|
||||
|
||||
session->session_id = session_id;
|
||||
session->peer_session_id = peer_session_id;
|
||||
session->nr = 1;
|
||||
session->nr = 0;
|
||||
|
||||
sprintf(&session->name[0], "sess %u/%u",
|
||||
tunnel->tunnel_id, session->session_id);
|
||||
|
Loading…
Reference in New Issue
Block a user