Hi,
Thanks for the illustrative capture files. There's nothing better then to have
that, so that we can look straight at the problem.
I've used them to open an issue here:
https://gitlab.com/wireshark/wireshark/-/issues/17868 which I can use to
resolve the problem.
Thanks,
Jaap
> Op
Hi Jaap,
Thanks for your response.
Please find the attached wireshark capture for "multiple FEC stack change
TLV" and "FEC stack change with Target FEC TLV" not decoded properly.
Also the bytes sent in mail below are complete encapsulation with all
headers and those bytes can be directly copied
Hi,
The immediate response by Alexis was to open an issue on the Wireshark issue
tracker.
My response would be to attach a small sample capture file with the packets,
instead of some bytes or screenshot to the email.
Can you do either of those?
Jaap
> On 6 Jan 2022, at 06:31, max payne..
Hi Team,
I have not got the resolution for the issue below.
This was the link provided to me.
https://www.wireshark.org/mailman/confirm/wireshark
-dev/d4b89dd02f824a954e2e3ffa37151bf0f7ebacbc
On Fri, Dec 3, 2021 at 12:27 AM max payne..
wrote:
> Hi,
>
> This is to inform you that we are
Hi,
Can you open an issue on wireshark gitlab ? With pcap file and link to spec.
Cheers
Le ven. 3 déc. 2021 à 17:26, max payne.. a
écrit :
> Hi,
>
> This is to inform you that we are supporting FEC Stack Change Sub-TLV in
> DDMAP TLV. I have Hex Dump, which is correct as per my understanding
Hi,
This is to inform you that we are supporting FEC Stack Change Sub-TLV in
DDMAP TLV. I have Hex Dump, which is correct as per my understanding but it
is not getting decoded on Wireshark or Online Decoder.
Please let me know if the latest Wireshark "Version 3.6.0
(v3.6.0-0-g3a34e44d02c9)"
