Ok, now I understand. Mibble currently doesn't do this for you. It attempts to find the MIB file based on the file name, assuming that the MIB file and the MIB has the same name (minus any additional extension). It currently isn't "clever" enough to find MIB files based names that are only present inside the file.

I'm adding this to my todo-list for the next version of Mibble. I guess the solution will be to read the first couple of lines of text in each file in the MIB path and checking the module name inside the file. This search should only be performed for files with a certain extension, though, or things risk becoming very slow.

In the meantime the workaround for this is to preload the MIB file that will be imported. That is, in version 2.3 Mibble checks the module names of loaded MIB files, so if the imported MIB has already been loaded it will be localized correctly. So if you first load the imported MIB with the same MibLoader and then the MIB you really wanted to load, things should work out correctly. Otherwise you could also change the file name, as you pointed out.

Mibble already attempts to load MIB files regardless of the file extension (be it .mib, .txt or any other). It is, however, currently case-sensitive on platforms that support it (i.e Unix). That is, loaded files should normally be named in UPPER-CASE if the MIB name is specified in that way.

See the MibLoader.locate() and the MibFileFilter classes for more details on the implementation of this.