Hello Paul,
It has been a while since I have worked with MIBs, and network management tools have apparently advanced a great deal since then. Although, as Paul indicated, Wireshark is used for monitoring network traffic, it appears that more recent versions also include the ability to decrypt encrypted SNMPV3 packets and a MIB complier that allows SNMP packets to be translated into human readable data.
MIB compilers have typically been inconsistent in how forgiving (or understanding) they are. However, when running a separate MIB compiler, they have typically been informative in what they don’t like. It is possible that the feedback in Wireshark is not as informative. I would suggest using a separate such as the one from MG-SOFT (although Ira may have some good suggestions for free compilers.
I do not quite understand what you did to get the error message below, but as you have probably have seen, the bug report you received reports “shows that it tries to read may MIBS and does not find them and then crashes”. This is quite possible since MIBs typically import other MIBs, and the whole set must be available to complete a compilation. So you must ensure that all imported MIBs (as well as those imported by the imported MIBs) are loaded.
Hope this helps.
Bill Wagner
From: Paul Santangelo via ipp
Sent: Friday, May 10, 2019 3:45 PM
To: Paul Tykodi
Cc: ipp at pwg.org
Subject: Re: [IPP] MIB construction information
Hey Paul:
Nice to hear from you again. I am trying to install our Private MIB into WireShark to decode the OID and Values.
After I submitted the email, I found one that looked very similar to others in the MIB folder under wireshark.
I moved the file over and named it properly as the name in the file and then added the filename to the SMI Modules.
I then relaunch Wireshark and get this error:
I am going back through the MIB to see what can be causing the error, but without a reference, I'm not sure that I will find it.
Regards,
PAUL SANTANGELO, CCNA, CNE
Escalation System Support (ESS) Integrator
Konica Minolta Business Solutions U.S.A., Inc.
101 Williams Drive Ramsey, NJ 07446
Office: 800-825-5664
Visit us: Count on Konica Minolta
Disclaimer
On 5/10/2019 3:29 PM, Paul Tykodi wrote:
Hi Paul,
IPP protocol alerts are harmonized with MIB functionality of PWG authored MIB RFC’s. Current versions of Wireshark recognize and can properly dissect IPP.
If you decide you have to go the MIB route, the communication to printer resident MIB’s is typically SNMP based. In my career, I have reviewed Wireshark traces of SNMP v1 and SNMP v2 network flows involving MIB communications with a printer and Wireshark captured the communication correctly.
I don’t believe I have ever reviewed an SNMP v3 trace though.
Best Regards,
/Paul
Sent from my iPhone
On May 10, 2019, at 2:06 PM, Paul Santangelo via ipp <ipp at pwg.org> wrote:
Hey All:
This is probably the wrong group to be writing to, but I saw the the Printer MIB Project is closed and support is through this IPP workgroup.
I'm trying to develop a MIB for our printers to be used with Wireshark. I saw some information online, but there really is not starting place, examples to follow. I'm am experienced enough to know how to read OID values and understand its hierarchy, but constructing the file so wireshark can read it, is weirding me out a bit.
Any help would be appreciated.
Thank you
--
Regards,
PAUL SANTANGELO, CCNA, CNE
Escalation System Support (ESS) Integrator
Konica Minolta Business Solutions U.S.A., Inc.
101 Williams Drive Ramsey, NJ 07446
Office: 800-825-5664
Visit us: Count on Konica Minolta
Disclaimer
_______________________________________________
ipp mailing list
ipp at pwg.orghttps://www.pwg.org/mailman/listinfo/ipp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190512/701adc5b/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6F0E4F4741ED4A1199ECFF0C5D8E9927.png
Type: image/png
Size: 10571 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190512/701adc5b/attachment.png>
