<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Look at that, you did say. I just "tl;dr"'ed it.... hahah<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<div></div>
-Ryan<br>
<div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> cisco-voip <cisco-voip-bounces@puck.nether.net> on behalf of Ryan Huff <ryanhuff@outlook.com><br>
<b>Sent:</b> Tuesday, April 30, 2019 12:08 PM<br>
<b>To:</b> Pawlowski, Adam<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Expressway E Firewall Rule Activation</font>
<div> </div>
</div>
<div dir="ltr">
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Adam,</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
I certainly didn't mean to imply the, "Expressway Edge on a Stick" method doesn't work, though out of pure technical curiosity, I would be curious as to what exists in your environment that would make a " single NIC" Expressway Edge deployment more preferred
than "dual NICs" (not that I expect you would or could say). I can think of very few reasons that a single NIC edge would be more ideal than a dual NIC edge (outside of the infosec team just not wanting to screw with the firewall, or production not being able
to sustain a maintenance window); its easier to troubleshoot, easier to install, easier to support and easier to secure.<br>
<br>
Though, I suspect I'm, "preaching to the choir", lol đ. All good my friend.<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Thanks,</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
Ryan<br>
</div>
<div id="x_Signature">
<div>
<div id="x_appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Pawlowski, Adam <ajp26@buffalo.edu><br>
<b>Sent:</b> Tuesday, April 30, 2019 11:36 AM<br>
<b>To:</b> 'Ryan Huff'<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> RE: [cisco-voip] Expressway E Firewall Rule Activation</font>
<div> </div>
</div>
<div lang="EN-US">
<div class="x_x_WordSection1">
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">Ryan,</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">The âtl;drâ is that we were sort of given the recommendation by Cisco to just run it with the single interface given our environment and requirements, and hasnât given us any trouble that I can recall.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">Long story is ⌠</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"><br>
Our environment ends up being the driver for a lot of this, as it is sort of a historic design from the early internet, with just about everything on public address space, and various services and networks secured behind firewalls as needed from internal and
external alike. </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">In the dual interface design, the outside interface sits in a âDMZâ with a firewall, which we donât have available explicitly. There is a border firewall but that isnât really its function. The inside leg has to sit somewhere as
well, which is a place that doesnât exist. </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"><br>
We did have a competitorâs border proxy become compromised in the past due to a software update, and this model where the inside wasnât properly secured â and given our current VMWare topology, creating another zone to hairpin traffic around to separate that
inside interface wasnât in the cards. Not to mention the annoyance of trying to setup split routes on this device to allow some traffic to go in, some to go out, in an environment that is MRA only.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">If you trust the E enough never to be a bad actor, then you could put that interface in the same zone as your other collaboration appliances, like the Expressway C, but, we didnât want to do that either really.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">Given that, we did have a call with Cisco to discuss this, and with representation from the Expressway group they recommended that we stick with the single interface design. That was based on the public addressing (so we could avoid
NAT reflection) and that despite the pipe dream of everyone wanting HD video calling and mobile client access, we didnât see that weâd be pushing that much traffic.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">As it is, the E clusters sit in a collaboration DMZ, where they are independent from any of our other appliances and treated like any other host on our network. Our application firewalls do not allow anything in from the Expressway
E since the C tunnels to it, so really the only thing lacking from a security standpoint there could be containment of that host, but, we chose to guard from it instead.
</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">Since we installed it back on X8.8 or whatever, Iâd noted that rebooting the appliance does not reapply the internal rules, which can easily be forgotten, and would need to be remembered if you run a VMWare HA policy that restarts
the guest. </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">That all being said the worst that we have seen are various SSH attempts (on any port, the zone tunnel, administrative SSH, doesnât matter) until the rules are put back up. We could tighten them on the border once that becomes available
to do so.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">The B2BUA is invoked on calls within the appliances sometimes which can cause some confusion with attempting to read logging if need be, but it hasnât otherwise caused us any trouble.</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D">Adam</span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="color:#1F497D"> </span></p>
<div style="border:none; border-left:solid blue 1.5pt; padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0in 0in 0in">
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<b>From:</b> Ryan Huff <ryanhuff@outlook.com> <br>
<b>Sent:</b> Tuesday, April 30, 2019 10:13 AM<br>
<b>To:</b> Pawlowski, Adam <ajp26@buffalo.edu><br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] Expressway E Firewall Rule Activation</p>
</div>
</div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif; margin-bottom:12.0pt">
That seems odd and not been my experience. Let me ask; why are you using the application firewall rather than the actual firewall (another reason all our edgeâs should be using dual interfaces with LAN1 and LAN2 in their own separate security zones)? Is there
a reason you have to, in other words?<span style="font-size:12.0pt"></span></p>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
Thanks,</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
Ryan</p>
</div>
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif; margin-bottom:12.0pt">
<br>
On Apr 30, 2019, at 08:49, Pawlowski, Adam <<a href="mailto:ajp26@buffalo.edu">ajp26@buffalo.edu</a>> wrote:</p>
</div>
<blockquote style="margin-top:5.0pt; margin-bottom:5.0pt">
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
Figured Iâd also ask this question</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
I note that it seems like any time I reboot an Expressway E, I have to go and re-activate all the firewall rules. They donât seem to activate automatically.
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
Is there something I missed or is this really whatâs necessary?</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
Adam</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
</p>
</div>
</blockquote>
<blockquote style="margin-top:5.0pt; margin-bottom:5.0pt">
<div>
<p class="x_x_MsoNormal" style="margin-top: 0px; margin-bottom: 0px;margin:0in 0in 0.0001pt; font-size:11pt; font-family:"Calibri",sans-serif">
<span style="font-size:12.0pt; font-family:"Times New Roman",serif">_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<a href="https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C0235df01cc3241d45be008d6cd862e3e%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636922373512855537&sdata=rxcl1m7IDBU%2FtkA%2FiRcm3QMAzwcjBo2Jhbg3fEDlu9s%3D&reserved=0" originalsrc="https://puck.nether.net/mailman/listinfo/cisco-voip" shash="tQr+COloVAK0xAwQAhPcIxhRdbHn0gF7zk2CU+NsPTj+rhveY8LFlqhoiWYaxjB5cJgoGjayrPEIdEHUXQVlEW7PkgqXoKmPiGQ8ZIdgrVzu8LDXjGH+te+KKyhp99bAdFefXrzjej8xt06mbiqFAuqdV1H+tNnvHvig8eb3TpI=">https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C3fcc9eb351fe41b70dfc08d6cd6a4a65%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636922253726465693&sdata=72kYzwChhoFD14H6a6mRTn4TdHUcMDcFWrMSXpRo%2Btw%3D&reserved=0</a></span></p>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>