[arm-allstar] Allmon

[Doug Crompton]

Would you not also have to allow general access to the manager(s) on the
various servers? The accessing system has to use the port and IP address of
the manager on the system you want to monitor. Thus I think you would need
to setup the manager.conf on the monitored system to allow access. In that
case the line bindaaddr=0.0.0.0 would need to be uncommented on his BBB.

The manager is not very secure but unless you port forward it  - typically
5038 - and you are behind a router and use it only locally it should not be
a problem.

 [general]

displaysystemname =
yes
enabled =
yes
;webenabled =
yes
port =
5038


;httptimeout =
60
; a) httptimeout sets the Max-Age of the http
cookie
; b) httptimeout is the amount of time the webserver
waits
;    on a action=waitevent request (actually its
httptimeout-10)
; c) httptimeout is also the amount of time the webserver
keeps
;    a http session alive after completing a successful
action


bindaddr = 127.0.0.1   ; Local interface
only!
;bindaddr = 0.0.0.0    ; Not secure
;



*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Mon, May 1, 2017 at 12:02 PM, "Larry via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi ken.
>
> Here is a sample of my "allmon.ini.php" this needs to be on the server
> that is doing the node monitoring of other nodes.
>
> This server monitors a group of my other nodes. I thought it might help
> with an example of what the Allmon2 server needs in order to log into the
> other nodes Asterick manager.
>
> I have removed the password but it needs to match the Asterisk Manager
> login you set on each of the other node if on different servers.
> Also ... Each server needs to have its own port number assigned as you
> will note in the "host" settings below.
>
> Doug was correct in his reply I just thought a picture of the process
> might help.
>
> Larry - N7FM
> ----------------------------------
> File: allmon.ini.php
>
> <?php
> [About]
> url=about.php
> [41880]
> host=127.0.0.1:5038
> user=admin
> passwd=xxxxxx
> menu=yes
> hideNodeURL=no
>
> :[41879]
> ;host=192.168.9.38:5033
> ;user=admin
> ;passwd=xxxxxx
> ;menu=nyes
> ;hideNodeURL=no
>
> [28162]
> host=192.168.9.68:5037
> user=admin
> passwd=xxxxxx
> menu=nyes
> hideNodeURL=no
>
> [28358]
> host=192.168.9.68:5037
> user=admin
> passwd=xxxxxxx
> menu=no
> hideNodeURL=no
>
> [41473]
> host=192.168.9.68:5037
> user=admin
> passwd=xxxxxxxx
> menu=nyes
> hideNodeURL=no
>
> [29018]
> host=192.168.9.50:5036
> user=admin
> passwd=
> menu=no
> hideNodeURL=no
>
>
>
>
> On 05/01/2017 05:58 AM, "Ken via arm-allstar" wrote:
>
>> Hi Kevin,
>>
>> Just tried your suggestion and unfortunately it didn't make any
>> difference,
>> I still get Could not connect to Asterisk Manager.
>> I did restart asterick   with astres.sh
>>
>> Regards
>> Ken
>>
>> -----Original Message-----
>> From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
>> "Kevin Walsh via arm-allstar"
>> Sent: 01 May 2017 12:25
>> To: ARM Allstar <arm-allstar at hamvoip.org>
>> Cc: Kevin Walsh <w8khw1 at gmail.com>
>> Subject: Re: [arm-allstar] Allmon
>>
>> Hi Ken,
>>
>> On your new Raspberry Pi node, go to the /etc/asterisk directory and edit
>> the "manager.conf" file. Scroll down in the file until you find the
>> following two lines:
>>
>> bindaddr = 127.0.0.1   ; Local interface only!
>>
>> ;bindaddr = 172.25.36.89    ; Not secure
>>
>> add a semicolon to the beginning of the first line to comment it out. It
>> should look like this:
>>
>> ;bindaddr = 127.0.0.1   ; Local interface only!
>>
>> ;bindaddr = 172.25.36.89    ; Not secure
>>
>> If the passwords match, this should solve your problem.
>>
>> 73,
>>
>> Kevin
>> W8KHW
>>
>> On Mon, May 1, 2017 at 4:13 AM, "Ken via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> Doug,
>>>
>>> My node runs on a BBB and as Allmon doesn't run on a BBB I am using a
>>> Raspberry Pi b as a webserver with Apache and PHP to run Allmon (As
>>> Tim states it doesn't have to be on the same machine as the Allstar)
>>>
>>> Unfortunately the SD card failed as did my backup. So after
>>> reinstalling everything again I can log in to Allmon2 but when I click
>>> on my node number I get the message cannot connect to Allstar Manager
>>>
>>> Working through the "howto" Both ID and passwords are the same in both
>>> Manager and Allmon.ini  IP address is set to 127.0.0.1 Both files look
>>> as they should but it won't connect
>>>
>>> I'm stuck!
>>>
>>> Ken
>>>
>>> -----Original Message-----
>>> From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf
>>> Of "Doug Crompton via arm-allstar"
>>> Sent: 30 April 2017 21:11
>>> To: ARM Allstar <arm-allstar at hamvoip.org>
>>> Cc: Doug Crompton <wa3dsp at gmail.com>
>>> Subject: Re: [arm-allstar] Allmon
>>>
>>>    Ken,
>>>
>>>   I am not sure what you mean by the "first" raspberry Pi. We have only
>>> had code that runs on the Pi2 or Pi3. If you are using either of them
>>> then I strongly suggest you upgrade to the V1.5 code available at
>>> hamvoip.org. It will just work and both allmon2 and supermon are
>>> included.  Version 1.5 has online updates and many enhancements and
>>> bug fixes compared to the original code.
>>>
>>>
>>>
>>> *73 Doug*
>>>
>>> *WA3DSP*
>>>
>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>>
>>> On Sun, Apr 30, 2017 at 1:49 PM, "Ken via arm-allstar" <
>>> arm-allstar at hamvoip.org> wrote:
>>>
>>> Hi Doug,
>>>>
>>>> I'm set up exactly as in the Allmon2 howto. I'm running the Allmon
>>>> on the first raspberry pi with Apache and php as the webserver. My
>>>> Allstar node runs on a BBB so Allmon runs independently
>>>>
>>>> I can log on to Allmon2 but cannot connect to the server. Passwords
>>>> and ID's in both manager and allmon.ini files are identical, ip
>>>> address is 127.0.0.1
>>>>
>>>>
>>>>
>>>> Would Supermon run on its own on the Raspberry pi
>>>>
>>>>
>>>>
>>>> Regards
>>>>
>>>> Ken
>>>>
>>>> _______________________________________________
>>>>
>>>> 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
>>>
>>> _______________________________________________
>>>
>>> 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
>>
>> _______________________________________________
>>
>> 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
>
>