Problem with Wireshark

Question

Level 1

0 points

Problem with Wireshark

I have just installed Wireshark 1.2 on my MacBook Pro 10.5.7 Leopard. Whenever I open the Wireshark, it would prompt out below error messages aboiut a lot of MIB module not found. It also showed what the current path is, but when I execute "echo $PATH", it does not match with what the error message window showed "The Current Path is".

How should I configure Wireshark so that it would not prompt such error message?

Message was edited by: boycemac

mac book pro, Mac OS X (10.5.7)

Posted on Jul 7, 2009 9:33 AM

Reply

Answer 1

boycemac Author

Level 1

0 points

Jul 7, 2009 9:39 AM in response to boycemac

When I execute Wireshark on Terminal, it would have below error output from Terminal.

bash-3.2# echo $PATH
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
bash-3.2# wireshark &
[1] 634
bash-3.2# 2009-07-08 00:36:15.399 defaults[644:10b]
The domain/default pair of (kCFPreferencesAnyApplication, AppleAquaColorVariant) does not exist
2009-07-08 00:36:15.409 defaults[645:10b]
The domain/default pair of (kCFPreferencesAnyApplication, AppleHighlightColor) does not exist

(process:634): Gdk-WARNING **: locale not supported by C library

(wireshark-bin:634): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.

(wireshark-bin:634): Gtk-WARNING **: Unable to locate theme engine in module_path: "clearlooks",

(wireshark-bin:634): Pango-WARNING **: Error loading GDEF table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GSUB table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GPOS table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GDEF table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GSUB table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GPOS table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GDEF table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GSUB table 28333

(wireshark-bin:634): Pango-WARNING **: Error loading GPOS table 28333

If I ignore this error, it looks like the Wireshark can work as expected to capture packet, but I look forward to get rid of this error message.

Reply

Answer 2

cb0

Level 1

0 points

Aug 5, 2009 6:59 PM in response to boycemac

First of all, the path that wireshark is referring to (in "Current Path is") is not the same path as you get from echo $PATH

The MIB modules are probably on your computer, but they are not in the place wireshark is looking.

On my system the MIBs are in /usr/share/snmp/mibs/IP-MIB.txt --- for example

You can fix this problem by doing an ln -s to establish the directory where ws is looking and point it to the directory(ies) where the MIBs actually live (be careful not to wipe out any existing directories/files when you do this).

Suggest you fix this problem then attack your other problems, which look more serious. But if you can't do the above, there's no sense in trying the harder problems.

Reply

Answer 3

boycemac Author

Level 1

0 points

Aug 12, 2009 10:50 PM in response to cb0

Thanks for your great assistance. I also noticed that my MacBook Pro stored all mibs files under "/usr/share/snmp/mibs" directory. Therefore, I go back to Wireshark and edit the Preference.

Under "Name Resolution", I click "Edit" button next to "SMI (MIB and PIB) paths for adding above directory as the path for Wireshark to search for MIBs.

It works finally without showing the error anymore when I start Wireshark.

Reply