Hello community support, I observe following strange but very real behaviour:
I have 5G SBI capture (so, basically JSON used for conveying protocol information which is another layer of weirdness but be it as it may) which was collected over several ports. For these ports "decode as" was set as JSON with TCP option "Analyze TCP Sequence numbers" on decode did not work -- just an undecoded payload stream was shown. With "Analyze TCP Sequence numbers" off -- [payload was correctly decoded as JSON. Why does this happen and what interdependency is there and why on these two functionalities ? Kind Regards Ariel Burbaickij
_______________________________________________ Wireshark-users mailing list -- wireshark-users@wireshark.org To unsubscribe send an email to wireshark-users-le...@wireshark.org
