<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">OK, we can slap some extra security on
there. Shouldn't need an extra router for that.<br>
<br>
What about the PtMP story? One of the advantages you mentioned
(Dean) was mobile access. Can it multiplex access somehow?<br>
<br>
--Bart<br>
<br>
<br>
On 4/27/2014 9:53 AM, Dean Gibson AE7Q wrote:<br>
</div>
<blockquote cite="mid:535D3627.7030003@ae7q.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
Exactly (or the equivalent).<br>
<br>
<div class="moz-cite-prefix">On 2014-04-27 09:34, John Hays wrote:<br>
</div>
<blockquote
cite="mid:EBCFEB6E-E247-42FB-98E9-FB69315B6DB1@hays.org"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>It should be on a dedicated router on its own segment. <br>
<br>
Sent from my iPhone</div>
<div><br>
On Apr 27, 2014, at 9:27 AM, Dean Gibson AE7Q <<a
moz-do-not-send="true" href="mailto:hamwan@ae7q.com">hamwan@ae7q.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
The only "authentication" the radio has, are the following:<br>
<ol>
<li>The radio can be set to only receive remote
transmissions that include a two-digit decimal code; <b>or</b></li>
<li>The radio can be set to only receive remote
transmissions that are addressed to the callsign
programmed into the receiving radio (I would recommend
this setting).<br>
</li>
</ol>
Any other authentication would have to be provided by a
router or firewall.<br>
<br>
<div class="moz-cite-prefix">On 2014-04-26 22:39, Bart Kus
wrote:<br>
</div>
<blockquote cite="mid:535C980B.6090504@bartk.us" type="cite">Any
packets on that LAN are considered trusted since they
passed authentication. What's the auth story on the 23cm
modems? <br>
<br>
--Bart <br>
<br>
On 4/26/2014 10:37 PM, Tom Hayward wrote: <br>
<blockquote type="cite">On Sat, Apr 26, 2014 at 9:26 PM,
Dean Gibson AE7Q <a moz-do-not-send="true"
class="moz-txt-link-rfc2396E"
href="mailto:hamwan@ae7q.com"><hamwan@ae7q.com></a>
wrote: <br>
<blockquote type="cite">At the Snohomish County DEM,
place a router (or bridge) between the ID-1 and the
44.24.240.x network. <br>
In this scenario, the ID-1 located at my house would
also be connected to a router that acts as though it
were directly connected to the 44.24.240.x (or any
other) network at the DEM. <br>
</blockquote>
We have a router at Snohomish County DEM with an extra
port that could be used for this. The subnet there is
44.24.240.128/28. We have another subnet of address
pairs set aside for router-to-router links. So as far as
networking goes, we could execute your plan. I can't
commend about the feasibility of any of the other bits.
<br>
<br>
Tom </blockquote>
</blockquote>
</div>
</blockquote>
</blockquote>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
PSDR mailing list
<a class="moz-txt-link-abbreviated" href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a>
<a class="moz-txt-link-freetext" href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
</body>
</html>