Yes Per it seems to be working ,
Thanks a lot.

Cheers
Anshul

Per,
Yeah , but other parsers are able to parse it. And I can see the issue being raised dating back to 2004, where you had mentioned that it has already been patched in mibble 2.3. Is there any other alternative, as I have to parse lot of files for all types of devices.

Cheers

Ans

I am using mibble 2.8, but there are still problems with the imports of certain symbols(IpAddress and Counter etc.). Have you patched it Per ?

In some cases it would be interesting to relax the semantical checks in Mibble. In particular this should be the case for very common mistakes like missing imports or similar.

One way to implement this would be to provide separate "relaxed" and "strict" parsing modes. In relaxed mode some errors would only be reported as warnings, whereas in the strict mode they would be seen as real errors. This separation is only possible in cases where error recovery can be made, however.

Regarding the missing symbols, error recovery would be possible by searching for the missing symbol in the already imported MIB:s. In most cases a missing import comes from one of the MIB:s already imported in the file (for other symbols). So it would be quite a simple extension to try to locate any missing import in one of those MIB:s. It is difficult to attempt reading other MIB files, as Mibble currently has no way of separating between SNMPv1 and SNMPv2 & v3 (see bug #4367).