Re: [App_rpt-users] Private Node - Connection Failed - Clarification
I got private to private worked out... thanks!! Before I get myself in too much more trouble with this... - is it possible for a Public node to also be a private node? Say I have Public node 43039 (I do) and it works connecting to and accepting connections among other Public nodes. One and only one radio interface. Can I also make it a private node, for example 1001, and able to accept or initiate connects with another known private node? Somehow I came to believe this is possible... but it could have been the tacos and creme soda messing with me... Perhaps differently - creating a radio-less 'hub' that could 'bridge' public and private? Only one node can be associated with the 'chan_ ..." interface on the same server - yes? no? I'm trying to reduce the footprint (rack and tower space, power suck, etc.) of a multi-site RF-linked system down to repeater + node at each site. Not every site needs to be publicly addressable/connectable - as you can imagine the feedback mess if someone ignorant the construct started re-connecting different sites together making a gnarly set of loops.
On 7/26/18 10:02 PM, Jim Aspinwall No1PC wrote:
Say I have Public node 43039 (I do) and it works connecting to and accepting connections among other Public nodes. One and only one radio interface. Can I also make it a private node, for example 1001, and able to accept or initiate connects with another known private node?
Jim, if you want a node that private nodes can connect to, but also AllStarLink nodes can connect to it too, the easiest way to to make this node a public node number. You define your private nodes on it and also define it on your private nodes. This way you'd have say private node 1004 connecting to public node 40821. Perfectly legal and easy to make play nice. -- Bryan Fields 727-409-1194 - Voice http://bryanfields.net
More or less you are looking for a gateway to the public side of AllStarLink. Any type of node would work on the public node. i.e. hub or radio interface. The private node could connect to your public node. Then the private node would have to pass commands to your public node to get pass it. i.e node 1001 wants to connect to 2000. it would connect to your public node first then pass commands to connect to 2000. Too answer your question about multiple node numbers on a single interface. No, I don't remember more then one node number per interface. Sounds like you are looking for a simple way to register your private nodes for your network. Making your own registration server wouldn't be too hard. Re-configuring your private nodes would be more work then making one file and coping to each private node. I can't remember if #includeifexists statement works with the rpt.conf file. But you could add a small script to download a private node list and restart asterisk. You could also make them all public nodes and try blacklist and whitelist. https://wiki.allstarlink.org/wiki/Blacklist_or_whitelist David KE6UPI On Thu, Jul 26, 2018 at 7:06 PM, Bryan Fields <Bryan@bryanfields.net> wrote:
On 7/26/18 10:02 PM, Jim Aspinwall No1PC wrote:
Say I have Public node 43039 (I do) and it works connecting to and accepting connections among other Public nodes. One and only one radio interface. Can I also make it a private node, for example 1001, and able to accept or initiate connects with another known private node?
Jim, if you want a node that private nodes can connect to, but also AllStarLink nodes can connect to it too, the easiest way to to make this node a public node number.
You define your private nodes on it and also define it on your private nodes. This way you'd have say private node 1004 connecting to public node 40821. Perfectly legal and easy to make play nice.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/ cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Private nodes are unregistered, and do not show up in the RPT external nodes list, hence there is no way for them to discover other nodes or they them unless the path to the other nodes are recorded in each node’s rpt.conf [nodes] stanza, for each node pairs, public and private that are intended for connection. Thanks, Bob K6ECM Sent from iPad
On Jul 27, 2018, at 8:06 AM, David KE6UPI <dshaw@ke6upi.com> wrote:
More or less you are looking for a gateway to the public side of AllStarLink. Any type of node would work on the public node. i.e. hub or radio interface. The private node could connect to your public node. Then the private node would have to pass commands to your public node to get pass it. i.e node 1001 wants to connect to 2000. it would connect to your public node first then pass commands to connect to 2000.
Too answer your question about multiple node numbers on a single interface. No, I don't remember more then one node number per interface.
Sounds like you are looking for a simple way to register your private nodes for your network. Making your own registration server wouldn't be too hard. Re-configuring your private nodes would be more work then making one file and coping to each private node. I can't remember if #includeifexists statement works with the rpt.conf file. But you could add a small script to download a private node list and restart asterisk.
You could also make them all public nodes and try blacklist and whitelist.
https://wiki.allstarlink.org/wiki/Blacklist_or_whitelist
David KE6UPI
On Thu, Jul 26, 2018 at 7:06 PM, Bryan Fields <Bryan@bryanfields.net> wrote: On 7/26/18 10:02 PM, Jim Aspinwall No1PC wrote:
Say I have Public node 43039 (I do) and it works connecting to and accepting connections among other Public nodes. One and only one radio interface. Can I also make it a private node, for example 1001, and able to accept or initiate connects with another known private node?
Jim, if you want a node that private nodes can connect to, but also AllStarLink nodes can connect to it too, the easiest way to to make this node a public node number.
You define your private nodes on it and also define it on your private nodes. This way you'd have say private node 1004 connecting to public node 40821. Perfectly legal and easy to make play nice.
-- Bryan Fields
727-409-1194 - Voice http://bryanfields.net _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
_______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
participants (4)
-
Bob Pyke -
Bryan Fields -
David KE6UPI -
Jim Aspinwall No1PC