Re: Maintainer of SNMP module?
| From: | Johann Hanne | Date: | Fri, 03 Jan 2003 12:20:40 +0000 |
| Subject: | Re: Maintainer of SNMP module? | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-93071@lists.php.net to get a copy of this message | ||
Hi Harrie,
thanks for the reply. I didn't want critize net-snmp or the PHP SNMP
binding. All I want to do is some SNMP programming with PHP, and the
points I mentioned *ARE* a problem for me. Just one example: I want to
find out what units are present in a 3Com SuperStack II. The first step is:
$stackinfo=snmpwalkoid($hostname, "rollout",
".iso.org.dod.internet.private.enterprises.43.10.27.1.1.1");
Now, with PHP prior to 4.3.0, the keys of the returned array completely
depend on which MIBs are loaded:
- If a 3Com MIB is loaded, the keys may be:
enterprises.a3Com.generic.27.1.1.1.2.1
enterprises.a3Com.generic.27.1.1.1.2.2
enterprises.a3Com.generic.27.1.1.1.2.3
etc.
- If no 3Com MIB is loaded, the keys may be:
enterprises.43.10.27.1.1.1.2.1
enterprises.43.10.27.1.1.1.2.2
enterprises.43.10.27.1.1.1.2.3
Additionally, the first part of the OID path
(.iso.org.dod.internet.private) is left out. Yes, this is documented, but
it's painful to check which part of the path is dropped for each SNMP
walk.
With the introduction of snmp_set_oid_numeric_print() this is solved now.
But the problem with the preparsed SNMP values still exists. There is no
way to find out, of which type a returned value is. snmp_set_quick_print()
is no complete solution. I*ll try to make a function which returns an
object with the properties snmp_type (int, string, oid, etc.) and value.
And I hope that somebody commits it...
The other thing why I was getting a little bit frustrated was this:
The EXTENSIONS file says that the maintainer of snmp only throws in "Odd
fixes". So I asked if somebody is really working on it and what I can do
to get something in which is NOT an "Odd fix". The maintainer told me
"Submit a patch". This is not what I want - I want to discuss changes
before I make a patch, otherwise there is the risk that it will not go in,
because people don't like it or because somebody is working on it with a
completely different approach. A few days later I saw PHP 4.3.0 and much
to my surprise I saw that the SNMP extension has been much improved. So
the "Odd fixes" statement in the EXTENSIONS file seems to be wrong?!
However, this is all over now. Harrie, I hope you are the man which I can
discuss the SNMP related stuff with? :-)
Cheers, Jonny <jonny@1409.org>