[Nut-upsuser] Nut not working remotely

Charles Lepple clepple at gmail.com
Sun Aug 14 17:55:34 UTC 2011

On Aug 14, 2011, at 1:34 PM, Chris Boot wrote:

> On 14/08/2011 18:30, Leslie Rhorer wrote:
>>> -----Original Message-----
>>> From: Charles Lepple [mailto:clepple at gmail.com]
>>> Sent: Sunday, August 14, 2011 10:29 AM
>>> To: lrhorer at satx.rr.com
>>> Cc: nut-upsuser at lists.alioth.debian.org
>>> Subject: Re: [Nut-upsuser] Nut not working remotely
>>> On Aug 13, 2011, at 1:03 PM, Leslie Rhorer wrote:
>>>> 	Hello everyone.  I have NUT up and running on three servers,
>>> What version(s) of NUT?
>> The system I can reach is running 2.2.2 under Debian "Lenny", kernel
>> 2.6.26-2-686.
>> The systems I cannot reach are running 2.4.3 under Debian  
>> "Squeeze", kernel
>> 2.6.32-5-amd64.
> That doesn't actually tell us the versions of NUT you're using...  
> But as I run Debian I think I know what the problem is.

Chris: I don't think the Debian package versions patch any of the NUT  
networking code, so the versions Leslie mentioned (2.2.2 and 2.4.3)  
are sufficient to identify the LISTEN difference you mentioned below.

> Edit /etc/nut/upsd.conf and add/change the LISTEN line to:
> LISTEN 3493
> By default newer Debian version of NUT bind to localhost, so you  
> won't be able to access it from other machines unless you make the  
> change.

Leslie: because of this change, be sure that you convert any leftover  
ACLs in your upsd.conf file to either /etc/hosts.deny lines or  
iptables-style firewall rules. 

More information about the Nut-upsuser mailing list