[AusNOG] Is TPG blocking everything to AS4851?

[Nicholas Meredith]

Thanks Ross,

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.

At a guess at least.

On Tue, Sep 9, 2014 at 8:33 AM, Ross Wheeler <ausnog at rossw.net> wrote:

>
>
>  trace from TPG customer DLS to any of our network currently failing to
>> reach us:
>>
>> traceroute 202.174.105.1
>> 1 192.168.0.1
>> 2 192.168.1.1
>> 3 * * *
>> 4 bri-sot-wic-csw1-gi-1-4.tpgi.com.au (202.7.173.193)
>> 5 203-219-166-67.static.tpgi.com.au (203.219.166.67)
>> 6 * * *
>> ...etc
>>
>
> traceroute to 202.174.105.1 (202.174.105.1), 64 hops max, 40 byte packets
>  3  203-219-100-73.static.tpgi.com.au (203.219.100.73)  2.348 ms
>  4  syd-sot-ken-dom2-be-10.tpgi.com.au (203.219.35.6)  3.341 ms
>  5  syd-sot-ken-dom2-be-10.tpgi.com.au (203.219.35.6)  2.104 ms
>  6  as38809.sydney.pipenetworks.com (218.100.2.93)  3.976 ms
>  7  s-br1-sydn-1.pr1.sydn.nxg.net.au (150.207.240.66)  14.485 ms
>  8  c-20392-1008-VAIES-200-097.cust.nxg.net.au (121.200.228.42)  1.470 ms
>  9  gi0-3950.rtr1.bne1.as4851.net (202.174.96.145)  23.922 ms
> 10  gi1-0-25.agg2.bne1.as4851.net (202.174.96.66)  17.578 ms
> 11  gi0-23.dist-d.bne1.as4851.net (202.174.96.82)  15.210 ms
>
>
> Looks ok from here, passing at least SOME of TPGs network.
>
> RossW
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140909/1700d171/attachment.html>