Libsmi November 2000

libsmi@ibr.cs.tu-bs.de

6 participants
11 discussions

question about trap oids
by Dan Stanger 14 Nov '00

14 Nov '00

i am sure that this question has been asked before, but i could not find any documentation on it. why does the trap oid have a 0 before the trap number? where is this added to the oid? thanks, dan stanger dan.stanger(a)ieee.org -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

Re: [libsmi] question about trap oids
by Frank Strauss 14 Nov '00

14 Nov '00

Dan> why does the trap oid have a 0 before the trap number? Dan> where is this added to the oid? This is done to ensure SMIv2 NOTIFICATION-TYPE definitions that can unabiguously be mapped to SNMPv1 trap identifications. See RFC 2578, Section 8.5. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

libsmi release 0.2.8
by Frank Strauss 13 Nov '00

13 Nov '00

Hi! Release 0.2.8... o introduces a new behavior of those smidump drivers that create multiple files (the internal driver interface has changed significantly), o reorganizes the test suite, and adds 5 new tests to the test suite (the tar.gz is now >2MB :-/), o checks for 64 bit types during the configure process and uses the result also for *printf() formats, o adds --with-pathseparator configure option (useful in cygwin environments?), o updates the IANA maintained modules, and o fixes some bugs. See the ChangeLog file for more details. As usual the current release can be found at http://www.ibr.cs.tu-bs.de/projects/libsmi/ ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/ Frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

Re: [libsmi] libsmi release 0.2.7
by Frank Strauss 09 Nov '00

09 Nov '00

Yigal> On a slightly different topic: Yigal> I added "-Wall -Wformat" to CFLAGS in tool/Makefile. Yigal> It looks like this: Yigal> CFLAGS = -g -O2 -Wall -Wformat Yigal> The -Wformat checks the validity of printfs syntax. Yigal> I discovered several places with printf syntax problems. If you add Yigal> those flags and recompile you will see those warnings/errors. Yigal> I suggest to add both flags as a standard to CFLAGS in Makefile. This Yigal> will help in creating a better quality source code. I should keep in remind to usually add it to the --with-cflags options when I build using gcc. However, I did not add -Wall to the CFLAGS by default, because it's compiler specific. We could do it in cases where configure finds and uses gcc, but that would be just half of the story. BTW, -Wall includes -Wformat. On which platform did you get the warnings? On Linux everything is fine. No warnings at all with -Wall. If your warnings appear on W32, could you please send me (not to the list) a dump of your make output? -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

Re: [libsmi] libsmi release 0.2.7
by Frank Strauss 09 Nov '00

09 Nov '00

Yigal> I built the new libsmi described below on NT4 using cygwin. The built Yigal> went ok. I use the following config file where I changed the path Yigal> directive to include : in front of the path. Yigal> ================<< start quote ============================ Yigal> # Last edit: Thu Nov 09 11:39:37 2000 Yigal> # By: Yigal Hochberg Yigal> # Yigal> # File: smi.cfg Yigal> # libsmi initialization file Yigal> # Yigal> # path of mib modules Yigal> # you can use the posix notation: //x/<path> to specify drive x: Yigal> # e.g //c/dmhsnmp-agent/mibdir/ Yigal> # Yigal> path ://f/yigal/dmh-libsmi/libsmi-0.2.7/mibs/ietf/ Yigal> path :../mibs/ietf/ Yigal> path :../mibs/iana/ Yigal> ================== end quote >>============================== Yigal> Unfortunately with or without the : smidump cannot find files in the Yigal> mib directories. Yigal> Any idea what is wrong? Note that up to and including libsmi 0.2.5 Yigal> smidump works very well in this environment. The path separator character on `#ifdef _WIN32' systems is `;' instead of `:'. I cannot confirm the comments of your configuration file on the `posix notation'. I would expect that something like path ;f:\yigal\dmh-libsmi\libsmi-0.2.7\mibs\ietf path ;..\mibs\ietf\ path ;..\mibs\iana\ is ok. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 2

Re: [libsmi] libsmi release 0.2.7
by Frank Strauss 09 Nov '00

09 Nov '00

>> The path separator character on `#ifdef _WIN32' systems is `;' instead >> of `:'. Yigal> I changed the config file to use ; instead of : Yigal> This works fine. Yigal> The problem is that the different path-separator char (; vs. :) now Yigal> requires different configuration file for wintel environment and unix Yigal> environment. Ok. So, what would you think about a configure option for optionally specifying the path separator character? -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

libsmi release 0.2.7
by Frank Strauss 09 Nov '00

09 Nov '00

Hi! >From time to time it's time for a new release. This time it's time for 0.2.7. o As always this release fixes bugs in the library and in the tools reported and fixed by many people. Thanks! Especially to Bill Fenner and Pat Knight. o A bunch of new and updated IETF standards track modules have been released and (fixed where appropriate and) integrated with libsmi. o Some new checks have been added to the SMIv1/v2 parser. o A new dump format has been contributed by Pat Knight, that generates Python dictionaries. o The man pages have been updated. o NOTE: There are at least two changes in the API. However, they are expected to be binary compatible, and the major library number has not been incremented. o Another change affects the module search path setup. The arguments of the configuration file `path' statement now have the same meaning as the SMIPATH environment variable. This means, to retain the semantics of your existent configuration files, you have to prepend a `:' to the `path' statements' arguments. See smi_config(3). See the ChangeLog file for more details. As usual the current release can be found at http://www.ibr.cs.tu-bs.de/projects/libsmi/ ftp://ftp.ibr.cs.tu-bs.de/pub/local/libsmi/ Enjoy, Frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Re: [libsmi] libsmi-0.2.7 make problems
by Bill Fenner 08 Nov '00

08 Nov '00

The released version of tcpdump from tcpdump.org only work with pre-0.2.0 libsmi. The most recent CVS versions (i.e. in the last day or two) contain fixes to allow it to also work with 0.2.x versions. Bill -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

2 1

Re: [libsmi] libsmi-0.2.7 make problems
by Frank Strauss 08 Nov '00

08 Nov '00

Steve> The first problem I seem to have fixed by editing on of the Steve> test files (008). Juergen> I agree that this is a bug in the text case. I have submitted Juergen> a patch to fix this to Frank and I guess it will soon show up Juergen> in the CVS. Oops. I'm sorry that I did not look closer at the test suite modules. I've applied the two changes. Thanks. -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <libsmi-request(a)ibr.cs.tu-bs.de>. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.

1 0

libsmi-0.2.7 make problems
by Steve Bernard 08 Nov '00

08 Nov '00

In attempting to install TCPDump, which requires libpcap, which requires libsmi ;), I have run into some problems when compiling on RH 7.0. The first problem I seem to have fixed by editing on of the test files (008). The other problems I'm not too sure on, so I've included all my debug info in the following attachments. Each file is labeled to describe what process created it. I'm using an updated version of VA Linux's RH 7.0.x distro on a K6-2 333MHz. Please excuse the file naming convention, I couldn't help myself ;) The debug info was created AFTER making the changes in libsmi-0.2.7-changes. In cases where there isn't an .err file there weren't any errors. The files are in the order that the operations occured. If the attachments are creating a problem I can send them by some other method. TIA, ***** Steve Bernard Network Engineer UCIS Emerging Technologies George Mason University

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Libsmi November 2000