search for: ar01s09

...o of latest Raspbian on a Raspberry Pi 3. When I installed from the package manager, everything worked great (just missing the SSL support). I've been referring to these docs: https://networkupstools.org/docs/user-manual.chunked/ar01s05.html https://networkupstools.org/docs/user-manual.chunked/ar01s09.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20200322/5d0ff288/attachment.html>

Hi: I found I can setup password for uspmon. but upsc can connect to any upsd without authentication. although the ups data is not very confidential, but I would like not to expose it to anyone who can connect to server. is there any method to harden upsd? thanks for hint. Regards, tbskyd

...assume this holds true for Raspbian as well. > I've been referring to these docs: > > https://networkupstools.org/docs/user-manual.chunked/ar01s05.html <https://networkupstools.org/docs/user-manual.chunked/ar01s05.html> > https://networkupstools.org/docs/user-manual.chunked/ar01s09.html <https://networkupstools.org/docs/user-manual.chunked/ar01s09.html> It's been hard to keep the NUT manual in sync with the various distributions, so the latest information for building is here: https://github.com/networkupstools/nut/wiki/Building-NUT-on-Debian,-Raspbian-and-Ubuntu &l...

...without SSL or NSS support. (Should be something like "--without-ssl") On the other hand, didn't you say in a previous email (mid-May) that you were using packages? If so, wolfy's suggestion is similar to the instructions here: https://networkupstools.org/docs/user-manual.chunked/ar01s09.html#_nss_backend_usage . -- - Charles Lepple https://ghz.cc/charles/

...lled from the package manager, everything > >worked great (just missing the SSL support). I've been referring to > >these > >docs: > > > >https://networkupstools.org/docs/user-manual.chunked/ar01s05.html > >https://networkupstools.org/docs/user-manual.chunked/ar01s09.html > > You mention compiling against libusb-1.0 but do not mention which NUT > codebase you use. The master branch at the moment does not support it, only > libusb-0.1 and there are some known connectivity stability bugs associated > with that. > > Currently there is a long-p...

Hello, when I have UPS connected to NUT server, does it matter if the NUT client (running a different version) supports that UPS? In other words, does the NUT protocol require the UPS being supported by the client in addition to the server? ...I guess the answer is 'no' but I'd like to know if there is anything good to know. -- Matus UHLAR - fantomas, uhlar at fantomas.sk ;

...only allow certain clients to connect. However, in most cases where you would consider TCP-wrappers, you would probably be better served with a kernel-level firewall. There is also an option to compile NUT to verify client SSL certificates: http://www.networkupstools.org/docs/user-manual.chunked/ar01s09.html#_upsd_optional_client_authentication -- Charles Lepple clepple at gmail

What is the purpose of the LOGIN <upsdevice> and LOGOUT commands in the network protocol? It seems if I supply USERNAME and PASSWORD then I am able to perform any operations on the device, so why would I need to use LOGIN? And since LOGIN takes a <upsdevice> but LOGOUT does not, I guess that LOGOUT is implicitly associated with the last (most recent) LOGIN? Which means a single client

...FCLCD via USB Followed this article: https://loganmarchione.com/2017/02/raspberry-pi-ups-monitor-with-nginx-web-m onitoring/ "upsc" command works and outputs UPS data correctly. My question regards the TCP network interface: https://networkupstools.org/docs/developer-guide.chunked/ar01s09.html I can connect and via netstat see the TCP connection is established. After writing a command to the stream, when I read it times out. Code here: https://pastebin.com/HXkGkhdZ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net...

...FCLCD via USB Followed this article: https://loganmarchione.com/2017/02/raspberry-pi-ups-monitor-with-nginx-web-m onitoring/ "upsc" command works and outputs UPS data correctly. My question regards the TCP network interface: https://networkupstools.org/docs/developer-guide.chunked/ar01s09.html I can connect and via netstat see the TCP connection is established. After writing a command to the stream, when I read it times out. Code here: https://pastebin.com/HXkGkhdZ -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://alioth-lists.debian.net...

...t;Raspberry Pi 3. When I installed from the package manager, everything >worked great (just missing the SSL support). I've been referring to >these >docs: > >https://networkupstools.org/docs/user-manual.chunked/ar01s05.html >https://networkupstools.org/docs/user-manual.chunked/ar01s09.html You mention compiling against libusb-1.0 but do not mention which NUT codebase you use. The master branch at the moment does not support it, only libusb-0.1 and there are some known connectivity stability bugs associated with that. Currently there is a long-pending competition of several imp...

Hello!! I'm a sysadmin at La Laguna University in Spain. We are using NUT to manage our UPS with great success, but we miss a feature and we would like to send this patch to you. If you apply this patch running upsd -c info you'll get information about client connections in syslog. This is very simple and helpfull if you have hundreds of servers connected to the same upsd. Thank you for

Hi all. I'm working on an update to the ONEAC driver and have a request from a user that I am not sure how to handle. The UPS can be communicated with through a couple different methods (e.g. Serial, network). If a UPS shutdown command comes through the network interface, the user wants NUT (serial connection) to signal the supported systems to shutdown. What is the "right"

...r, >everything >> >worked great (just missing the SSL support). I've been referring to >> >these >> >docs: >> > >> >https://networkupstools.org/docs/user-manual.chunked/ar01s05.html >> >https://networkupstools.org/docs/user-manual.chunked/ar01s09.html >> >> You mention compiling against libusb-1.0 but do not mention which NUT >> codebase you use. The master branch at the moment does not support >it, only >> libusb-0.1 and there are some known connectivity stability bugs >associated >> with that. >>...

On May 31, 2019, at 1:29 AM, Manuel Wolfshant wrote: > > On 5/31/19 6:54 AM, Gene Heskett wrote: >> Greetings all; >> >> gene at coyote:~$ upsc myups >> Init SSL without certificate database >> battery.charge: 100 >> battery.charge.low: 30 >> [yadda yadda] >> >> Is there a certificate package I should install? >> >>

I tried adding SSL/TLS support to NUT following the User Manual chapter 9.5 "Configuring SSL". I got as far as generating a self-signed private key and a certificate (public key) in a single file gold.pem which has the form -----BEGIN CERTIFICATE----- MIID3DCCA... -----END CERTIFICATE----- -----BEGIN PRIVATE KEY----- MIIEvQIBA... -----END PRIVATE KEY----- I updated

....txt&#39; from the nut-2.4.3 branch (this file didn&#39;t make= it into AsciiDoc).</blockquote> <div><br>this file (ssl.txt) was merged into security.txt, part of the Asci= iDoc rewrite:<br><a href=3D"http://new.networkupstools.org/docs/user-manual= .chunked/ar01s09.html#_recommended_make_upsmon_verify_all_connections_with_= certificates">http://new.networkupstools.org/docs/user-manual.chunked/ar01s= 09.html#_recommended_make_upsmon_verify_all_connections_with_certificates</= a><br> <br>that being said, CERTVERIFY and FORCESSL are not...