<div dir="ltr">ARP showing for us, are you still having the ARP problem now?<div><br></div><div><div>24:e9:b3:b7:08:00 218.100.0.12 as7545.brisbane.pipenetwo ge-1/1/1.49 none</div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 9, 2014 at 6:35 PM, Ryan Crouch <span dir="ltr"><<a href="mailto:ryan@apexn.com.au" target="_blank">ryan@apexn.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-AU" link="blue" vlink="purple"><div><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hey Nicholas,</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">I suspect this issue is localised to the PIPE IX in QLD and then only some peers.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">It became obvious we didn't have an ARP record for the TPG peer 218.100.0.12. TPG confirmed they had an ARP entry for us, and resetting interfaces/caches didn't resolve the issue. We had ARP entries for other peers and also route servers - BGP was working fine. When we created a static ARP entry for the TPG peer, it started working. </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">218.100.0.12 resolves to 24e9.b3b7.0800</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Long term this isn't a solution, and I am still waiting for more information as to why this might need to happen after having the connection in place since 2006.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Additionally, I am not sure if we're unable to reach any other peers at this time but many/most look ok but be wary if you implement this work around.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Hopefully this information assists those of you whom are impacted.</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">- Ryan</span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p><p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri","sans-serif""> AusNOG [mailto:<a href="mailto:ausnog-bounces@lists.ausnog.net" target="_blank">ausnog-bounces@lists.ausnog.net</a>] <b>On Behalf Of </b>Nicholas Meredith<br><b>Sent:</b> Tuesday, 9 September 2014 8:37 AM<br><b>To:</b> Ross Wheeler<br><b>Cc:</b> <<a href="mailto:ausnog@ausnog.net" target="_blank">ausnog@ausnog.net</a>><span class=""><br><b>Subject:</b> Re: [AusNOG] Is TPG blocking everything to AS4851?</span></span></p><p class="MsoNormal"> </p><div><p class="MsoNormal">Thanks Ross,</p><div><div class="h5"><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">We are not too confident about restoring our PIPE Peering until TPG advise what policies they have messed up. I'm guessing this has occured because we are transit customers of AAPT, yet TPG seem to have our network over PIPE Peering, and have started dropping transit customer traffic if traversing peering exchanges.</p></div><div><p class="MsoNormal"> </p></div><div><p class="MsoNormal">At a guess at least.</p></div></div></div></div><div><div class="h5"><div><p class="MsoNormal"> </p><div><p class="MsoNormal">On Tue, Sep 9, 2014 at 8:33 AM, Ross Wheeler <<a href="mailto:ausnog@rossw.net" target="_blank">ausnog@rossw.net</a>> wrote:</p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal" style="margin-bottom:12.0pt"> </p><blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal">trace from TPG customer DLS to any of our network currently failing to<br>reach us:<br><br>traceroute 202.174.105.1<br>1 192.168.0.1<br>2 192.168.1.1<br>3 * * *<br>4 <a href="http://bri-sot-wic-csw1-gi-1-4.tpgi.com.au" target="_blank">bri-sot-wic-csw1-gi-1-4.tpgi.com.au</a> (202.7.173.193)<br>5 <a href="http://203-219-166-67.static.tpgi.com.au" target="_blank">203-219-166-67.static.tpgi.com.au</a> (203.219.166.67)<br>6 * * *<br>...etc</p></blockquote><p class="MsoNormal"><br>traceroute to 202.174.105.1 (202.174.105.1), 64 hops max, 40 byte packets<br> 3 <a href="http://203-219-100-73.static.tpgi.com.au" target="_blank">203-219-100-73.static.tpgi.com.au</a> (203.219.100.73) 2.348 ms<br> 4 <a href="http://syd-sot-ken-dom2-be-10.tpgi.com.au" target="_blank">syd-sot-ken-dom2-be-10.tpgi.com.au</a> (203.219.35.6) 3.341 ms<br> 5 <a href="http://syd-sot-ken-dom2-be-10.tpgi.com.au" target="_blank">syd-sot-ken-dom2-be-10.tpgi.com.au</a> (203.219.35.6) 2.104 ms<br> 6 <a href="http://as38809.sydney.pipenetworks.com" target="_blank">as38809.sydney.pipenetworks.com</a> (218.100.2.93) 3.976 ms<br> 7 <a href="http://s-br1-sydn-1.pr1.sydn.nxg.net.au" target="_blank">s-br1-sydn-1.pr1.sydn.nxg.net.au</a> (150.207.240.66) 14.485 ms<br> 8 <a href="http://c-20392-1008-VAIES-200-097.cust.nxg.net.au" target="_blank">c-20392-1008-VAIES-200-097.cust.nxg.net.au</a> (121.200.228.42) 1.470 ms<br> 9 <a href="http://gi0-3950.rtr1.bne1.as4851.net" target="_blank">gi0-3950.rtr1.bne1.as4851.net</a> (202.174.96.145) 23.922 ms<br>10 <a href="http://gi1-0-25.agg2.bne1.as4851.net" target="_blank">gi1-0-25.agg2.bne1.as4851.net</a> (202.174.96.66) 17.578 ms<br>11 <a href="http://gi0-23.dist-d.bne1.as4851.net" target="_blank">gi0-23.dist-d.bne1.as4851.net</a> (202.174.96.82) 15.210 ms<br><br><br>Looks ok from here, passing at least SOME of TPGs network.<br><br>RossW</p></blockquote></div><p class="MsoNormal"> </p></div></div></div></div></div>
</blockquote></div><br></div>