<div dir="ltr">Oh I was just diagnosing the path currently being taken, as regardless of BigRed not announcing to TPG (or being accepted, or whatever), the route TPG takes is weird and interesting :)<div><br></div><div>Given the below result from AAPT LG (syd or mel):<div><div><a href="http://103.18.204.0/24">103.18.204.0/24</a>: 7545 56203 132839<br><a href="http://203.27.101.0/24">203.27.101.0/24</a>: 7474 4826 38803 56203 132839 133196<br></div></div><div><br></div><div>I suppose my comment " and trace route from AAPT LG for some reason goes via Optus Syd?" ought to have been more like "... goes via Optus Syd, so actually if not AAPT-Telstra, use AAPT-Optus, like AAPT does?"</div><div><br></div><div>Carry on!</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 12, 2014 at 7:58 AM, David Keegel <span dir="ltr"><<a href="mailto:david.keegel@gmail.com" target="_blank">david.keegel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div>Joshua,<br><br>Daniel added some important information later last night :-<span class=""><br><span style="color:rgb(31,73,125)">103.18.204.4 is on the same network/location
and that routes perfectly fine, straight to tpg all the way in, as we
peer with TPG </span><br><br></span>Here is a traceroute from TPG Melbourne (my home ADSL) :-<br> 3 <a href="http://nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au" target="_blank">nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au</a> (203.29.140.50) 41.061 ms 41.978 ms 43.092 ms<br> 4 <a href="http://nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au" target="_blank">nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au</a> (203.29.140.50) 44.294 ms 46.736 ms 47.130 ms<br> 5 <a href="http://203-26-30-91.static.tpgi.com.au" target="_blank">203-26-30-91.static.tpgi.com.au</a> (203.26.30.91) 49.598 ms 50.475 ms 51.218 ms<br> 6 <a href="http://bdr-1.vic.au.glonetwork.com.au" target="_blank">bdr-1.vic.au.glonetwork.com.au</a> (1.0.4.76) 55.804 ms 53.214 ms 52.992 ms<br> 7 103.18.204.4 (103.18.204.4) 54.124 ms 35.252 ms 39.178 ms<br><br></div>To me this indicates the problem is something about the way BigRed are advertising the routes to TPG (<a href="http://103.18.204.4/X" target="_blank">103.18.204.4/X</a> is "right" and <a href="http://203.27.101.101/Y" target="_blank">203.27.101.101/Y</a> is "wrong") or that TPG are accepting the BigRed route advertisement for <a href="http://103.18.204.4/X" target="_blank">103.18.204.4/X</a> but not <a href="http://203.27.101.101/Y" target="_blank">203.27.101.101/Y</a> (both should be routed to the same next hop TPG -> 1.0.4.76).<br><br></div>I say this problem has nothing to do with Telstra, EFtel, Golden IT or Brisbane. The crux of the issue is that packets for 203.27.101.101 should be flowing TPG -> Big Red direct and they are not, even though the link is up (cf traceroute for 103.18.204.4).<br><br></div>I think Daniel should check with BigRed that they are advertising <a href="http://203.27.101.101/Y" target="_blank">203.27.101.101/Y</a> in exactly the same way as <a href="http://103.18.204.4/X" target="_blank">103.18.204.4/X</a> to TPG, that there aren't extra ASes prepended for <a href="http://203.27.101.101/Y" target="_blank">203.27.101.101/Y</a>, that the route isn't flapping, that they have used appropriate procedures to advise TPG that <a href="http://203.27.101.101/Y" target="_blank">203.27.101.101/Y</a> is a prefix they can expect to see from BigRed so TPG don't filter it out, etc.<br><br></div>If BigRed say they have double checked the route advertisement to TPG etc and everything looks fine, then Daniel can report it to TPG via TPG's residential ADSL help desk where it should be escalated to someone in TPG who can investigate routing.<br><br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 12 September 2014 06:40, Joshua D'Alton <span dir="ltr"><<a href="mailto:joshua@railgun.com.au" target="_blank">joshua@railgun.com.au</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><div dir="ltr">+1, and:<div><br></div><div><div><div>TPG are bringing your DSL all the way to Sydney:</div><span><div> 3 36 ms 40 ms 36 ms <a href="http://203-29-138-174.static.tpgi.com.au" target="_blank">203-29-138-174.static.tpgi.com.au</a> [203.29.138.174]</div></span><div>Next, they appear to be using Eftel:</div><span><div>6 34 ms 39 ms 44 ms <a href="http://ve4000.bdr01.syd01.eftel.com" target="_blank">ve4000.bdr01.syd01.eftel.com</a> [202.62.152.121]</div></span><div>Appears to be in Sydney too, however for some reason they haul it to BNE:</div><div>7 <a href="http://ve46-eth2-1.er01.bne03.eftel.com" target="_blank">ve46-eth2-1.er01.bne03.eftel.com</a> (14.137.96.74)</div><div>Which they give to Telstra:</div><span><div> 8 48 ms 47 ms 48 ms <a href="http://gigabitethernet3-1.woo7.brisbane.telstra.net" target="_blank">gigabitethernet3-1.woo7.brisbane.telstra.net</a> [139.130.119.57]</div></span><div>Appears to be in Brisbane as rDNS and ping indicates.</div><div><br></div><div>Telstra then bring it to Sydney (nice of them, but seems the only location they get <a href="http://203.29.138.0/24" target="_blank">203.29.138.0/24</a>):</div><span>
<div>13 49 ms 49 ms 49 ms <a href="http://vocusf.lnk.telstra.net" target="_blank">vocusf.lnk.telstra.net</a> [139.130.73.106]</div><div><br></div></span><div>Where hand it off to:</div><div><br></div><div>15 118.107.189.234 [AS 38803] GoldenIT (we receive this route from GoldenIT in Sydney, you can verify with our LG)</div><div><br></div><div>Then down to Melbourne:</div><div>17 <a href="http://bdr-1.vic.au.glonetwork.com.au" target="_blank">bdr-1.vic.au.glonetwork.com.au</a> (1.0.4.76) [AS 56203] (BigRed apparently?)</div><div><br></div><div>Then you 18 <a href="http://bdr-1.vic.au.sbd.net.au" target="_blank">bdr-1.vic.au.sbd.net.au</a> (103.18.204.242) [AS 132839] </div><div>Then 203.27.101.101, apparently SBDC-AS Small Business Data Company </div><div><br></div><div><br></div><div>Problems I see here:</div><div>1. TPG haul it to Sydney (known to happen, LNS capacity issues in Melb?)</div><div>2. Eftel are giving TPG routes in Sydney which Eftel learned in Brisbane?</div><div>3. Telstra are giving Eftel routes in Brisbane, which Telstra learned from Sydney</div><div><br></div><div>Solutions:</div><div>1. Don’t haul to Sydney (even using AAPT LG Melbourne, 203.29.138.17 is 15ms away)</div><div>2. If you do, use your AAPT-Telstra port (actually aapt isn’t in the path, and trace route from AAPT LG for some reason goes via Optus Syd?)</div><div><br></div><div>Oh, and probably something for Eftel, but if they only connect with TPG in Brisbane, and perhaps not Telstra in Brisbane, then it could make sense for them to take routes they get from Telstra Sydney to Brisbane, but seems expensive vs getting some connectivity in each state (though I'm pretty sure Eftel do connect to Telstra in Brisbane too, and Melbourne).</div></div><div><br></div><div><br></div></div><span><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 11, 2014 at 8:38 PM, Nathan Brookfield <span dir="ltr"><<a href="mailto:Nathan.Brookfield@simtronic.com.au" target="_blank">Nathan.Brookfield@simtronic.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="auto">
<div>I would suggest <a href="mailto:noc@eftel.com" target="_blank">noc@eftel.com</a>, with my 1 second glance it makes 0 sense that they are in this path.<br>
<br>
<div>Kindest Regards,</div>
Nathan Brookfield
<div><br>
<div>Chief Executive Officer</div>
<div><span style="font-size:13pt">Simtronic Technologies Pty Ltd</span></div>
<div><span style="font-size:13pt"><br>
</span></div>
<div>Web: <a href="http://simtronic.com.au" target="_blank">http://simtronic.com.au</a></div>
<div>Phone: 1300 592 330</div>
<div>Fax: (02) 4749 4950</div></div></div></div></blockquote></div></div></span></div>
<br></div></div><span class="">_______________________________________________<br>
AusNOG mailing list<br>
<a href="mailto:AusNOG@lists.ausnog.net" target="_blank">AusNOG@lists.ausnog.net</a><br>
<a href="http://lists.ausnog.net/mailman/listinfo/ausnog" target="_blank">http://lists.ausnog.net/mailman/listinfo/ausnog</a><br>
<br></span></blockquote></div><br></div>
</blockquote></div><br></div>