[App_rpt-users] Multiple Repeaters Per Site

Sat Mar 21 20:01:19 UTC 2015

How many simultaneous connections are you talking about that you need that kind of horsepower? 

One on the nice things about this software is how relatively low the overhead is. 

I have run two usbradio (URI) nodes and a hub on a P4 3.2 GHZ machine with 2 GB of ram, and 80 GB of disk. An IBM Think center Small Form Factor desktop to be exact. 

My first setup here at home was a P2 800 MHZ with 512 MB of RAM, and I think maybe 40GB of disk (that I happened to have on hand). That ran a simplex base and a hub. 

My favorite hardware thus far is a Super Micro Atom D2550 1 RU box, with 4GB of RAM. It now has a 500 GB conventional disk in it. After the SSD that it came with failed one month out of the warranty period. Also using that box for my others to rsync with to backup files.

My standard setup now is a repeater and a hub on each box.

As far as a long time to recover after power failure, hasn't been a problem for me in the last 4-5 years. But then I'm not maintaining terabytes of (un-needed) disk at the sites.

No multiple container VM's or any of that stuff. Define the multiple nodes in the config files.

Nor have I found the need for an IP KVM.

And in a multiple repeater system, it's so very convenient to have them connected via a hub node. Each node in the group can then drop out and connect somewhere else, say for a net or something, without dragging the others along.

I'm about to connect a BBB node to one of our local club's RC-210. So I've read up on the controller. OK, the RC-210 is very capable. But, I think they would have been better off basing the repeater on Allstar to begin with.

《/SOAPBOX》

On March 21, 2015 1:42:26 PM EDT, "R. Wayne" <allstar at controlservers.net> wrote:
>Thank you all for some fresh ideas. I too like the hub idea even though
>it means a Linux server at the repeater site. The problem with Linux at
>a repeater site is power outrages. I work for the hosting company that
>has allowed me to place our high powered hub in a rack (dual Intel
>processors, quad core, 16GB RAM, RAID [ to be replaced with SSD ]) with
>a 100MBit pipe. We will be able to handle a lot of connections. At the
>repeater site we need to make sure that we at least have a UPS
>installed that will give the site owners generator time to come online.
>Otherwise Linux sucks when it scrambles. It may take hours to do a
>FSCK. That means a trip to the site unless we add a KVM over IP device.
>$$$ all the way around.
>
>We have three repeater sites. We have three RC-210’s. I propose adding
>a RTCM on the 4th port of the RC-210 and then port 1 –> 2m port 2 –>
>440 port 3 –> 900.
>
>Here’s the price breakdown:
>
>1 PC: $300
>3 URI’s: $297
>1 APC SmartUPS UPS: $500
>1 KVM/IP: $305
>
>==>> $1397
>
>Compared to:
>
>1 Arcom RC-210: $400
>1 RTCM: $269
>
>==>> $669
>
>The difference here besides the price is that each repeater cannot be
>individually linked via Allstar. But the RC-210 can allow all three
>repeaters to connect to one RTCM. From what Chris Kurtis tells us the
>RC-210 worked out fine.
>
>I’d love to read more ideas.
>
>Wayne @ Node 41660
>
>From: Chris Curtis 
>Sent: Saturday, March 21, 2015 9:26 AM
>To: 'R. Wayne' 
>Subject: RE: [App_rpt-users] Multiple Repeaters Per Site
>
>I used a port on the 210 for IRLP and then later allstarlink.
>
> 
>
>Works fine.
>
> 
>
>You still need a sound fob in between the PC and the 210 though.
>
> 
>
>The 210 treats the fob as a radio and the fob treats the 210 as a
>radio.
>
> 
>
>210 port àfobß PC
>
> 
>
>No problem at all.
>
> 
>
>Chris
>
>KB0WLF
>
> 
>
>From: app_rpt-users-bounces at ohnosec.org
>[mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of R. Wayne
>Sent: Saturday, March 21, 2015 10:32 AM
>To: app_rpt-users at ohnosec.org
>Subject: Re: [App_rpt-users] Multiple Repeaters Per Site
>
> 
>
>But what about using an external controller like a Arcom RC-210?
>
> 
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>App_rpt-users mailing list
>App_rpt-users at ohnosec.org
>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>To unsubscribe from this list please visit
>http://ohnosec.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. 

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150321/815cee5a/attachment.html>