A builtin dissector please. I would recommend you to do a MR with a single
IE to start with to get early feedback and get a hang of the process rather
than a single large contribution that people would be reluctant to review.
Best regards
Anders

Den tis 15 juli 2025 15:37Lavanika Raghavan <lavanika2...@gmail.com> skrev:

> Hello Dev Team,
>
> I was wondering if you would like me to contribute my changes for the
> C-based dissector for Wireshark to support Juniper’s vendor-specific
> Information Elements (IEs) for the PFCP protocol -- as a plugin
> (plugins/epan) or as an in-built dissector (epan/dissectors/packet-pfcp.c).
> Any help here would be greatly appreciated!
>
> Thank you,
> Lavanika
>
> On Fri, Jul 11, 2025 at 11:23 AM Lavanika Raghavan <lavanika2...@gmail.com>
> wrote:
>
>> Thank you very much!
>>
>> Lavanika
>>
>> On Fri, Jul 11, 2025 at 10:57 AM Gilbert Ramirez <g...@alumni.rice.edu>
>> wrote:
>>
>>> Welcome!
>>>
>>> This is the place to start:
>>> https://www.wireshark.org/docs/wsdg_html_chunked/
>>>
>>> And specifically:
>>> https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html
>>>
>>> Gilbert
>>>
>>> On Fri, Jul 11, 2025 at 9:52 AM Lavanika Raghavan <
>>> lavanika2...@gmail.com> wrote:
>>>
>>>> Dear Wireshark Development Team,
>>>>
>>>> I hope this message finds you well.
>>>>
>>>> My name is Lavanika Srinivasaraghavan, and I am currently a Software
>>>> Engineering Intern at Juniper Networks Inc. As part of my internship
>>>> project, I am developing a C-based dissector for Wireshark to support
>>>> Juniper’s vendor-specific Information Elements (IEs) for the PFCP protocol,
>>>> based on TR-459 and internal extensions.
>>>>
>>>> I would like to contribute this work upstream to Wireshark to benefit
>>>> both Juniper and the broader community. I am reaching out to request
>>>> guidance on the process for contributing dissector code and any permissions
>>>> or prerequisites required to get started.
>>>>
>>>> As my internship concludes on *August 15*, I would greatly appreciate
>>>> it if I could get the necessary permissions and directions at the earliest,
>>>> so I can align my work with Wireshark’s contribution standards and
>>>> timelines.
>>>>
>>>> Looking forward to your guidance on:
>>>>
>>>>    -
>>>>
>>>>    Steps to begin contributing the dissector code
>>>>    -
>>>>
>>>>    Any documentation or contribution guidelines to follow
>>>>    -
>>>>
>>>>    Review or submission process for protocol dissectors
>>>>
>>>> Thank you for your time and support.
>>>>
>>>> Best regards,
>>>> Lavanika Srinivasaraghavan
>>>>
>>>>
>>>> _______________________________________________
>>>> Wireshark-dev mailing list -- wireshark-dev@wireshark.org
>>>> To unsubscribe send an email to wireshark-dev-le...@wireshark.org
>>>>
>>> _______________________________________________
>>> Wireshark-dev mailing list -- wireshark-dev@wireshark.org
>>> To unsubscribe send an email to wireshark-dev-le...@wireshark.org
>>>
>> _______________________________________________
> Wireshark-dev mailing list -- wireshark-dev@wireshark.org
> To unsubscribe send an email to wireshark-dev-le...@wireshark.org
>
_______________________________________________
Wireshark-dev mailing list -- wireshark-dev@wireshark.org
To unsubscribe send an email to wireshark-dev-le...@wireshark.org

Reply via email to