search for: nutscan

I'm trying to get SNMPv3 management working for an APC AP9617 card. It is newly refurbed, running sumx v3.7.2 and aos v3.7.3. In the SNMPv3 user profiles section I have (I don't care about the password leaking, it's temporary): User Name: nut Authentication Passphrase: NutScan at Password43LongerWord Privacy Passphrase: NutScan at Password43LongerWord Authentication protocol: MD5 (only option other than none) Privacy Protocol: DES (only option other than none) In access control I've enabled user nut. However, when I try to use nut-scanner on it: $ nut-scanner...

> The Buildbot has detected a new failure of Ubuntu-maverick-x86 on > Network UPS Tools. > Full details are available at: > http://buildbot.networkupstools.org/public/nut/builders/Ubuntu-maverick-x86/builds/39 Looks like the nutscan-snmp.h file has not been checked into the branch: make[3]: Entering directory `/var/lib/buildbot/buildbot-slave-cayenne/ Ubuntu-maverick-x86/build/tools/nut-scanner' make[3]: *** No rule to make target `nutscan-snmp.h', needed by `distdir'. Stop. - Charles

Just a hunch about your snmpwalk, what happens if you format like this? snmpwalk -l authpriv -v 3 -u user -a MD5 -x DES -A authpassphrase -X privpassphrase {host address} so snmpwalk -l authpriv -v 3 -u nut -a MD5 -x DES -A NutScan at Password43LongerWord -X NutScan at Password43LongerWord apcups Thank you, David Zomaya Tripp Lite ________________________________ From: Nut-upsuser <nut-upsuser-bounces+david_zomaya=tripplite.com at alioth-lists.debian.net> on behalf of Lee Damon <nomad at ee.washington.edu>...

...ompiled for myself with the exact same result. nomad -------------- next part -------------- Script started on 2020-05-04 09:19:50-07:00 ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [936] ; nut-scanner -S --secLevel authPriv --secName nut --authProtocol MD5 --privProtocol DES --authPassword NutScan at P Password43LongerWord --privPassword NutScan at Password43LongerWord -s apcups Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase ]0;lvd at chscc-pc-052:~: || lvd at chscc-pc-052 ~ [937] ; please snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secNam...

...- Dfreebsd8=freebsd8 -DAPPLLIB_EXP=/usr/local/lib/perl5/5.8.9/BSDPAN - DHAS_FPSETMASK -DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/ local/include -I/usr/local/lib/perl5/5.8.9/mach/CORE -I/usr/include -I/ usr/local/include -I/usr/local/include/neon -g -O2 -Wall -Wsign- compare -MT libnutscan_la-scan_nut.lo -MD -MP -MF .deps/libnutscan_la- scan_nut.Tpo -c ../../../tools/nut-scanner/scan_nut.c -fPIC -DPIC - o .libs/libnutscan_la-scan_nut.o In file included from ../../../tools/nut-scanner/nut-scan.h:23, from ../../../tools/nut-scanner/scan_nut.c:22: ../../../tools/nut-scanner/nutscan-ip...

...ommunity string have read/write access? I tried setting them all with -x thing= arguments as well as letting it pull from ups.conf, same result. It's all SNMPv3 settings. sudo snmp-ups -DDDD -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k The output with -DDDD is the same either way. > tcpdump to listen for packets across UDP 161 is one way to check what is > actually being sent. I guess that really is the next step, isn't it? Darn. I was hoping...

...delay.start: 0 ups.firmware: 70.11.D ups.id: apcups ups.load: 14.00 ups.mfr: APC ups.mfr.date: 07/28/98 ups.model: SMART-UPS 1400 ups.serial: WS9831004667 ups.status: OL ups.temperature: 24.70 ups.test.date: 04/29/2020 ups.test.result: Ok I can use snmpset to halt the UPS. snmpset -v 3 -a MD5 -A NutScan at Password43LongerWord -l authPriv -u nut -x DES -X NutScan at Password43LongerWord apcups SNMPv2-SMI::enterprises.318.1.1.1.6.1.1.0 i 2 (Passwords are temporary, I don't care if they leak.) I am aware of the note in the MIB that states "Setting this variable to turnUpsOffToConserveBatt...

...============================================================== > --- trunk/tools/nut-scanner/scan_usb.c Wed Sep 14 12:24:58 2011 (r3225) > +++ trunk/tools/nut-scanner/scan_usb.c Wed Sep 14 12:25:03 2011 (r3226) > @@ -22,6 +22,7 @@ > #include "upsclient.h" > #include "nutscan-usb.h" > #include <stdio.h> > +#include <string.h> > #include "nutscan-device.h" > > static char* is_usb_device_supported(usb_device_id_t *usb_device_id_list, > > _______________________________________________ > nut-commits mailing list >...

...mand from a FBSD box with the same unfortunate result. Mind you, it could be the UPS card, I'm using the same one for both tests. : || nomad at castle nut-2.7.4 [93] ; please drivers/snmp-ups -a nutdev1 -x secLevel=authPriv -x secName=nut -x authProtocol=MD5 -x privProtocol=DES -x authPassword=NutScan at Password43LongerWord -x privPassword=NutScan at Password43LongerWord -k Network UPS Tools - Generic SNMP UPS driver 0.97 (2.7.4) No matching MIB found for sysOID '.1.3.6.1.4.1.318.1.3.2.10'! Please report it to NUT developers, with an 'upsc' output for your device. Going back to...

...kGCX9gosuUR3R9b6cDZLJnumKkJ4s1Ms&e=>: apcups ups.load: 14.00 ups.mfr: APC ups.mfr.date: 07/28/98 ups.model: SMART-UPS 1400 ups.serial: WS9831004667 ups.status: OL ups.temperature: 24.70 ups.test.date: 04/29/2020 ups.test.result: Ok I can use snmpset to halt the UPS. snmpset -v 3 -a MD5 -A NutScan at Password43LongerWord -l authPriv -u nut -x DES -X NutScan at Password43LongerWord apcups SNMPv2-SMI::enterprises.318.1.1.1.6.1.1.0 i 2 (Passwords are temporary, I don't care if they leak.) I am aware of the note in the MIB that states "Setting this variable to turnUpsOffToConserveBatt...

.../A.pine64/scripts/udev/62-nut-usbups.rules >> ../A.pine64/scripts/udev/nut-usbups.rules >> ../scripts/upower/95-upower-hid.rules >> ../scripts/devd/nut-usb.conf.in >> ../scripts/udev/nut-usbups.rules.in >> ../scripts/hotplug/libhid.usermap >> ../tools/nut-scanner/nutscan-usb.h >> harlan at pine64-a> >> >> scripts/upower/95-upower-hid.rules (automatically generated) >> scripts/devd/nut-usb.conf.in (automatically generated) >> scripts/udev/nut-usbups.rules.in (automatically generated) >> scripts/hotplug/l...

?Hello, I would like to merge branches/serial_nutscanner to the trunk. The attached patch contains the needed modifications. You can read docs/man/nutscan_scan_eaton_serial.txt to see what it is about and docs/man/nut-scanner.txt to see modification to nut-scanner tool interface. This adds about 100K to the libnutscan.so file. Regards, Fred -------...

Hi! I would like to ask about current state of Windows port. Is it frozen? It will be cool to know the plans :) Where are a lot of Windows-branches at GitHub. What is the most actual one? The Windows builder looks like turned off, am I right that it is not available currently and where were no builds after version 2.6.5-6? I couldn't find any info about proper environment to build Windows

.../upssched.pipe LOCKFN /var/run/upssched.lock AT ONLINE * EXECUTE online AT ONLINE * CANCEL-TIMER fsd AT LOWBATT * EXECUTE lowbatt AT NOCOMM * EXECUTE nocomm AT FSD * EXECUTE fsd AT ONBATT * EXECUTE onbatt upssched-cmd (on Synology): I don’t see this file.  Here are all the files in the ups folder: nutscan-usb.h  ups.conf  upsd.conf  upsd.users  upsmon.conf  upssched.conf > What is "Safe mode"?  Is it complete power down?, or some sort of hibernation? > If it's not a complete power down, how is the hibernation powered? "When the Synology NAS enters Safe Mode, it stops all se...

upsmon.conf on server:  https://pastebin.com/z4CrUTxb nut.conf on server:  https://pastebin.com/540ShZH7 Permissions for /etc/nut:  https://hastebin.com/qecolodapi.diff On the Synology (I didn’t edit any of these files): ups.conf:  https://hastebin.com/dedereqizi.shell upsd.conf:  https://hastebin.com/pupeseweda.css upsd.users:  https://hastebin.com/ocenamecex.cs I don’t think I am able to run