Re: [Apcupsd-users] Additional (non-3551) ports opened by apcupsd

[Manuel L. <lop...@gm...>]

Windows 7 x64:
Here's something peculiar, perhaps related to the non-3551 ports issue:
whenever I run apctray.exe, I get two tray icons on the *master* computer
(--to which the ups is attached).  The icons refer to the same UPS and show
the same information.  I get only one tray icon on the slave computers.

I've tried setting the "NISIP" parameter in the configuration file of the
master computer to the address of the local network adapter (i.e.
192.168.x.x.).  However, I get "communication lost" (on the master).   So
I've left NISIP at the default of 0.0.0.0.  (Setting NISIP to 127.0.0.1
gives me "communication lost" on the slaves.)  I do have more than one
network adapter on this computer, but only one network adapter is connected
to the the apcupsd slaves.
When I run TcpView.exe, I show three threads for apcupsd.exe: with tcp
local port 3551, they have remote ports of 0, 49361, and 49362 (these last
two are random on reboot).  And I show two threads for for apctray.exe:
with remote port 3551, they have local ports of 49361 and 49362 (last two
random on reboot).
When I exit apctray.exe only, then apcupsd.exe goes down to one thread:
local port 3551 and remote port 0.

I know almost nothing about networks, so I don't know what's going on, but
I can say everything on the network works as it should or at least as
documented-- except for the multiple apcupsd tray icons and those multiple
and non-3551 ports.

Is it possible to set NISIP to more than one address?  If so, I could try
setting it to the address of all the local network computers and see if
that resolves the issue.

(As a minor and entirely separate point: the "start" and "stop" apcupsd
commands in the windows start menu should be changed to require "admin"
privileges--with uac on, they do nothing on windows 7 unless you run them
elevated).


On Tue, Jan 17, 2012 at 1:43 AM, Manuel Lopez <lop...@gm...> wrote:

> On windows 7 x64, with latest stable release of apcupsd (3.14), I tried to
> get apcupsd to work as a slave (NIS server/client config), but the slave
> couldn't read the information ("COMMUNICATION LOST"), even though I created
> both inbound and outbound rules for tcp & udp ports 3551 to be open on both
> master and slave computers.  It worked when I turned windows firewall
> completely off.   Using tcpview.exe from sysinternals, I saw that
> apcupsd.exe opened up, not only port 3551 as per the docs, but also
> (seemingly) random ports: ports 59218 and 60022 also were used.
>
> I finally got it to work with the firewall on by creating inbound and
> outbound firewall rules that allowed all traffic from apcupsd.exe on ANY
> port through.
>
> I may have overlooked something in the docs, or something obvious here,
> but if I didn't, I think it's worth adding this information to the docs.
> Also, as part of windows setup, one could have a batch file that creates
> the necessary firewall rule, whatever that rule is, or add such a batch
> file to the apcupsd etc folder.   Dealing with the windows firewall was
> easily the most time consuming part of the installation.   Thank you.
>
>