diff options
| author | James Chapman <jchapman@katalix.com> | 2013-07-02 20:28:59 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2013-07-02 16:33:24 -0700 |
| commit | 8a1631d588a39e826f4248e60310498d5266c6fa (patch) | |
| tree | d4bc90f912c4f54a3becf34c2d8a7f35d2c605c6 /COPYING | |
| parent | b6dc01a43aaca24e6e6928e24d9b37ba599f1e3c (diff) | |
| download | linux-stable-8a1631d588a39e826f4248e60310498d5266c6fa.tar.gz linux-stable-8a1631d588a39e826f4248e60310498d5266c6fa.tar.bz2 linux-stable-8a1631d588a39e826f4248e60310498d5266c6fa.zip | |
l2tp: make datapath sequence number support RFC-compliant
The L2TP datapath is not currently RFC-compliant when sequence numbers
are used in L2TP data packets. According to the L2TP RFC, any received
sequence number NR greater than or equal to the next expected NR is
acceptable, where the "greater than or equal to" test is determined by
the NR wrap point. This differs for L2TPv2 and L2TPv3, so add state in
the session context to hold the max NR value and the NR window size in
order to do the acceptable sequence number value check. These might be
configurable later, but for now we derive it from the tunnel L2TP
version, which determines the sequence number field size.
Signed-off-by: James Chapman <jchapman@katalix.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions