[arm-allstar] identifying private nodes via public nodes

[Doug Crompton]

Jay,

 An option would be to make them public nodes and if you don't want anyone
to connect directly put in a whitelist of just the nodes that can connect.
The problem is when a node appears in the stats server as active people
expect to be able to connect to it. When they can't they think there is a
problem. This is why I suggest not advertising nodes to the stat server
that ae not connectible.


*73 Doug*

*WA3DSP*

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


On Mon, Jul 9, 2018 at 7:29 PM, "Jay Urish via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Good stuff,
>
> Thanks Doug!
>
> I would generally agree with you, however, the option would still be nice.
> In my configuration, 45941 is a HUB with 3 fobs attached that go to 2
> repeaters and an scom 7330 controller.
>
> There is nothing really secret about what the private nodes are and it
> would be cool to be able to have them at least identified with a text
> label, say "146.60 repeater" or "n5ers remote base" in the bubble charts.
>
>
>
> On 07/09/2018 05:54 PM, "Doug Crompton via arm-allstar" wrote:
>
>> Jay,
>>
>>   The short answer is no but you can add private node information for
>> local
>> use like lsnodes or supermon. This is done in
>> /etc/asterisk/local/privatenodes.txt - privatenodes.readme gives info.
>> This
>> information is appended to the local database of nodes when astdb.php is
>> run and then will display on lsnodes and supermon. Here is an example on
>> one of my nodes -
>>
>> cat /etc/asterisk/local/privatenodes.txt
>>
>> 1600|WA3DSP|Six Meter Repeater RX|Richboro/Warrington, PA
>> 1601|WA3DSP|Six Meter Repeater TX|Richboro/Warrington, PA
>> 1700|WA3DSP|Broadcastify|
>>
>> In general you would not want private node information in a public
>> database. No one can connect to it and it would only be useful to you.
>>
>>
>> *73 Doug*
>>
>> *WA3DSP*
>>
>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>>
>>
>> On Mon, Jul 9, 2018 at 6:33 PM, "Jay Urish via arm-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>>
>> Doug,
>>>
>>> I have 3 private nodes hanging off of my hub node 45941. When you look a
>>> the bubble chart, the private nodes are pink colored andnot in the
>>> database. Is there are way to have the parent node provide information to
>>> the reg server to populate the bubble chart?
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> 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
>