Aha, it seems quite easy to add custom oids to that. Would it be possible, and keeping with the design of pfSense, to include a custom OID in the default config giving the version?
Personally I think it would be preferable to give out the pfsense version in place of the freebsd version, but I guess most people wouldn't agree :) Adam. -----Original Message----- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: 24 January 2007 17:10 To: [email protected] Subject: Re: [pfSense Support] pfSense SNMP identification We use BSnmpd. Scott On 1/24/07, Adam Armstrong <[EMAIL PROTECTED]> wrote: > That MIB doesn't help me identify a pfSense box from a FreeBSD box? > > Does the SNMP daemon you're using allow you to define custom OIDs? Which > daemon is it? > > Perhaps the default SNMP configuration could include an OID which gives a > pfSense id and version? > > Adam. > > -----Original Message----- > From: Scott Ullrich [mailto:[EMAIL PROTECTED] > Sent: 24 January 2007 15:37 > To: [email protected] > Subject: Re: [pfSense Support] pfSense SNMP identification > > While I don't have a answer to your questions specifically, we do have > some of the mibs documented if it will help: > > http://cvstrac.pfsense.com/tktview?tn=257 > > Scott > > > On 1/24/07, Adam Armstrong <[EMAIL PROTECTED]> wrote: > > My current deployment is generating 500mb of rrd files! > > > > I'm sure at some point in the future it would be quite easy to > > appliance-ize, though perhaps a pfsense package wouldn't be the correct > > place? > > > > If anyone is interested in having a poke at it, I'd be willing to help > them > > install it. It's not very well documented at the moment, but I could do > with > > some other people to give suggestions and/or fix things! > > > > Adam. > > > > -----Original Message----- > > From: Holger Bauer [mailto:[EMAIL PROTECTED] > > Sent: 24 January 2007 14:47 > > To: [email protected] > > Subject: RE: [pfSense Support] pfSense SNMP identification > > > > I don't have an answer to your questions but the screenshots at your > > page look promising :-) > > You could maybe create a package for pfSense to make it a monitoring > > appliance. > > > > Holger > > > > > > > > > -----Original Message----- > > > From: Adam Armstrong [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, January 24, 2007 3:04 PM > > > To: [email protected] > > > Subject: [pfSense Support] pfSense SNMP identification > > > > > > Hi, > > > > > > I'm currently writing an NMS > > > (http://www.pimpmynetwork.org/observer/) which uses SNMP to > > > automatically guess the operating system of hosts and setup > > > graphing/monitoring accordingly. > > > > > > The cut-down SNMP daemon in m0n0/pfsense massively reduces > > > the number of things I can monitor on m0n0, and I can't see a > > > way to easily identify them via SNMP using version strings or > > > similar. I'm currently manually identifying m0n0 boxes in the > > > database, which then limits the amount of information the > > > application tries to poll/display. > > > > > > Does anyone have any suggestions on how to identify m0n0wall > > > and pfSense via SNMP? > > > > > > Could a simple change be made to allow them to be easily > > > identified? (a custom OID for pfSense giving out its version > > > would be great!) > > > > > > Perhaps an identifier and version could be appended to the > > > FreeBSD kernel version? > > > > > > (sorry for cross-posting, and for those of you who've seen > > > something very similar on the m0n0 list!) > > > > > > Thanks, > > > Adam. > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] For > > > additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
