Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Tim Dawson
Try ALL:ALL in /etc/hosts.allow temporarily. If that still doesn't work, it's likely something else. If it does, only then screw with creating narrow rules . . . - Tim On November 25, 2016 6:37:02 AM CST, Roger Price wrote: >On Fri, 25 Nov 2016, Jonah Naylor wrote: > >>

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Jonah Naylor
Hi, When on the same LAN it just worked without anything in the hosts.allow file. It's difficult for me to now put the slave back on the same lan as the master due to the way the production servers are being used... Causing downtime etc... I do have another spare server though which I could put

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Roger Price
On Fri, 25 Nov 2016, Jonah Naylor wrote: I'm still getting "Connection refused on the client cgi screen as well as in the shell it gives me UPS upsname@ipaddresshere is unavailable... You reported that access works correctly from elsewhere on the master subnetwork. Does access from the

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Jonah Naylor
Hi thanks Roger, I've amended my hosts.allow file to your suggested one - thanks for that. I'm still getting "Connection refused on the client cgi screen as well as in the shell it gives me UPS upsname@ipaddresshere is unavailable... Any ideas what I can try next to debug why it's not working.

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Roger Price
On Fri, 25 Nov 2016, Jonah Naylor wrote: upsd : ipaddressofclientgoeshere If it were me I would write upsd : ipaddressofclient :\ spawn (/bin/mail -r hosts.allow@localhost\ -s '%s@%h accepted access to %d from %c'\ sysadmin@somedomain) &

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Jonah Naylor
Hi thanks Roger. Well I'm just using Ubuntu Server 16.04 LTS I only ran that command as a few guides say that's how to establish if a daemon is compiled with tcp wrappers: https://www.cyberciti.biz/faq/tcp-wrappers-hosts-allow-deny-tutorial/ I haven't really used TCP wrappers before so I'm not

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Roger Price
On Fri, 25 Nov 2016, Jonah Naylor wrote: I don't think nut is built with TCP wrappers support, although the package is listed as depending on libwrap... Why would you have such a dependency if nut didn't use TCP Wrappers? I ran this command: ldd /sbin/upsd | grep libwrap.so and it has

Re: [Nut-upsuser] Can't get NUT slave to connect to master

2016-11-25 Thread Jonah Naylor
Hi thanks for helping. I don't think nut is built with TCP wrappers support, although the package is listed as depending on libwrap... I ran this command: ldd /sbin/upsd | grep libwrap.so and it has returned no output. Does this mean I have to compile from source or is there a way to add the