[arm-allstar] Split site repeater
KD0Q
kd0q at traer.net
Wed Sep 27 09:59:29 EST 2017
OK, Thanks Doug!
73, Glenn - KD0Q
On Tue, Sep 26, 2017 at 11:43 AM, "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> Glenn,
>
> You could have the private and public on the same node at one end. It is
> often done that way. I just thought you want them separate.
>
> You would only want the permanent connect at one end. Although I have never
> tried it I am sure it would cause a confusing situation for Allstar to have
> it at both ends and I don't think it would work. There also would be no
> reason to do that because having it in the startup macro at one end would
> ensure if anything happened short of a system locking up, which would be
> very rare, it would reconnect.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
>
>
> On Tue, Sep 26, 2017 at 11:29 AM, "KD0Q via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > Thanks for the good info Doug!
> >
> > Couple of questions...
> >
> > Is a third node really needed? Could the receiver node be private and
> the
> > transmit/repeater controller node be public and connect to the Allstar
> > network?
> >
> > What happens if both nodes are setup to automatically do a *73 permanent
> > connect to each other at startup?
> >
> > Thanks, Glenn - KD0Q
> >
> > On 9/24/2017 00:03, "Doug Crompton via arm-allstar" wrote:
> >
> >> Glenn,
> >>
> >> As long as you have static or reserved DHCP IP's on both link ends it
> >> is
> >> easy. You can set them up as private nodes. Lets say one was 1500 and
> the
> >> other 1501. They do not need to be registered (no registration lines in
> >> iax.conf) but you do need to put routing information in the [nodes]
> >> stanza
> >> of rpt.conf with IP addresses and ports pointing back to each other. You
> >> also do not do any status updates on either node as this would be
> >> meaningless. The rc.updatenodelist file could be disabled - comment in
> >> /usr/local/etc/rc.allstar and the astdb daily cron update could be
> >> commented in crontab. Once that is setup you should be able to connect
> >> between them. I would use a *73 permanent connect. It probably does not
> >> matter which end initiates the connect whatever is most convenient for
> >> you.
> >> You also should setup a startup_macro at the connection end so it
> connects
> >> automatically at boot.
> >>
> >> Understand that private unregistered nodes can only connect to other
> nodes
> >> that they have specific routing information for and that have specific
> >> routing information back to them. In this case they would be very secure
> >> because not only are they unregistered they also are on a private
> network.
> >> They could only connect to each other.
> >>
> >> This howto explains the [nodes] setup. It would be the same for private
> >> nodes. Just use the correct IP and port for the server you are
> connecting
> >> to.
> >>
> >> https://www.hamvoip.org/multi-server%20howto.pdf
> >>
> >> Note since these are private servers no setup at allstarlink.org is
> >> needed.
> >> You select the IAX ports you want in iax.conf - bindport= You can use
> >> any
> >> port you want. Pick some high 5 digit port to avoid any conflict with
> >> other
> >> Allstar servers. Something like 40000 40001 Just make sure you specify
> >> the port in the routing info IP:port - 192.168.1.200:40000
> >>
> >> If you want to then connect to the Allstar network add another Pi with a
> >> registered node and connect when you want Allstar traffic. Specific
> >> routing
> >> in the [nodes] stanza of rpt.conf would be needed between them.
> >>
> >> It is also important to have stable power. Pi's don't like to be power
> >> cycled quickly and that can sometimes happen on the power grid. A small
> >> UPS
> >> or battery backup would work fine. Some people run them on the car
> >> adapters
> >> 12V to 5V 3A and then you could parallel a battery with diode isolation
> >> and
> >> a charge circuit.
> >>
> >> I hope this addresses you question but it is a little more complex
> >> installation so if you don't understand something please let me know.
> >>
> >>
> >> *73 Doug*
> >>
> >> *WA3DSP*
> >>
> >> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>
> >>
> >>
> >> On Sat, Sep 23, 2017 at 3:57 PM, "KD0Q via arm-allstar" <
> >> arm-allstar at hamvoip.org> wrote:
> >>
> >> Hi Doug,
> >>>
> >>> Both the receiver and the transmit/repeater controller nodes are on the
> >>> same local network and have static, but not public, IP addresses. I
> guess
> >>> the connection between them could (should?) be private.
> >>>
> >>> The transmit/repeater controller node will also have a transceive
> >>> connection to an external Allstar node over the internet.
> >>>
> >>> The repeater will only have audio from the receiver over the Allstar
> >>> link.
> >>>
> >>> Glenn - KD0Q
> >>>
> >>>
> >>> On Sat, Sep 23, 2017 at 11:47 AM, "Doug Crompton via arm-allstar" <
> >>> arm-allstar at hamvoip.org> wrote:
> >>>
> >>> Glenn,
> >>>>
> >>>> A couple of questions. Is this to be a private connection? Are you
> >>>> just
> >>>> using Allstar for the remote link? Do you have any other RF coming in
> to
> >>>> the repeater directly or is this just a receiver connected by Allstar
> >>>> via
> >>>> Internet to a transmitter? Do you want to connect to other Allstar
> nodes
> >>>> besides the remote receiver?
> >>>>
> >>>> Do you have static IP addresses or Dyndns at either or both ends?
> >>>>
> >>>>
> >>>> *73 Doug*
> >>>>
> >>>> *WA3DSP*
> >>>>
> >>>> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>>>
> >>>>
> >>>>
> >>>> On Sat, Sep 23, 2017 at 11:18 AM, "KD0Q-Glenn via arm-allstar" <
> >>>> arm-allstar at hamvoip.org> wrote:
> >>>>
> >>>> I'm working on a split site repeater with a node at the receiver
> linked
> >>>>>
> >>>> to
> >>>>
> >>>>> another node acting as the controller at the transmitter.
> >>>>>
> >>>>> Are there any special configurations I need to make? Any other
> >>>>> suggestions or gotchas?
> >>>>>
> >>>>> Thanks, Glenn - KD0Q
> >>>>>
> >>>>> _______________________________________________
> >>>>>
> >>>>> 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
>
>
More information about the arm-allstar
mailing list