MIBS error on launch on OSX

This issue was migrated from bug 3163 in our old bug tracker.

Original bug information:

Reporter: Michael Revees
Status: RESOLVED FIXED
Product: Wireshark
Component: Extras
OS: Mac OS X 10.5
Platform: All
Version: 1.0.6

Michael Revees said:

Build Information: Version 1.0.5 (SVN Rev 26954)

Copyright 1998-2008 Gerald Combs <gerald@‍wireshark.org> and contributors. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.12.9, with GLib 2.16.3, with libpcap 0.9.5, with libz 1.2.3, without POSIX capabilities, with libpcre 7.8, with SMI 0.4.8, without ADNS, without Lua, with GnuTLS 2.6.2, with Gcrypt 1.4.3, with MIT Kerberos, with PortAudio V19-devel (built Nov 14 2008), without AirPcap.

Running on Darwin 9.6.0, with libpcap version 0.9.5.

Built using gcc 4.0.1 (Apple Inc. build 5488).

---

I am getting the following error on launch. Which did not appear in 1.0.4

The following errors were found while loading the MIBS:
-:0 1 module-not-found failed to locate MIB module `IP-MIB'
-:0 1 module-not-found failed to locate MIB module `IF-MIB'
-:0 1 module-not-found failed to locate MIB module `TCP-MIB'
-:0 1 module-not-found failed to locate MIB module `UDP-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMPv2-MIB'
-:0 1 module-not-found failed to locate MIB module `RFC1213-MIB'
-:0 1 module-not-found failed to locate MIB module `IPV6-ICMP-MIB'
-:0 1 module-not-found failed to locate MIB module `IPV6-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-COMMUNITY-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-FRAMEWORK-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-MPD-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-NOTIFICATION-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-PROXY-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-TARGET-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-USER-BASED-SM-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-USM-DH-OBJECTS-MIB'
-:0 1 module-not-found failed to locate MIB module `SNMP-VIEW-BASED-ACM-MIB'

The Current Path is: /usr/local/share/mibs/ietf:/usr/local/share/mibs/iana:/usr/local/share/mibs/irtf:/usr/local/share/mibs/site:/usr/local/share/mibs/tubs:/usr/local/share/pibs/ietf:/usr/local/share/pibs/site:/usr/local/share/pibs/tubs

SNMP is not installed on my machine because I have no need for it. Based on what I've read elsewhere I believe this is the root cause. The error does not otherwise affect wireshark.

added cliother osmacos version1.0 labels

Martin Cleaver said:

I get this error as well, on 10.5.6.

And then I can't capture because there are no interfaces available.

As this bug stops me from using Wireshark I've upped the Priority to High.

Jeff Morriss said:

(In reply to #3163 (comment 400634917))

I get this error as well, on 10.5.6.

And then I can't capture because there are no interfaces available.

As this bug stops me from using Wireshark I've upped the Priority to High.

Wireshark not being able to find the MIBs won't stop you from capturing or otherwise using Wireshark. You must be experiencing a different problem. I'd suggest first checking:

http://wiki.wireshark.org/CaptureSetup

and if that doesn't help then ask one of the lists for ideas why you can't capture.

Jeff Morriss said:

I had noticed the same error a while back when not installing the MIBs on Windows:

http://www.wireshark.org/lists/wireshark-dev/200711/msg00249.html

I'm still not sure what to do about it, though.

tom said:

I am also expiriencing the same problem at Leopard 10.5.6 / Intel. Development Release 1.1.2 also does not fix this bug. It should be CRITICAL / MAJOR, because I can't use Wireshark anyway - no ethernet/wireless interfaces are listed!!

Jaap Keuter said:

As this problem does not cause interference with the capability to capture this the priority/severity does not need to be raised. Please review comment #2 on this issue.

Hans said:

I too am having this issue. I had wireshark working until I did an OS reinstall, and downloaded the new version. This is a fresh install of OS X 10.5.6, and I've tried both the experimental and stable versions. They both come up with the same error, and neither lists any available interfaces.

Dan Hale said:

I had the same issue loading MIBS. I did some hunting around online, and found a link addressing the purpose of SNMP, MIBS, etc. It seems that the directory where these are stored is actually /usr/share/snmp/mibs/ , not the default path that the program is searching. Open the Name Resolution section under preferences and add the above directory to SMI (MIB and PIB) paths.

That will fix the loading error (hopefully), but like you, my interface is not being recognized. If I get that figured out, I'll see if I can send some info your way, since our systems seem to be suffering the same symptoms.

Dan

Hans said:

(In reply to #3163 (comment 400634964))

I had the same issue loading MIBS. I did some hunting around online, and found a link addressing the purpose of SNMP, MIBS, etc. It seems that the directory where these are stored is actually /usr/share/snmp/mibs/ , not the default path that the program is searching. Open the Name Resolution section under preferences and add the above directory to SMI (MIB and PIB) paths.

That will fix the loading error (hopefully), but like you, my interface is not being recognized. If I get that figured out, I'll see if I can send some info your way, since our systems seem to be suffering the same symptoms.

Dan

Thanks Dan. That certainly resolved one issue. The more pressing issue now, just as you have stated, is that the interfaces are not listed. The program is completely unusable until that is resolved, so I'm very curious to see what you come up with.

Dan Hale said:

Well, I should have just waited and put both of these together. Now that you've got MIBS running, try this command in the terminal: sudo chmod go+r /dev/bpf* It's an issue with the bpf permissions, which I thought I knew from reading the support documents, but most of them were about as clear as mud and didn't help me get it working. The above command may not work if you don't have administrator privileges, but you'd have to ask someone who knows a bit more than I do if you want to be sure. Here's the link to the page where I found this, which also has the CHModBPF script that can run on startup. http://blog.nominet.org.uk/tech/2008/04/30/wireshark-capture-under-mac-os-x/

Dan

Hans said:

(In reply to #3163 (comment 400634976))

Well, I should have just waited and put both of these together. Now that you've got MIBS running, try this command in the terminal: sudo chmod go+r /dev/bpf* It's an issue with the bpf permissions, which I thought I knew from reading the support documents, but most of them were about as clear as mud and didn't help me get it working. The above command may not work if you don't have administrator privileges, but you'd have to ask someone who knows a bit more than I do if you want to be sure. Here's the link to the page where I found this, which also has the CHModBPF script that can run on startup. http://blog.nominet.org.uk/tech/2008/04/30/wireshark-capture-under-mac-os-x/

Dan

Dan, you are a gentleman and a scholar. That worked flawlessly! I wonder why this issue existed in the first place though? No matter, this was perfect. Thanks a lot!

Dan Hale said:

(In reply to #3163 (comment 400634984))

Glad it's working for you too, but I don't know why it's an issue either. I'm guessing that the MIBS directory changed in one of the Mac OS revisions and hasn't been changed in the program to reflect the update (I'm also working off of a fresh install). I don't know why the command to alter bpf permissions is so hard to find in the support documents, a situation I find more puzzling than the startup error.

Dan

Jeff Morriss said:

As previously mentioned (and now confirmed through Hans' and Dan's comments), this bug has nothing to do with not being able to see any capture devices on MacOS.

Putting the Severity and Priority back down where they belong.

Jeff Morriss said:

*** Bug #3251 (closed) has been marked as a duplicate of this bug. ***

Jason Duell said:

Unless I'm mistaken, there's still a bug here: As mentioned in #3163 (comment 400634964), OSX now stores some MIBS files in

/usr/share/snmp/mibs/

which is still not in wireshark's default search path. (I just upgraded to 1.0.6).

As a result, I assume all (?) OSX users are getting these "failed to locate MIB module" messages at startup. No, they're not fatal, but they're irritating, and this should be a one-line fix.

I've verified that adding "/usr/share/snmp/mibs/" to the "SMI (MIB and PIB) paths" settings makes this go away on my machine, at least.

rasz said:

samo on windows (XP SP3) with 1.0.6
VERY annoying, I have to see this bug and press ok every time i want to use wireshark

Jeff Morriss said:

(In reply to #3163 (comment 400635016))

samo on windows (XP SP3) with 1.0.6
VERY annoying, I have to see this bug and press ok every time i want to use wireshark

This bug does NOT apply to Windows. The problem here (I think) is that the default MIBs search path is wrong on MacOS.

On Windows the problem is that if you choose (at install time) not to install the MIBs then Wireshark gives errors about the "missing" MIBs. You might want to open a separate bug about that if it bugs you.

rasz said:

(In reply to #3163 (comment 400635026))

This bug does NOT apply to Windows. The problem here (I think) is that the default MIBs search path is wrong on MacOS.

On Windows the problem is that if you choose (at install time) not to install the MIBs then Wireshark gives errors about the "missing" MIBs. You might want to open a separate bug about that if it bugs you.

bug name is "MIBS error on launch 1.0.5", description doesnt say anything about wrong patch, in fact submitter said he didnt install MIBS at all.

Michael Revees said:

I didn't explicitly install it but changing the default search path does fix it in OS 10.5 as it comes with MIBS.