[arm-allstar] One Superman session for two nodes

[Ronald Foster]

Thanks Doug.

I have it working with the exception of the lsnodes not showing except for the first node. I’ll work on the that.

Thanks again!

Ron

> On May 13, 2018, at 9:37 AM, Doug Crompton via arm-allstar <arm-allstar at hamvoip.org> wrote:
> 
> Ron,
> 
>  I run one Supermon here which monitors 13 nodes both local and remote.
> Let me try to explain again.
> 
> Here are the cases -
> 
> If a node is local and on the same server as Supermon -
> 
>  You use 127.0.0.1:5038  and the manager is 127.0.0.1. Multiple nodes on
> that same server would use the same setup.
> 
> If a node is on another server but on your same LAN -
> 
>  You use the local LAN IP address to that server like  192.168.1.100:5038.
> In the manager of that (other) node you need  to set the manager to 0.0.0.0
>  No port forwarding would be necessary and as long as you are behind a
> router no firewall as described in the howto.
> 
> If a node is on another server and out somewhere on the Internet -
> 
>  You use the Internet (public) IP address or domain name - like
> 70.34.21.67:5038. Again the manager needs to be set to 0.0.0.0, port 5038
> needs to be forwarded to the Supermon server, and you should use the
> firewall example in the howto to limit 5038 access to just the remote IP
> address.
> 
> Here are three actual examples. Passwords removed and IP address/domain
> changed -
> 
> The node is on the same server as -
> 
> [27225]
> host=127.0.0.1:5038
> user=admin
> passwd=
> menu=yes
> system=Nodes
> hideNodeURL=no
> 
> The node is on another server on the SAME LAN. This node has to have
> manager at 0.0.0.0 -
> 
> [29014]
> host=192.168.0.154:5038
> user=admin
> passwd=
> menu=yes
> system=Nodes
> hideNodeURL=no
> lsnodes="http://192.168.0.154:15501/cgi-bin/lsnodes_web?node=29014"
> 
> Node is on a server out on the Internet using domain name to access. This
> server has to have manager at 0.0.0.0 and port 5038 must be forwarded. Also
> you should firewall after initially testing.
> 
> [40961]
> host=northcapemay.somedomain.com:5038
> user=admin
> passwd=
> menu=yes
> system=Nodes
> hideNodeURL=no
> lsnodes="http://northcapemay.mooo.com/cgi-bin/lsnodes_web?node=40961"
> 
> This is a private node using an IP address out on the Internet. This server
> has manager set to 0.0.0.0, has port 5038 forwarded, and firewall set. Note
> if you wanted to use lsnodes remotely you would also need to forward the
> http port at this server.
> 
> [1601]
> host=109.11.39.132:5038
> user=admin
> passwd=
> menu=yes
> system=Nodes
> hideNodeURL=yes
> lsnodes="http://109.11.39.132/cgi-bin/lsnodes_web?node=1601"
> 
> I would not initiate the firewall for public Internet servers until you
> have checked it without the firewall. Doing so would just complicate things
> in testing and you would not know what was causing the problem. Note if you
> wanted to use lsnodes remotely you would also need to forward the http port
> at this server.
> 
> I hope that answers your questions.
> 
> 
> *73 Doug*
> 
> *WA3DSP*
> 
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> 
> 
> 
> 
> On Sun, May 13, 2018 at 8:01 AM, "Ronald E Foster via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
> 
>> I been trying to configure my two nodes to function properly using one
>> supermon browser session inside my LAN.
>> 
>> I have set the bindaddr=0.0.0.0 in manager.conf on both nodes, but the
>> Supermon 6.0+ How-to procedure, but my understanding is a bit cloudy.
>> 
>> The How-to states to reference the node, Local_IP_address:5038, user, and
>> password for each server in the allmon.ini file. I done this on both
>> servers, but they both cease to work after I’ve completed the change.
>> 
>> It is confusing to me exactly how the Supermon session accesses the second
>> node even when I run separate browser sessions. I can always control the
>> nodes separately,  but the second node listed never responds to a connect
>> command although it appears that a connection is being processed, but fades
>> away with nothing happening.
>> 
>> I believe I’ve tried most all the possible combinations on entering
>> addresses, but none work except the original 127.0.0.1
>> 
>> Thanks.
>> 
>> Ron
>> _______________________________________________
>> 
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>> 
>> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> _______________________________________________
> 
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3 web page - http://hamvoip.org