summaryrefslogtreecommitdiff
path: root/net/ipv4
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2013-07-02 16:33:31 -0700
committerDavid S. Miller <davem@davemloft.net>2013-07-02 16:33:31 -0700
commit784771e74b9207b0dd9e1f3b04729e6356c88650 (patch)
tree3f5187519c078bfa265654239854ab0a41597719 /net/ipv4
parent8a59bd3e9b296b93b905b5509c4ff540ee0e00bf (diff)
parenta0dbd822273ce7660bf35525d61d7a8ac5e679a3 (diff)
Merge branch 'l2tp_seq'
James Chapman says: ==================== L2TP data sequence numbers, if enabled, ensure in-order delivery. A receiver may reorder data packets, or simply drop out-of-sequence packets. If reordering is not enabled, the current implementation does not handle data packet loss correctly, which can result in a stalled L2TP session datapath as soon as the first packet is lost. Most L2TP users either disable sequence numbers or enable data packet reordering when sequence numbers are used to circumvent the issue. This patch series fixes the problem, and makes the L2TP sequence number handling RFC-compliant. v2 incorporates string format changes requested by sergei.shtylyov@cogentembedded.com. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4')
0 files changed, 0 insertions, 0 deletions