<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Which RP2D? K7LWH or NR7SS? I heard you on K7LWH DV-A ...<br>
<br>
Did you read the Icom and/or K5TIT documentation? [Lurkers: that's
my idea of humor ...]<br>
<br>
ps: John: Since an Icom gateway is dual-homed at 10.0.0.2
(Internet gateway 10.0.0.1) and 172.16.0.20, if one wants to put
another box on the local 10.x.x.x network, are there any 10.x.x.x
addresses that are reserved/available for local use, without being
assigned/preempted by the US Trust system? Otherwise, I suppose I
could do port-forwarding on the box into the 172.16.x.x network, and
allocate one there ...<br>
<br>
<div class="moz-cite-prefix">On 2014-04-27 19:02, John D. Hays
wrote:<br>
</div>
<blockquote
cite="mid:CAN77r3xrH0jyrKwUTRNuvXthhDoP8Cx+65V3OJmwKYgoe2TT1A@mail.gmail.com"
type="cite">
<div dir="ltr">BTW, I through a bunch of packets at the RP2D. I
think it was replying but I wasn't able to get IP level
responses.</div>
<div class="gmail_extra"><br clear="all">
<div><br>
<hr>
<div style="float:left;padding-left:1em;color:blue">
John D. Hays<br>
<span style="color:rgb(128,128,128)">K7VE</span></div>
<div style="float:right;text-align:right">PO Box 1223,
Edmonds, WA 98020-1223
<div style="padding-top:0.5em"><a moz-do-not-send="true"
href="http://k7ve.org/blog" target="_blank"><img
moz-do-not-send="true"
src="http://k7ve.org/images/blog-icon-box-red-26.png"></a> <a
moz-do-not-send="true"
href="http://twitter.com/#%21/john_hays" target="_blank"><img
moz-do-not-send="true"
src="http://k7ve.org/images/Twitter-26.png"></a> <a
moz-do-not-send="true"
href="http://www.facebook.com/john.d.hays"
target="_blank"><img moz-do-not-send="true"
src="http://k7ve.org/images/Facebook-26.png"></a></div>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Sun, Apr 27, 2014 at 6:48 PM, Dean
Gibson AE7Q <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:hamwan@ae7q.com" target="_blank">hamwan@ae7q.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> I had to Google to
find out what P2MP was, but in my VERY brief Google
education on the subject, I don't think it applies.<br>
<br>
The radio doesn't multiplex anything.<br>
<br>
The consumer-grade routers I own (Linksys BEFSR41, Netgear
WGT624v2) seem to have no way to turn off NAT. dd-wrt is
not possible with the BEFSR41; it is "work-in-progress"
for the WGT624v2. NAT seems to make routing issues a
little more complex to think through. Both routers have
the ability to specify a "DMZ host", but I think that just
turns on universal NAT to that host. Both routers have
the capability of manually adding entries to a static
routing table, but I don't know if that skips over the
NAT. If we have to have NAT, it seems to me that the best
way to set up the router is with the radio connected to
the LAN side (with whatever private IP address we want),
and have the WAN side connected to the 44.x.x.x network.
That allows incoming (ie, via the radio) packets to go
wherever they can and responses to come back; whereas
orienting the router the other way (unless we use the "DMZ
host" feature) doesn't. I suppose I could donate one of
my (very) elderly (2005) Dell PowerEdge 1650 1U servers to
the effort, but that seems like a bit of overkill ...<br>
<br>
What I think would be a good idea is to meet and discuss
this face-to-face (pretty much anytime) with diagrams,
rather than shoveling eMails back and forth. Scott, if
your schedule permits, you are more than welcome.<span
class="HOEnZb"><font color="#888888"><br>
<br>
-- Dean<br>
</font></span><br>
ps: Scott, I plan to come to the DEM on Tuesday to start
on this, unless you're not going to be there, or other
conditions (like ongoing slide work) make it a bad idea.
<div>
<div class="h5"><br>
<br>
<div>On 2014-04-27 12:06, Bart Kus wrote:<br>
</div>
<blockquote type="cite">
<div>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 type="cite"> Exactly (or the
equivalent).<br>
<br>
<div>On 2014-04-27 09:34, John Hays wrote:<br>
</div>
<blockquote type="cite">
<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"
target="_blank">hamwan@ae7q.com</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div> 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>On 2014-04-26 22:39, Bart Kus wrote:<br>
</div>
<blockquote 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"
href="mailto:hamwan@ae7q.com"
target="_blank"><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 <a
moz-do-not-send="true"
href="tel:44.24.240.128"
value="+14424240128" target="_blank">44.24.240.128</a>/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></fieldset>
<br>
<pre>_______________________________________________
PSDR mailing list
<a moz-do-not-send="true" href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a>
<a moz-do-not-send="true" href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
PSDR mailing list
<a moz-do-not-send="true" href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a>
<a moz-do-not-send="true" href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a moz-do-not-send="true" href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br>
<a moz-do-not-send="true"
href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org"
target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<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>