Monitoring a remote mode

Allmon
1

I have setup up supermon (I know, not quite the same, but I think for purposes of this discussion it makes no difference). It runs well on one of my local nodes and from the one login I can monitor the various other nodes on my LAN.

Now I would like to add into the remote nodes I manage, that are accessible over the WAN. I assume this can be done, yes? If not, please let me know and there’s no need to read the rest of this!

The first two remote nodes I am wanting to connect to are on a single network at another person’s QTH. I have forwarded TCP 8081 (and 8082) to each node’s local static IP address (eg. 192.168.1.220). I also forwarded 5038 and 5039 to the respective nodes (both UDP and TCP) - not sure if this was necessary. Please let me know.

I can connect to the allmon instances via a browser using xx.xx.xx.xx:8081/supermon and …:8082/supermon. So far so good.

But soon as I put either of these nodes into my allmon.ini file, not only do they not connect but all my local nodes fail to show up.

My allmon.ini file is below.

I have redacted the passwords, but they are as set for user “admin” in htpasswd in /svr/http/supermon

The remote nodes are 450524 and 450525. Note that I tried with and without the “/supermon” appended to no successes.

[450520] ; This node - NFARC Hub - no radio connected
host=192.168.1.230:5038
user=admin
passwd=*****
menu=yes
hideNodeURL=no

[45053] ; Test Node [this is on the same Pi as 450520]. No radio connected.
host=192.168.1.230:5038
user=admin
passwd=*****
menu=yes
hideNodeURL=no

[51730] ; Canada Hub [sits on it’s own seperate Pi4]
host=192.168.1.231:5039
user=admin
passwd=****
menu=yes
hideNodeURL=no

[450521] ; VE7NZ-220 [sits on its own Pi]
host=192.168.1.220:5040
user=admin
passwd=****
menu=yes
hideNodeURL=no

[450522] ; Future Node [seperate Pi]
host=192.168.1.223:5042
user=admin
passwd=****
menu=yes
hideNodeURL=no

[450523] ; VE7NZ-440 [sits on its own Pi]
host=192.168.1.222:5041
user=admin
passwd=****
menu=yes
hideNodeURL=no

[450524] ; VE7PTF-440 [First remote node - Pi #1]
host=96.55.22.180:8081/supermon
user=admin
passwd=****
menu=yes
hideNodeURL=no

[450525] ; VE7NFR-900 [second remote node Pi#2]
host=96.55.22.180:8082/supermon
user=admin
passwd=****
menu=yes
hideNodeURL=no

[All Nodes]
nodes=450520,45053,450521,450522,450523,450524,450525,51730
menu=yes

[lsNodes]
url="/cgi-bin/lsnodes_web?node=450520"
menu=yes

[IRLP Status]
url=“http://status.irlp.net”
menu=yes

[HAMVOIP]
url=“http://HamVOIP.org”
menu=yes

[Grouped Nodes]
nodes=450520,45053,450521,450522,450523,51730
menu=yes

Thx. Adrian VE7NZ
Also available at node 450520 most of the time if it is easier to talk it over.

2

Hi Adrian,
You’re confusing what is running at each ip/port. In your local file, 192.168.1.230:5038 refers to the IP of your asterisk server running AMI at port 5038. In the case of 95.55.22.180:8081/supermon, that is the IP of the Apache web server running Supermon on port 8081. Your allmon.ini file needs to have the AMI ports of the remote systems, not the Supermon webserver ports. You’ll also need to make sure you are using the AMI credentials, not the Supermon login.
-Jon

3

So does that mean I should use 95.55.22.180:5038 to reach the asterisk server running AMI on port 5038 on the remote network (and :5039 to reach the other node)?

If so, then I assume I also forward 5038 to the local IP address on that network’s router. If so, is it TCP, UDP, or both?

Thanks for the quick and helpful reply!

4

Yes, you link to 95.55.22.180:5038 as you have shown and you only need to forward TCP for it.

5

Also FYI - there can be a few more gotcha’s with setting this up. Make sure the manager.conf file has bindaddr=0.0.0.0 instead of 127.0.0.1. You need this setting to make sure Asterisk is listening for connections from other hosts. Additionally, you may want deny/permit sections defined there to limit what hosts can/cannot connect.

6

I just got the first node working with your advice. I used a bindaddr of 192.168.x.x being the local static IP address of the node and that seems to work ok. Just working on the second node now.