[arm-allstar] Public/Private node connection(s)

[gm4upx at gb7jd.co.uk]

Doug,

That cured the private node problem, I can now see the status from the 
public node(s) Supermon. thanks.

I had read somewhere that if on the same local network, 127.0.0.1 was 
OK.

The two public nodes that connect to each other have 127.0.0.1 as the 
bindaddr.

All nodes have " -A INPUT -p tcp -s 192.168.1.0/16 -i eth0 --dport  5038 
-m state --state NEW -j ACCEPT " in iptables; with a different " 5038 " 
number for each.

I now have two public nodes, bindaddr 127.0.0.1 showing status of 
private node, bindaddr 0.0.0.0

 From private node, bindaddr 0.0.0.0, when logged in to Supermon I can 
show status on one public node, bindaddr 127.0.0.1 but not the other !

This is not a problem as my main Supermon now works as expected, I'm 
just curious as to how I have managed to get the results I am getting.

Regards,
Ian..



> Hello,
> 
> I have downloaded and updated to the most recent version and I would
> like to know if I have Supermon configured correctly.
> 
> I have three RPI's and a x86 on my network.
> 
> Two Rpi's and the x86 are public nodes and one Rpi is private nodes.
> 
> In my main Supermon menu I have added a drop down with public nodes and
> private nodes.
> 
> Clicking on the public nodes shows my public nodes status ( except the
> x86 - I'm not bothered about this at the moment )
> 
> Clicking on the private nodes give a " could not connect to Asterisk
> manager " prompt.
> 
> If I log into Supermon, select a public node and then select connect to
> a private node, I have a connection showing the private node status.
> 
> Is this the correct operation ?  eg: private node status only available
> after login to Supermon ?
> 
> Regards,
> Ian..
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Wed, 29 Aug 2018 19:29:30 -0400
> From: Doug Crompton <wa3dsp at gmail.com>
> To: ARM Allstar <arm-allstar at hamvoip.org>
> Subject: Re: [arm-allstar] Public/Private node connection(s)
> Message-ID:
> 	<CAMp6vssMgAx5EnhBhows63527aGMd6RRii419Xb_nd-wjqhYUQ at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
> Ian,
> 
>   There would be no difference public or private as far as management. 
> It
> sounds like you are not connecting to the private node servers manager 
> with
> supermon - thus the "could not connect to Asterisk manager"  message.  
> Make
> sure the server you cannot connect to has the bindaddr=0.0.0.0 NOT
> 127.0.0.1  in /etc/asterisk/manager.conf and that the password (secret) 
> in
> manager.conf matches the entry in your allmon.ini file for supermon.
> Restart Asterisk when you make changes.
> 
> 
> *73 Doug*
> 
> *WA3DSP*
> 
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>