[IPP] MIB construction information

[Paul Santangelo]

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 <tel:800-825-5664>
Visit us: Count on Konica Minolta <http://www.countonkonicaminolta.com/>
<http://www.facebook.com/konicaminoltaus> 
<http://www.twitter.com/konicaminoltaus> 
<https://plus.google.com/u/0/101069343240482341568/about> 
<http://www.linkedin.com/companies/4830> 
<http://www.youtube.com/user/konicaminoltaus> 
<http://www.pinterest.com/konicaminoltaus>
Disclaimer 
<http://kmbs.konicaminolta.us/signature/KMBSUS-Disclaimer%20.png>


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 
> <mailto: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 <tel:800-825-5664>
>> Visit us: Count on Konica Minolta <http://www.countonkonicaminolta.com/>
>> <http://www.facebook.com/konicaminoltaus> 
>> <http://www.twitter.com/konicaminoltaus> 
>> <https://plus.google.com/u/0/101069343240482341568/about> 
>> <http://www.linkedin.com/companies/4830> 
>> <http://www.youtube.com/user/konicaminoltaus> 
>> <http://www.pinterest.com/konicaminoltaus>
>> Disclaimer 
>> <http://kmbs.konicaminolta.us/signature/KMBSUS-Disclaimer%20.png>
>>
>>
>> _______________________________________________
>> ipp mailing list
>> ipp at pwg.org <mailto:ipp at pwg.org>
>> https://www.pwg.org/mailman/listinfo/ipp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190510/a17984f7/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: amfkllakpmeckmnp.png
Type: image/png
Size: 10571 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190510/a17984f7/attachment.png>