[AusNOG] TPG Routing: Melbourne to Melbourne Via Brisbane?

Fri Sep 12 07:58:22 EST 2014

Joshua,

Daniel added some important information later last night :-
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

Here is a traceroute from TPG Melbourne (my home ADSL) :-
 3  nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au (203.29.140.50)  41.061 ms
41.978 ms  43.092 ms
 4  nme-sot-tpgn-ppr01-gi-0-1.tpgi.com.au (203.29.140.50)  44.294 ms
46.736 ms  47.130 ms
 5  203-26-30-91.static.tpgi.com.au (203.26.30.91)  49.598 ms  50.475 ms
51.218 ms
 6  bdr-1.vic.au.glonetwork.com.au (1.0.4.76)  55.804 ms  53.214 ms  52.992
ms
 7  103.18.204.4 (103.18.204.4)  54.124 ms  35.252 ms  39.178 ms

To me this indicates the problem is something about the way BigRed are
advertising the routes to TPG (103.18.204.4/X is "right" and
203.27.101.101/Y is "wrong") or that TPG are accepting the BigRed route
advertisement for 103.18.204.4/X but not 203.27.101.101/Y (both should be
routed to the same next hop TPG -> 1.0.4.76).

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).

I think Daniel should check with BigRed that they are advertising
203.27.101.101/Y in exactly the same way as  103.18.204.4/X to TPG, that
there aren't extra ASes prepended for 203.27.101.101/Y, that the route
isn't flapping, that they have used appropriate procedures to advise TPG
that 203.27.101.101/Y is a prefix they can expect to see from BigRed so TPG
don't filter it out, etc.

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.

On 12 September 2014 06:40, Joshua D'Alton <joshua at railgun.com.au> wrote:

> +1, and:
>
> TPG are bringing your DSL all the way to Sydney:
>   3    36 ms    40 ms    36 ms  203-29-138-174.static.tpgi.com.au
> [203.29.138.174]
> Next, they appear to be using Eftel:
> 6    34 ms    39 ms    44 ms  ve4000.bdr01.syd01.eftel.com
> [202.62.152.121]
> Appears to be in Sydney too, however for some reason they haul it to BNE:
> 7 ve46-eth2-1.er01.bne03.eftel.com (14.137.96.74)
> Which they give to Telstra:
>   8    48 ms    47 ms    48 ms
> gigabitethernet3-1.woo7.brisbane.telstra.net [139.130.119.57]
> Appears to be in Brisbane as rDNS and ping indicates.
>
> Telstra then bring it to Sydney (nice of them, but seems the only location
> they get 203.29.138.0/24):
> 13    49 ms    49 ms    49 ms  vocusf.lnk.telstra.net [139.130.73.106]
>
> Where hand it off to:
>
> 15 118.107.189.234 [AS 38803] GoldenIT     (we receive this route from
> GoldenIT in Sydney, you can verify with our LG)
>
> Then  down to Melbourne:
> 17 bdr-1.vic.au.glonetwork.com.au (1.0.4.76) [AS 56203]  (BigRed
> apparently?)
>
> Then you  18 bdr-1.vic.au.sbd.net.au (103.18.204.242) [AS 132839]
> Then 203.27.101.101,  apparently SBDC-AS Small Business Data Company
>
>
> Problems I see here:
> 1. TPG haul it to Sydney (known to happen, LNS capacity issues in Melb?)
> 2. Eftel are giving TPG routes in Sydney which Eftel learned in Brisbane?
> 3. Telstra are giving Eftel routes in Brisbane, which Telstra learned from
> Sydney
>
> Solutions:
> 1. Don't haul to Sydney (even using AAPT LG Melbourne, 203.29.138.17 is
> 15ms away)
> 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?)
>
> 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).
>
>
>
> On Thu, Sep 11, 2014 at 8:38 PM, Nathan Brookfield <
> Nathan.Brookfield at simtronic.com.au> wrote:
>
>>  I would suggest noc at eftel.com, with my 1 second glance it makes 0 sense
>> that they are in this path.
>>
>> Kindest Regards,
>> Nathan Brookfield
>>
>> Chief Executive Officer
>> Simtronic Technologies Pty Ltd
>>
>>  Web: http://simtronic.com.au
>> Phone: 1300 592 330
>> Fax: (02) 4749 4950
>>
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140912/6f2e41a7/attachment.html>