There also seems to be an issue with all MIB modules being listed twice
(IP-MIB ... FRAMEWORK-PIB, then the list repeats again), and if you try
to delete the duplicates or add your own MIB to the list, the changes
are not saved across Wireshark restarts. This is the behavior on
Windows at least.
-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Thomas Anders
Sent: Tuesday, August 28, 2007 6:56 AM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] smi_modules
Jaap Keuter wrote:
> I was thinking about Wireshark specific tags as well, but using
~/.smirc
> for that is probably wrong. Which $HOME should that be? It should go
in
> the global smi.config to have it available for everyone. Not sure I
like
> the idea of changing the global config.
> Their should be another way. Just not sure which.
There's also still the problem that wireshark needs to find out where
COPS-PR-SPPI et al. are actually located. Is this possible with libsmi?
Just blindly adding /usr/share/pibs (no matter how) doesn't feel right.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
-----------------------------------------
This email may contain confidential and privileged material for the
sole use of the intended recipient(s). Any review, use, retention,
distribution or disclosure by others is strictly prohibited. If you
are not the intended recipient (or authorized to receive for the
recipient), please contact the sender by reply email and delete all
copies of this message. Also, email is susceptible to data
corruption, interception, tampering, unauthorized amendment and
viruses. We only send and receive emails on the basis that we are
not liable for any such corruption, interception, tampering,
amendment or viruses or any consequence thereof.