Ethereal-users: NET-SNMP problems was: [Ethereal-users] Re: unsupported Ethernet type 10
EXT / SITICOM KURZWEG wrote:
<Yes, you've got it! MIBDIRS is indeed set by some NM software I'm using on
<that machine. Ethereal 0.9.8 works fine when called from within a batch that
<reset this variable.
Good that you got around the problem. However not good that Ethereal crashes when net-snmp
has problems parsing some mib-files or similar.
But I'm anyway happy that net-snmp support is included in the Windows binary now from
Ethereal version 0.9.8. I have been using Ethereal 0.9.1 sometimes for looking at SNMP captures.
The file I had problem was the Diffserv-PIB (PIB converted to MIB) from the following message, and
another mib-file that seems to be corrupt.
http://www.ethereal.com/lists/ethereal-dev/200202/msg00272.html
I had the same mib-files in /usr/mibs/ when using Ethereal 0.9.1 (with ucd-snmp)
and then I didn't notice any problems.
With Ethereal 0.9.8 I got a crash on Windows 98:
ETHEREAL orsakade ett ogiltigt sidfel i (page fault in module ETHEREAL.EXE on address 015f:0067314c)
modul ETHEREAL.EXE på adress 015f:0067314c.
Registrerar:
EAX=00000010 CS=015f EIP=0067314c EFLGS=00010202
EBX=00000010 SS=0167 ESP=00e8f87c EBP=78010c0e
ECX=ffffffff DS=0167 ESI=00974174 FS=4cd7
EDX=00ea03d0 ES=0167 EDI=00000001 GS=0000
Byte på CS:EIP:
80 3b 00 74 73 53 e8 d9 f9 ff ff 83 e0 7f 83 c4
Stackdump:
00000001 00974174 78010c0e 7802650e 0067358e 00000010 ffffffff 00fb9b60 00000000 00fb9b3c bff7cf27 81794c40 bff7ffc5 81794c40 81794c40 bff80276
Seems to be same address in your case (0067314c).
On Windows 2000 nothing seems to happen when I double clicked on the Ethereal icon.
No GUI appears. I notice in Task Manager that ethereal.exe process is there. It seems Ethereal is hanging during startup.
I will try to look into this later this week and if it seems to be a problem with net-snmp I will
report it to http://sourceforge.net/projects/net-snmp/. I noticed that there seemed to be a couple of messages
about looping for ever for certain MIBs or similar, so it may be a problem that already has been reported.
