<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body smarttemplateinserted="true">
<div class="moz-cite-prefix">A customer of mine has had the same
issue with a TW-connected site in Ohio and another in PA. One VPN
tunnel works fine, the other has one-way ISAKMP traffic to the
other head-end, which connects to Level3. A traceroute shows the
failing path includes 66.109.7.162. The failing direction is from
the PA/OH sites toward the L3 head end. Full-size pings work
fine. It's the UDP/500 that vanishes. I.E., it has nothing to do
with MTU.<br>
<br>
Both started having the issue around Aug 26. Mysteriously, every
week to 10 days, the broken path will start working for a while.
This is usually shortly after midnight EDT; they go back down 1-3
hours later and stay down. The log entries for the two sites
match within seconds.<br>
<br>
The customer's contract is with Comcast Business so it's been
difficult to get to someone clueful about this symptom in TW.<br>
<br>
-Marty<br>
<br>
On 10/15/2019 8:04 AM, Biddle, Josh via Outages wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BN8PR07MB6836EBDBA350111C04D39482C0930@BN8PR07MB6836.namprd07.prod.outlook.com">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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]-->
<div class="WordSection1">
<p class="MsoNormal">Found a thread in the Spectrum forums
talking about the issue finally – it was marked as resolved so
I started a new one.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><a
href="https://forums.timewarnercable.com/t5/Connectivity/Traffic-issues-at-66-109-7-162/m-p/164091#M53497"
moz-do-not-send="true">https://forums.timewarnercable.com/t5/Connectivity/Traffic-issues-at-66-109-7-162/m-p/164091#M53497</a><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b>From:</b> Outages
<a class="moz-txt-link-rfc2396E" href="mailto:outages-bounces@outages.org"><outages-bounces@outages.org></a> <b>On Behalf Of
</b>Biddle, Josh via Outages<br>
<b>Sent:</b> Sunday, October 13, 2019 12:00 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:outages@outages.org">outages@outages.org</a><br>
<b>Subject:</b> [outages] VPN issues over Spectrum L3
boundaries<o:p></o:p></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">We have several offices over the Ohio and
Pennsylvania area that are experiencing issues passing traffic
over VPN tunnels (specifically, there is always a Spectrum
>< Level 3 interconnect). It is a very strange issue.
The VPN tunnel will actually establish, and if you source your
ping from inside the internal network across the VPN tunnel to
the destination, the traffic gets there and replies, but the
replies never make it back to the original sending point.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Anyone else experiencing any similar issues
like this?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Best Regards,<o:p></o:p></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#005480">Josh</span></b><o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<br>
</div>
</blockquote>
<span class="st4cursor"></span>
</body>
</html>