<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@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;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks Tom, you’re beginning to stir more memories of the conversation. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Part of it is that it comes back to the overall amount of administration. To be honest, other than things that absolutely NEED to be on a public IP, I prefer to have all of the internal assets protected by a firewall – same as your typical household. I realize that firewall rules can be setup to protect public IPs as well as private, but why go to all that extra effort? Your average consumer router takes care of all that, rather than giving and EOC or hospital a dozen IPs that all MUST have administration applied and updated every time the end-user wants to add a widget or make a change. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I can understand it if for example a hospital for some reason wanted to have public web servers on the 44 space, but most EMCOMM uses are pretty standard – we want to hook up a laptop, VOIP phone, or tablet to be able to communicate in a disaster. Very seldom (if ever) would you have inbound IPs needing to be port forwarded or managed, and if so then they can do that on their end-user firewall (Netgear, ‘Tik, or whatever). It still leaves the greater flexibility and capabilities that you outline when needed, but the admins don’t need to be involved UNTIL it is one of those cases. Most EOCs and hospitals don’t host Echolink nodes!<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Another aspect is – why put something critical like an EOC or hospital at risk when it’s not needed. You may have perfectly good firewall rules and configurations on the public / 44 IPs used by laptops or other items within an EOC, but one screw-up snafu’d automation script and those devices are potentially compromised. Not the kind of PR you want to move forward with – particularly when the default “safe” method of having an internal firewall covers that – and transfers the liability to the end-user and not the network admins.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Not sure where that leaves us, but thanks for the discussion. Look forward to getting it ironed out.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Rob<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> PSDR [mailto:psdr-bounces@hamwan.org] <b>On Behalf Of </b>Tom Hayward<br><b>Sent:</b> Sunday, March 5, 2017 5:49 PM<br><b>To:</b> Puget Sound Data Ring<br><b>Subject:</b> Re: [HamWAN PSDR] Metal 5SHPN Network Help<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Rob,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>When you and I were talking about this, the point I was trying to make is, why stop at one? Why do you only want HamWAN on the site router? It's no problem to give you as many addresses as you need to cover all the devices at the site. For instance, we have EOCs with a full public /24 dedicated to end-user devices. There's no need to NAT; we have plenty of addresses available. The benefit of this, in the long run, is that people can add devices in the EOC, hospital, etc., and not have to request port forwarding for apps that require it. We set up the /24 once and then don't have to make changes every time someone wants to add an Echolink node. It just works.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Tom<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Mar 5, 2017 at 5:10 PM, Rob Salsgiver <<a href="mailto:rob@nr3o.com" target="_blank">rob@nr3o.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>Cory,<o:p></o:p></p><div><p class=MsoNormal>This is pretty much the question I had brought up after working with Tom I think when bringing up the Monroe hospital. All I was looking for was to expose the site's router (RB2011 in this case) to grab a public IP similar to a DSL or cable connection. Configuring a public subnet just to have an external IP on an internal router seems to add more administration than would be needed for 90% or more of the sites. Having the firewall configurations being done/updated on a normal basis out at the antenna/metal means you have to GO to the antenns to reaet the router if there are and config snags (been there/done that). Having the user-managed device be inside the building is a LOT more convenient when something goes TU and leaves the antenna router in a more static/stable condition. Please keep me in the loop for what becomes the preferred config for this as I expect to have most of my sites in this situation.<o:p></o:p></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'><br><br>-------- Original message --------<br>From: "Cory (NQ1E)" <<a href="mailto:cory@nq1e.hm" target="_blank">cory@nq1e.hm</a>> <br>Date: 3/5/17 3:56 PM (GMT-08:00) <br>To: Puget Sound Data Ring <<a href="mailto:psdr@hamwan.org" target="_blank">psdr@hamwan.org</a>> <br>Cc: <a href="mailto:netops@hamwan.org" target="_blank">netops@hamwan.org</a> <br>Subject: Re: [HamWAN PSDR] Metal 5SHPN Network Help <o:p></o:p></p><div><p class=MsoNormal>Hi Kyle,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It is possible to bridge your interfaces togtether so your internal router could request a DHCP lease from the sector. However, we would prefer you avoided that.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If you would like public IP addresses to use inside of your network, we can have a subnet of your desired size routed to your modem.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>For help configuring that, please either join us in the IRC chat room (#HamWAN on freenode) or email the ops team directly at: <a href="mailto:netops@hamwan.org" target="_blank">netops@hamwan.org</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Good luck!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>-Cory<o:p></o:p></p></div><div><p class=MsoNormal>NQ1E<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Sun, Mar 5, 2017 at 2:39 PM, Kyle Burgess <<a href="mailto:kd7iyt@gmail.com" target="_blank">kd7iyt@gmail.com</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal>I am trying to figure out the best way to configure my Metal 5SHPn so it acts like a bridge. However, I want to try and do it in a way where it won't disrupt the ability to remotely manage the radio (so the HamWAN team can still access it if need be).<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Ultimately, I would like to have the HamWAN assigned IP handed off to a dedicated interface on my router, just like what your typical ISP would do. That way I can handle any additional routing or NAT via my router, and not on the radio itself.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Any thoughts on the best way to go about that? Would I just simply switch the wireless mode from "station" to "station bridge"? Or would there be more involved to do that?<o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Any assistance would be greatly appreciated!<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards,<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Kyle Burgess<o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br><a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><br>_______________________________________________<br>PSDR mailing list<br><a href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br><a href="http://mail.hamwan.net/mailman/listinfo/psdr" target="_blank">http://mail.hamwan.net/mailman/listinfo/psdr</a><o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>