Custom NSE NNF Wireshark Dissector

@debianguy

Hello, I've built parsers and tooling around custom binary protocols, so the Wireshark side of this project is familiar territory. I understand the goal is to decode NSE NNF packets, expose all header/payload fields in Wireshark, and support display filters such as nnf.msg_type == 0x12. I can implement the dissector in Lua, C/C++, or Rust depending on the protocol complexity and maintenance requirements. Before confirming the approach, I'd like to review the protocol specification and a few sample traces. One important question: does the specification fully define all message layouts and field structures, or is any part of the protocol expected to be reverse-engineered from packet captures? Once I review the spec, I can recommend the best architecture and provide an accurate timeline. Regards

@extreamcode

Hi, There’s a hidden complexity here: the hardest part isn’t parsing packets, it’s making every NNF field genuinely usable in Wireshark filters and future upgrades. I can build the dissector in Lua or C/C++ depending on how the protocol nesting and reassembly behave; for clean maintenance, I’ll first map whether it should register under IP/TCP or remain a standalone plugin, then structure the fields so nnf.msg_type-style filters work naturally in the details pane. I’ve worked on Linux-based protocol tooling and software development tasks where decoding accuracy, field hierarchy, and stable plugin loading mattered more than just making it compile. I’ll deliver commented source, a Windows/Linux-ready build, a sample capture, and a short README with rebuild steps and usage notes. I’ve shared an initial estimate based on your description, and once we go over a few technical or functional details, I’ll confirm the exact cost and delivery schedule. I can start as soon as you share the spec and traces, and I’ll confirm the best implementation path after reviewing message framing and any TCP segmentation concerns. Does NSE NNF run strictly over TCP/IP, or do you need the dissector to handle any segmentation or encapsulation edge cases? Please send the protocol spec and a few representative captures so I can confirm the decoding model. Best regards, Asad

@mohjib092

Hi there, Expert here, I can build a Wireshark dissector for your proprietary NSE NNF protocol with full header/payload decoding, hierarchical field display, and filterable fields such as `nnf.msg_type == 0x12`. I can guide the best architecture after reviewing the spec, but for fast delivery and easier maintenance I’d likely start with Lua unless performance or deep integration requires C/C++. I’ll include commented source code, Windows/Linux build or install steps, sample decoded capture, and a clear README. Best Regards, Muhammad Jibran Ahmed

@Hrolgar

NNF's message-type dispatch is what needs to be nailed first. Each message type carries a different field layout after the common header, so the dissector has to branch cleanly on that type byte rather than applying a flat decode that works for one message class and silently misaligns everything else. Starting in Lua makes sense here, faster to iterate against live captures when you're confirming field offsets, no recompile loop. The build is a decode table covering every header field from the spec (offset, length, type, display label), with per-message-type subtrees for the payload section. For any fields where throughput matters under high-feed load, specific sections can be ported to a C plugin without changing the rest. What you'd get: complete Lua dissector and field mapping table for all NNF header fields and message types, ready to install directly into Wireshark's plugin directory. 32,000 INR, 4 days. Do you have a sample NNF capture handy, or just the spec doc?

@sjohn117

Hi,\n\nI’m Sean, an AI & Full-Stack Developer with over 10 years of experience, specializing in C/C++ and software development. I understand that you need a Wireshark dissector for the proprietary NSE NNF protocol, which requires intricate decoding of header and payload fields to allow for easy filtering and analysis.\n\nI have successfully implemented similar projects where I developed dissectors that seamlessly integrated with existing architectures. Based on your requirements, I recommend a standalone plugin to ensure ease of maintenance and compatibility with future Wireshark upgrades.\n\nI will ensure that the code is clean, well-commented, and includes detailed instructions for building on both Windows and Linux. Deliverables will include the compiled .dll/.so file, sample captures, and a README for ease of use and understanding. I estimate a realistic turnaround time of one week for the initial version. What are your thoughts on a standalone plugin versus integration with existing dissectors for maintenance? \n\nThanks,\nSean

@kamild89

I'm a C++ engineer with a trading background, so I'll understand what the fields actually mean, not just parse bytes blindly. On architecture I would recommend registering under the existing TCP dissector. It seems more natural and easier to maintain across Wireshark upgrades I'll deliver commented source, compiled plugin for Windows and Linux, sample capture and README. Estimated delivery time: 5-6 days