search for: snmpv1

...lients don't always match up with the complaint times on the master. Sometimes they both complain at the same time, sometimes the master complains but the client doesn't, and some times the client complains but the master doesn't. I don't remember seeing this at all when I was using SNMPv1 but I didn't use that for very long so it's possible I just didn't see it because it hadn't happened yet. I think I'm going to switch the config to SNMPv1 for a while and see if the problem persists. nomad

...ps.mfr: CYBERPOWER ups.model: PR3000LCDRTXL2U ups.serial: PTEHU2000098 ups.status: OL In particular, no load, no input or output voltage. (And the runtime report is not to be trusted yet until I do a calibration run.) Is this to be expected from snmp-ups? (Also, I can so far connect only using snmpv1, but I don't know whether I should expect to get any additional data from snmpv3 anyway.) The HCL seems to imply that this UPS should *also* be supported by the powerpanel driver. However, I see from the documentation that the powerpanel driver is a lot of best-effort because cyberpower is u...

...ays match up with the complaint times on the master. > Sometimes they both complain at the same time, sometimes the master > complains but the client doesn't, and some times the client complains > but the master doesn't. I don't remember seeing this at all when I was > using SNMPv1 but I didn't use that for very long so it's possible I just > didn't see it because it hadn't happened yet. I think I'm going to > switch the config to SNMPv1 for a while and see if the problem persists.

...ed are probably the snmpwalk outputs described at the end of this section: https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers <https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers> > (Also, I can so far connect only using snmpv1, but I don't know whether > I should expect to get any additional data from snmpv3 anyway.) Again, not my area of expertise, but as far as NUT is concerned, I think the different versions are for authentication methods (SNMPv1 is cleartext). -------------- next part -------------- An HTML...

...iv -a MD5 -A ralow6moHet7zoboP8 \ -x AES -X tuseL8Pakaz9degim7 tfapc01 .1.3.6.1.4.1.318.1.1.1.1.1.1.0 No log handling enabled - turning on stderr logging SNMPv2-SMI::enterprises.318.1.1.1.1.1.1.0 = STRING: "SMART-UPS 700" Now if we drop the "snmp_version" line from ups.conf and SNMPv1 is enabled on the APC with default public read private write, NUT will happily use its defaults to talk to the APC using v1 even though you have configured the ups.conf settings for v3 following documentation examples. Note: contrary to the documentation saying that valid values for snmp_version a...

I have it "working" with the following settings changes from the default in the RPM. By "working" I mean it starts after reboot and after issuing 'sudo systemctl restart nut-driver' but, as expected, it takes quite a while to finish startup. /etc/systemd/system/nut-driver.service.d/nut-driver.conf [Unit] StopWhenUnneeded=no [Service] TimeoutSec=600

...dling requests and traps. NOTE: The Net-SNMP port directory is ports/net/net-snmp, but the package name is still ucd-snmp. II. Problem Description The Net-SNMP port, versions prior to 4.2.3, contains several remotely exploitable vulnerabilities. The OUSPG has discovered vulnerabilities in many SNMPv1 implementations through their `PROTOS - Security Testing of Protocol Implementations' project. The vulnerabilities are numerous and affect SNMPv1 request and trap handling in both managers and agents. Please refer to the References section for complete details. The Net-SNMP port is not insta...

...rd. The SNMPv3 configurations on all three are exactly the same. This is confirmed by snmpget calls that work just fine: snmpget -Cf -v3 -u [...] -l authPriv -A '[...]' -X '[...]' -a MD5 -x DES [upsname] .1.3.6.1.4.1.318.1.1.1.1.1.1.0 snmp-ups can query all three UPSs with SNMPv1 with no problems. However, querying with SNMPv3 doesn't work if I try to query more than one of them. SNMPv3 works fine when I have any one of the three configured in ups.conf while the other two are configured with SNMPv1. It doesn't matter which _one_ UPS is configured for SNMPv3 in ups....

...l to none and leaving off the -x & -X flags, still get the same error messages. I see a note in APC's documentation that it may take some time for the card to be ready to talk SNMPv3. I've waited as long as 15 minutes with no change in behavior. snmpwalk and nut-scanner are both happy SNMPv1 -c public. Can anyone tell me, please, what trivially obvious thing am I missing? thanks, nomad -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200428/c461b613/attachment.html>

...ere is already a skeleton MIB mapping in NUT, the only two > things needed are probably the snmpwalk outputs described at the end of > this > section: https://networkupstools.org/docs/developer-guide.chunked/ar01s04.html#snmp-subdrivers > >> (Also, I can so far connect only using snmpv1, but I don't know whether >> I should expect to get any additional data from snmpv3 anyway.) > > Again, not my area of expertise, but as far as NUT is concerned, I think > the different versions are for authentication methods (SNMPv1 is cleartext). I actually switched to the u...

This is slightly off-topic, I guess, but I'm not sure who better to ask for help. I'm active within the FreeNAS community and involved in their (FreeBSD based) documentation work. There is a long standing bug ticket - years old now - to update their "network ups tools" docs page, to cover Ethernet attached UPS that use nut for the link. Currently the docs mainly describes

On Nov 30, 2017, at 6:31 PM, Lee Damon <nomad at ee.washington.edu> wrote: > > SNMPv3 works fine when I have any one of the three configured in > ups.conf while the other two are configured with SNMPv1. It doesn't > matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all > work individually (see below example). > > However, if I configure any two or all three of them to use SNMPv3 then > on startup upsdrvctl complains about "unhandled ASN 0x81 received from...

I'm having trouble using the documentation to install the SNMP driver to use in my UPS how do I install the driver to actually get it to work? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20230411/fe271d26/attachment.htm>

On 4/28/20 1:58 PM, David Zomaya wrote: > snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X > privpassphrase Evidently, even with argument identifiers order matters. That worked just fine and dandy. Now I guess I need to play with the order of the nut-scanner arguments to see if I get a similar result. thanks, nomad

...l to none and leaving off the -x & -X flags, still get the same error messages. I see a note in APC's documentation that it may take some time for the card to be ready to talk SNMPv3. I've waited as long as 15 minutes with no change in behavior. snmpwalk and nut-scanner are both happy SNMPv1 -c public. Can anyone tell me, please, what trivially obvious thing am I missing? thanks, nomad ________________________________ This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender....

...mmand: rpm --checksig <filename> If you only wish to verify that each package has not been corrupted or tampered with, examine only the md5sum with the following command: rpm --checksig --nogpg <filename> 8. References: http://www.ee.oulu.fi/research/ouspg/protos/testing/c06/snmpv1/0100.html http://www.cert.org/advisories/CA-2002-03.html http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0012 http://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2002-0013 Copyright(c) 2000, 2001 Red Hat, Inc.

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=512 ------- Additional Comments From kaber@trash.net 2006-09-18 07:36 MET ------- There are still some problems with the PPtP helper, I'm currently trying to fix these. Can you attach a tcpdump of a failed attempt please? -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You are

...oubt anyone will be. :) nomad On 12/3/17 14:34 , Charles Lepple wrote: > On Nov 30, 2017, at 6:31 PM, Lee Damon <nomad at ee.washington.edu> wrote: >> >> SNMPv3 works fine when I have any one of the three configured in >> ups.conf while the other two are configured with SNMPv1. It doesn't >> matter which _one_ UPS is configured for SNMPv3 in ups.conf, they all >> work individually (see below example). >> >> However, if I configure any two or all three of them to use SNMPv3 then >> on startup upsdrvctl complains about "unhandled ASN...