<HTML v="urn:schemas-microsoft-com:vml"
o="urn:schemas-microsoft-com:office:office"
w="urn:schemas-microsoft-com:office:word"
m="http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=Generator content="Microsoft Word 12 (filtered medium)">
<STYLE>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-US dir=ltr link=blue vLink=purple>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Allstar wasn’t an option when our repeater was first activated and
ultimately grew into three sites. There is something to be said about each
repeater being able to drop out and connect elsewhere. But that isn’t our
current situation.</DIV>
<DIV> </DIV>
<DIV>As I stated this is partly about $$$. We already have the RC-210’s and need
to question over $1k per site. You cannot run FSCK via SSH if the file system is
really FUBARed. How will you reformat and restore from a back-up without going
to the site? Our sites are at >5k feet and often inaccessible due to snow.
Without KVM/IP you will lose connectivity. I have been a network administrator
for many, many years. Been there; done that. Your point is well taken that a
small OS can be recovered faster than terabytes but only if you can drive to the
site. I remain very hesitant to become PC-based at a remote site.</DIV>
<DIV> </DIV>
<DIV>One point on VM containers. A PC that has multiple or even a single
container [some still call it a node] can have a scheduled backup run to a
remote PC. If the node or even the PC fails it may be restored by issuing a
simple command on the back-up server that would in our case be located in our
data center. No KVM/IP needed in this case; just a second PC running
Linux/Virtuozzo/VMWare. In a CRON one enters vzbackup –Cg –p –e [nodeID][nodeID]
one time unless you alter the config file(s). Restoring is just as easy once a
P2 that finally died has been replaced with another legacy PC just as aged and
long in the tooth. It is one thing to say that the overhead is minimal and that
a P2 will work and still another to use something with a limited supply of spare
parts.</DIV>
<DIV> </DIV>
<DIV>Why such a powerful hub? Because a have a room full of already built server
class PC’s for free. <IMG class="wlEmoticon wlEmoticon-smile"
style="BORDER-TOP-STYLE: none; BORDER-BOTTOM-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none"
alt=Smile src="cid:2784D66BF97E4FDDAB7E3A8D90751CFC@delllaptop"> Add a HDD and
go. Most of the boards don’t have SATA/IDE busses in anticipation of an external
controller that actually could be SATA/SSD. But would you really risk an
out-dated P2 at a remote possibly inaccessible site? But we also would like to
share with others. This is why our preference of RTCM’s. Regardless of a RC-210
controller we can be all Allstar-based without PC’s at remote sites far cheaper
than with. No moving parts.</DIV>
<DIV> </DIV>
<DIV>I think that the initial question has been answered but each of you has
given me things to think about. At this point I am leaning towards using the
RC-210’s rather than selling them on eBay for far less than we paid. <IMG
class="wlEmoticon wlEmoticon-sadsmile"
style="BORDER-TOP-STYLE: none; BORDER-BOTTOM-STYLE: none; BORDER-RIGHT-STYLE: none; BORDER-LEFT-STYLE: none"
alt="Sad smile" src="cid:9370DEAF12A343E6980D76A068260872@delllaptop"> One RTCM,
one node number, X number of repeaters/remote bases. If it doesn’t work we can
change it and add RTCM’s for each repeater.</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=wb3awj@comcast.net
href="mailto:wb3awj@comcast.net">Robert A. Poff</A> </DIV>
<DIV><B>Sent:</B> Saturday, March 21, 2015 1:01 PM</DIV>
<DIV><B>To:</B> <A title=app_rpt-users@ohnosec.org
href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</A> </DIV>
<DIV><B>Subject:</B> Re: [App_rpt-users] Multiple Repeaters Per
Site</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>How
many simultaneous connections are you talking about that you need that kind of
horsepower? <BR><BR>One on the nice things about this software is how relatively
low the overhead is. <BR><BR>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. <BR><BR>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. <BR><BR>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.<BR><BR>My standard setup now is a repeater and a hub on
each box.<BR><BR>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.<BR><BR>No multiple container VM's or
any of that stuff. Define the multiple nodes in the config files.<BR><BR>Nor
have I found the need for an IP KVM.<BR><BR>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.<BR><BR>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.<BR><BR>《/SOAPBOX》<BR><BR><BR>
<DIV class=gmail_quote>On March 21, 2015 1:42:26 PM EDT, "R. Wayne"
<allstar@controlservers.net> wrote:
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>Here’s the price breakdown:</DIV>
<DIV> </DIV>
<DIV>1 PC: $300</DIV>
<DIV>3 URI’s: $297</DIV>
<DIV>1 APC SmartUPS UPS: $500</DIV>
<DIV>1 KVM/IP: $305</DIV>
<DIV> </DIV>
<DIV>==>> $1397</DIV>
<DIV> </DIV>
<DIV>Compared to:</DIV>
<DIV> </DIV>
<DIV>1 Arcom RC-210: $400</DIV>
<DIV>1 RTCM: $269</DIV>
<DIV> </DIV>
<DIV>==>> $669</DIV>
<DIV> </DIV>
<DIV>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.</DIV>
<DIV> </DIV>
<DIV>I’d love to read more ideas.</DIV>
<DIV> </DIV>
<DIV>Wayne @ Node 41660</DIV>
<DIV style="FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: " inline?
DISPLAY: normal; FONT-STYLE: #000000; COLOR: FONT-WEIGHT: calibri?;>
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A title=demoman@rollanet.org
href="mailto:demoman@rollanet.org">Chris Curtis</A> </DIV>
<DIV><B>Sent:</B> Saturday, March 21, 2015 9:26 AM</DIV>
<DIV><B>To:</B> <A title=allstar@controlservers.net
href="mailto:allstar@controlservers.net">'R. Wayne'</A> </DIV>
<DIV><B>Subject:</B> RE: [App_rpt-users] Multiple Repeaters Per
Site</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV style="FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: " inline?
DISPLAY: normal; FONT-STYLE: #000000; COLOR: FONT-WEIGHT: calibri?;>
<DIV class=Section1>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>I used a port on the 210 for IRLP and then later
allstarlink. </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>Works fine. </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>You still need a sound fob in between the PC and
the 210 though. </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>The 210 treats the fob as a radio and the fob
treats the 210 as a radio. </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>210 port </SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: wingdings; COLOR: #1f497d">à</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d? calibri?,?sans-serif?;
color:>fob</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: wingdings; COLOR: #1f497d">ß</SPAN><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d? calibri?,?sans-serif?; color:>
PC </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>No problem at all. </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>Chris </SPAN>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:>KB0WLF </SPAN></P></DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: " #1f497d?
calibri?,?sans-serif?; color:></SPAN>
<DIV
style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 0in; PADDING-LEFT: 4pt; BORDER-LEFT: blue 1.5pt solid; PADDING-RIGHT: 0in">
<DIV>
<DIV
style="BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; PADDING-BOTTOM: 0in; PADDING-TOP: 3pt; PADDING-LEFT: 0in; BORDER-LEFT: medium none; PADDING-RIGHT: 0in">
<P class=MsoNormal><B><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: "
tahoma?,?sans-serif??>From:</SPAN></B><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: " tahoma?,?sans-serif??>
app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org]
<B>On Behalf Of </B>R. Wayne<BR><B>Sent:</B> Saturday, March 21, 2015 10:32
AM<BR><B>To:</B> app_rpt-users@ohnosec.org<BR><B>Subject:</B> Re:
[App_rpt-users] Multiple Repeaters Per Site </SPAN></P></DIV></DIV>
<P class=MsoNormal></P>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-FAMILY: " calibri?,?sans-serif?; color:
black?>But what about using an external controller like a Arcom RC-210?
</SPAN></P></DIV>
<DIV>
<DIV>
<DIV>
<P class=MsoNormal><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: " color: black?
Tahoma?,?sans-serif?;>
</SPAN></P></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV></DIV>
<P
style="MARGIN-BOTTOM: 1em; BORDER-BOTTOM: #000 1px solid; MARGIN-TOP: 2.5em"></P><PRE class=k9mail><HR><BR>App_rpt-users mailing list<BR>App_rpt-users@ohnosec.org<BR><A href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</A><BR><BR>To unsubscribe from this list please visit <A href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</A> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<BR>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. </PRE></BLOCKQUOTE></DIV><BR>--
<BR>Sent from my Android device with K-9 Mail. Please excuse my brevity.
<P>
<HR>
_______________________________________________<BR>App_rpt-users mailing
list<BR>App_rpt-users@ohnosec.org<BR>http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users<BR><BR>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"<BR>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.</DIV></DIV></DIV></BODY></HTML>