search for: secnam

This adds [f]getc() and fgets() for parsing config files. Probably hard to avoid. Still trying to decide if I actually want to add system() or not. -hpa

...ifferent one (e.g. an SNMP v1 or v2c string) does that user > / community 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...

nut-2.6.5 Scientific Linux 6.3 APC AP9630 management card My basic question is, does nut's SNMPv3 implementation work? I have this in /etc/ups/ups.conf ...... [tfapc01] driver = snmp-ups port = tfapc01.testfest.ixorg.org mibs = apcc snmp_version = v3 secLevel = authPriv secName = tfsnmpprof1 authPassword = ralow6moHet7zoboP8 privPassword = tuseL8Pakaz9degim7 authProtocol=MD5 privProtocol=AES desc = "APC SU700 SNMP v3 device, with the highest security level" ...... Now I test /sbin/snmp-ups -DDD -a tfapc01 Network UPS Tools - Generic SNMP UPS driver 0.68 (...

...assphrase: 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 -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x...

...problem with the binaries from EPEL I downloaded the source and compiled 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]...

...een the values are on the port and desc lines (ignoring #, of course). [ups1] desc = "APC Smart-UPS 5000 SNMP in rack 1 - AP9617" driver = snmp-ups mibs = apcc port = [ups1...] # snmp_version = v1 # community = [xxx] snmp_version = v3 secLevel = authPriv secName = [xxx] authPassword = [xxx] authProtocol = MD5 privPassword = [xxx] privProtocol = DES [ups2] desc = "APC Smart-UPS 5000 SNMP in rack 2 - AP9619" driver = snmp-ups mibs = apcc port = [ups2...] snmp_version = v1 community = [xxx] # snmp_version...

...smart UPS srt3000 with NMC I am trying to set up NUT with snmp for my apc ups. Heres the config; [ups6]                 Driver = snmp-ups                 Port: ups6.domain.name (also tried 192.168.24.9)                 Snmp_version = v3                 secLevel = authPriv                 secName = ups6                 authPassword = PASSWORDSTRING                 authProtocol = MD5                 privPassword = PASSWORDSTRING                 privProtocol = AES                 pollfreq = 15                 desc = “apc ups” But when I run the service, I get this error # /usr/...

...assphrase: 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 -S -s apcups --secLevel authPriv --secName nut --authProtocol MD5 --authPassword NutScan at Password43LongerWord --privProtocol DES --privPassword NutScan at Password43LongerWord Scanning SNMP bus. Error: unknown authtypeError generating Ku from authentication pass phrase snmpwalk gives a different error: $ snmpwalk -v 3 -u nut apcups -x...

...where in nut, not a config problem. I've just tried the same command 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 deve...

Hi, Every time that I have to restart the nut-server it's a nightmare. For example, after editing ups.conf In many cases the only "solution" is to reboot the system. These are the errors: systemctl -l status nut-driver ? nut-driver.service - Network UPS Tools - power device driver controller Loaded: loaded (/usr/lib/systemd/system/nut-driver.service; static; vendor preset:

...Mar 30 2018 16:51:08 * ups.conf [..] [foo] driver = snmp-ups # 'hostname' is resolvable, tcpdump shows initial snmp udp request and reply port = hostname snmp_version = v3 secLevel = authPriv # 4 lowercase ascii letters secName = xxxx # # 16 lower case ascii letters authPassword = xxxxxxxxxxxxxxxx # 15 lower case ascii letters privPassword = yyyyyyyyyyyyyyy authProtocol = SHA privProtocol = AES [..] * driver debug output and tcpdump attached in nuttrace & nut.pca...

I'm in the process of trying to get NUT to manage an APC SmartUPS. Monitoring of the UPS is working fine: $ upsc nutdev1 at localhost Init SSL without certificate database ambient.1.humidity.alarm.high: 60.00 ambient.1.humidity.alarm.low: 30.00 ambient.1.temperature.alarm.high: 40.00 ambient.1.temperature.alarm.low: 10.00 battery.charge: 94.00 battery.charge.restart: 0 battery.current: 0.00