[AusNOG] TPG Routing: Melbourne to Melbourne Via Brisbane?
Greg Lipschitz
Greg at thesummitgroup.com.au
Thu Sep 11 21:29:25 EST 2014
Hi Daniel,
You're misunderstanding... Not bashing you at all. You seem to think that anyone who questions you or passes comment that is beyond your belief or understanding is "Bashing Daniel". Settle down fella, the world really isn't against you. :)
Back to square one - You are a having an issue as a customer of a residential ISP.
Regardless of whether the fault is a core network fault or you've found the cure for cancer in your telephone jack - You're logging the fault as a residential DSL customer.
Yes, I understand that you believe the issue is deeper within the internet cosmos - but regardless of all of this, if you want to log a fault on your DSL service, you need to follow the processes to do so. ISP's have escalation processes in place for exactly these sorts of circumstances, but, only once you've logged a fault.
If you're a direct customer of AAPT for transit and you've got an issue with your IP Transit, then you follow the process and log a fault in Frontier right?
If you're a direct customer of Vocus for transit and you've got an issue with your Dark Fibre, then you follow the process and log a fault in the Portal, right?
Then as a direct customer of TPG for your DSL service, if you've got an issue you need to follow the process and log a fault.
That's my point, my only point, follow the support process, clear as mud- no bashing Daniel. :)
We all have processes to make our businesses run more efficiently, we all require our customers to log faults and follow our processes for faults. Why as people running the ISP's do we think that we should be able to bypass the systems??? We're really not that special you know! :P
Just think, you may be doing them a favour by logging a fault as no one may have noticed a bigger issue and you can alert them to the fact they are having an issue??? This is exactly the point of logging tickets :)
I can see The Age headlines now - "Man Logs Ticket, Internet lives to see another day!"
Now go log a ticket! :P
[g]
________________________________
From: Daniel Watson [Daniel at glovine.com.au]
Sent: Thursday, 11 September 2014 9:00 PM
To: Greg Lipschitz; ausnog at ausnog.net
Subject: RE: TPG Routing: Melbourne to Melbourne Via Brisbane?
Greg,
I actually disagree with your entire argument,
If that were the case, then why does this rule not apply to every other tracerouteable issue I see come across this list?
Once again I believe this is turning into another “bash Daniel” thread
If you have an issue with me on this list, then take it to moderation… because funnily enough, I am still on moderation and all my posts have to be approved, and because you see them, they are acceptable to this list
If you also have an issue with the way I go about posting to this list, then I welcome you to email me directly instead of to the entire list and try and humiliate me like this
Now lets all get back on the topic of this thread, because clearly its not a resie issue as ive already pointed out, and for the list’s information ive called TPG and there is no issues in Melbourne which would stop the routing going direct from me to NextDC M1 so nothing there explains the odd routing they have in place at present.
Regards,
Daniel Watson
Network Administrator / Network Operations Manager
E Daniel at GloVine.com.au
W www.GloVine.com.au
From: Greg Lipschitz [mailto:Greg at thesummitgroup.com.au]
Sent: Thursday, 11 September 2014 8:59 PM
To: Daniel Watson; ausnog at ausnog.net
Subject: RE: TPG Routing: Melbourne to Melbourne Via Brisbane?
Sorry to disappoint you Daniel..... If you're on a residential DSL connection, then regardless of whether the issue is a "have your turned it off and turned it on again" or a bigger issue that a helpdesk person may or may not understand, you're still a residential customer that needs to follow the ISP's support process to get resolution to your "issue".
If every person who had an "issue" just posted their "issue" here then this would be nothing different to Whirlpool.
How your ISP routes their traffic is entirely up to them, that's why it's their network - it may be strategic, it may be for financial reasons, a relationship reason or it may be because they're routing around another issue within their network. Just as how you have peering relationships and route traffic on your network is up to you.
If you believe the issue to be with your DSL provider, follow the support process, log a ticket with your provider and go through the motions. If a helpdesk person can't help you in a reasonable period of time (given its a residential connection say 24-72 hours) then request escalation.
Pretty straight forward really.
[g]
________________________________
From: AusNOG [ausnog-bounces at lists.ausnog.net] on behalf of Daniel Watson [Daniel at glovine.com.au]
Sent: Thursday, 11 September 2014 8:21 PM
To: Daniel Watson; ausnog at ausnog.net<mailto:ausnog at ausnog.net>
Subject: Re: [AusNOG] TPG Routing: Melbourne to Melbourne Via Brisbane?
Gday Guys
@David, 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 :d, ill try a back trace and see where it goes for that same network im having the issues with,
@Robert, this clearly isn’t a resie issue.. so they wont help me and id just confuse the hell out of them if I tried :D
Regards,
Daniel Watson
Network Administrator / Network Operations Manager
E Daniel at GloVine.com.au<mailto:Daniel at GloVine.com.au>
W www.GloVine.com.au<http://www.GloVine.com.au>
From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of Daniel Watson
Sent: Thursday, 11 September 2014 7:33 PM
To: ausnog at ausnog.net<mailto:ausnog at ausnog.net>
Subject: [AusNOG] TPG Routing: Melbourne to Melbourne Via Brisbane?
Gday Noggers,
>From my home connection here in Melbourne on TPG, I have just performed another traceroute to 203.27.101.101 however as you will see I am being routed up to Brisbane and then back
C:\Users\danie_000>tracert 203.27.101.101
Tracing route to 203.27.101.101 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 23 ms 23 ms 22 ms 10.20.21.170
3 36 ms 40 ms 36 ms 203-29-138-174.static.tpgi.com.au [203.29.138.17
4]
4 33 ms 35 ms 35 ms 203-29-138-174.static.tpgi.com.au [203.29.138.17
4]
5 34 ms 34 ms 34 ms 203-219-100-74.static.tpgi.com.au [203.219.100.7
4]
6 34 ms 39 ms 44 ms ve4000.bdr01.syd01.eftel.com [202.62.152.121]
7 45 ms 45 ms 45 ms ve46-eth2-1.er01.bne03.eftel.com [14.137.96.74]
8 48 ms 47 ms 48 ms gigabitethernet3-1.woo7.brisbane.telstra.net [13
9.130.119.57]
9 51 ms 48 ms 53 ms tengige0-8-0-7.cha-core4.brisbane.telstra.net [2
03.50.50.1]
10 49 ms 48 ms 49 ms bundle-ether11.ken-core10.sydney.telstra.net [20
3.50.11.72]
11 52 ms 48 ms 49 ms bundle-ether19.ken-core4.sydney.telstra.net [203
.50.11.128]
12 48 ms 50 ms 54 ms tengigabitethernet7-1.ult2.sydney.telstra.net [2
03.50.20.51]
13 49 ms 49 ms 49 ms vocusf.lnk.telstra.net [139.130.73.106]
14 48 ms 48 ms 48 ms as38803.cust.bdr02.syd04.nsw.VOCUS.net.au [175.4
5.73.230]
15 49 ms 47 ms 48 ms 118.107.189.234
16 48 ms 48 ms 48 ms 118.107.188.186
17 49 ms 50 ms 49 ms bdr-1.vic.au.glonetwork.com.au [1.0.4.76]
18 64 ms 66 ms 50 ms bdr-1.vic.au.sbd.net.au [103.18.204.242]
19 52 ms 53 ms 92 ms 203.27.101.101
Trace complete.
I am not sure whom I need to contact in regards to this? My Upstream provider? TPG? Eftel? Vocus or Telstra?
Any information would be greatly appreciated as always
Daniel
ExchangeDefender Message Security: Check Authenticity<https://admin.exchangedefender.com/verify.php?id=s8BAwdLw008942&from=greg@thesummitgroup.com.au>
--
ExchangeDefender Message Security: Click below to verify authenticity
https://admin.exchangedefender.com/verify.php?id=s8BBTVBu017781&from=greg@thesummitgroup.com.au
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20140911/517b8c33/attachment.html>
More information about the AusNOG
mailing list