Re: [Nut-upsuser] MACOSX-UPS Client/Server Communications Issues

2015-08-01 Thread AIYL
I’ve already completed the tests, setting up NUT in FreeBSD running in a Parallels virtual machine.Results:a.- Can you try 'upscups@10.0.2.151' from another system on the network?NUT Client running in FreeBSD connects to NUT server in OSX, upsc@10.0.2.151, output:battery.charge:

Re: [Nut-upsuser] MACOSX-UPS Client/Server Communications Issues

2015-07-28 Thread Charles Lepple
On Jul 28, 2015, at 12:13 PM, AIYL adliya...@gmail.com wrote: Before contacting Synology and Netgear/Readynas, I’d prefer to make sure that the NUT UPS Server has been setup correctly and that the “experimental” MACOSX-UPS driver is equivalent to a standard “usb” driver in terms of

Re: [Nut-upsuser] MACOSX-UPS Client/Server Communications Issues

2015-07-28 Thread Charles Lepple
I’ve not been able to solve some issues regarding the communication between a NUT Server running the MACOSX-UPS driver and the NUT clients on networked NAS’es. NUT Software installed on a Macmini running OSX Yosemite has managed to shutdown the networked devices, a Readynas and a

Re: [Nut-upsuser] MACOSX-UPS Client/Server Communications Issues

2015-07-28 Thread AIYL
To your comments: 1.- Can you try 'upsc ups@10.0.2.151 mailto:ups@10.0.2.151' from another system on the network? I’ve just one computer in the network, it’s my home's network. However, I can do the following: a.- Turn-off the Macmini’s firewall. (Note: I’ve already added “upsd to the