Wireshark · Wireshark-commits: [Wireshark-commits] master-2.4 322cc03: Once we've identified a TCP segment as rpcap, use rpcap for

[Wireshark code review <code-review-do-not-reply@xxxxxxxxxxxxx>]

URL: https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=322cc03b9ca0533a5542d2d2f8f9d12f122ae7fa
Submitter: "Guy Harris <guy@xxxxxxxxxxxx>"
Changed: branch: master-2.4
Repository: wireshark

Commits:

322cc03 by Guy Harris (guy@xxxxxxxxxxxx):

    Once we've identified a TCP segment as rpcap, use rpcap for the connection.
    
    One reason to use Wireshark is to diagnose protocol errors, so don't,
    for example, treat too-short packets, in a TCP connection where we've
    already seen rpcap packets, as not being rpcap packets.  (Yes, that *is*
    a bug, in the libpcap master, that I found and fixed.)
    
    Change-Id: I9a81e5b9a2910331574164395302247a446e805b
    Reviewed-on: https://code.wireshark.org/review/31809
    Reviewed-by: Guy Harris <guy@xxxxxxxxxxxx>
    (cherry picked from commit d58a3ffe4f69366f25fd192e41a89b4769c7d22c)
    Reviewed-on: https://code.wireshark.org/review/31811
    

Actions performed:

    from  1011d68   Further improve that error message.
     add  322cc03   Once we've identified a TCP segment as rpcap, use rpcap for the connection.


Summary of changes:
 epan/dissectors/packet-rpcap.c | 22 +++++++++++++++++++++-
 1 file changed, 21 insertions(+), 1 deletion(-)