Nut upsuser - Nov 2016 - Can't get NUT slave to connect to master

Hi can anyone please help.

Although I have two servers in the same cabinet/room and sharing the same
UPS - they're on different networks.

I've tried everything I can find online, but whatever I do I can't get
the
slave nut client to connect to the master.

When testing then on the same LAN, they DO work - but how do I allow the IP
of the slave to connect to the master when both on different networks?

Please help I've searched everywhere and spent a lot of time on this and
I'm not getting anywhere fast!

Thank you for any help with this. All I'd like to do is allow one external
IP access so it can be a client and shutdown correctly with the master on
the other network.

Thanks again for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161124/d26ca063/attachment.html>

On Thu, 24 Nov 2016, Jonah Naylor wrote:
> Hi can anyone please help.
> Although I have two servers in the same cabinet/room and sharing the same
UPS - they're on different networks.
> I've tried everything I can find online, but whatever I do I can't
get the slave nut client to connect to the master.
> When testing then on the same LAN, they DO work - but how do I allow the IP
of the slave to connect to the master when both on different networks?
Can you ping from one server to the other?  If not, then this is a 
network/subnetwork routing problem.  Is it a deliberate site policy that 
systems on diferent subnets cannot connect?  Are you the administrator of 
the networks? Do the network routers have rules to allow traffic between 
subnets? Can you see in the router logs where the traffic is blocked?

Roger

Hi thanks for the reply.

The servers can ping each other...

The router log doesn't show anything and I am the admin for the servers.
The machines firewalls allow each other's ips etc.

Part of the issue is possibly that I just don't know if I've set up NUT
correctly for this arrangement? Like I say it works ok on LAN, but not
across networks.

Is there something I should be doing other than adding "allowfrom
ipaddressofslave" to the upsd.users file on the master?

I have this also in there:

[monuser]
                password  = pass
                upsmon slave
                allowfrom = ipaddressofslave

-

Then on the slave client I have this in the upsmon.conf:

MONITOR UPS at ipaddressofmaster 1 monuser pass slave

Thanks again for any help.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161124/b4c4d5fd/attachment.html>

On Thu, 24 Nov 2016, Jonah Naylor wrote:
> The servers can ping each other... The router log doesn't show anything
> and I am the admin for the servers. The machines firewalls allow each 
> other's ips etc. Part of the issue is possibly that I just don't
know if
> I've set up NUT correctly for this arrangement? Like I say it works ok 
> on LAN, but not across networks. Is there something I should be doing 
> other than adding "allowfrom = ipaddressofslave" to the
upsd.users file
> on the master?
Does your NUT have TCP wrappers compiled in?  In that case is 
/etc/hosts.allow on the master set to allow the traffic?

When you issue a NUT command on the slave, addressed to the master, does 
tcpdump on the master's subnetwork show the traffic to port 3493?

Roger

On Nov 24, 2016, at 10:58 AM, Jonah Naylor <jonah at hostingyorkshire.uk>
wrote:
> 
> Is there something I should be doing other than adding "allowfrom =
ipaddressofslave" to the upsd.users file on the master?
Which version of NUT are you using?

Reference for the current version:
http://networkupstools.org/docs/man/upsd.users.html

Roger asked about whether your build of NUT uses TCP-wrappers. If it does, you
may need to configure hosts.allow and hosts.deny, which replaces the ACLs in
upsd.users. (I haven't used TCP-wrappers in years, so I may be
misremembering.) If you are not sure, let us know more details about your setup.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20161124/7f5c009e/attachment-0001.html>