Posted: 10 Mar 2006 18:18
Option c) from R@ge is the best option. We will ALL help you nget it done.......
.gif "::ringadingding::")
Page 5 of 6
Posted: 10 Mar 2006 18:29
^^^^ says the man who hates ONS
Posted: 10 Mar 2006 18:43
gggrrrrrrrrrrrrrr
ffs
ffs
Posted: 11 Mar 2006 00:07
I just find out were is the problem with my bead ping .
Check the page from my post in the whirlpool:
http://forums.whirlpool.net.au/forum-re ... =-1#bottom
Check the page from my post in the whirlpool:
http://forums.whirlpool.net.au/forum-re ... =-1#bottom
Posted: 11 Mar 2006 00:48
Replay from AussieHQ Support :
There appears to be an issue within the Telstra network that is causing traffic to your IP range to be routed via the USA. This would be a routing issue caused by Telstra announcing an incorrect path for your IP range.
Here is the reverse path to your IP range:
traceroute to 149.167.139.211 (149.167.139.211), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.482 ms 0.544 ms 0.356 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
MPLS Label=1190 CoS=0 TTL=0 S=0
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
MPLS Label=18 CoS=0 TTL=0 S=0
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
13 10GigabitEthernet13-0.chw-core2.Sy dney.telstra.net (203.50.6.1) 164.315 ms 164.664 ms 164.597 ms
14 Pos-channel1.cha-core4.Brisbane.te lstra.net (203.50.6.226) 188.010 ms 176.472 ms 176.951 ms
15 TenGigabitEthernet7-1.cha30.Brisba ne.telstra.net (203.50.51.40) 176.936 ms 176.486 ms 177.272 ms
16 telstr269.lnk.telstra.net (139.130.3.134) 178.202 ms 178.351 ms 178.733 ms
17 61.9.209.5 (61.9.209.5) 178.608 ms 178.836 ms 178.520 ms
18 * * *
19 CPE-61-9-211-221.qld.bigpond.net.a u (61.9.211.221) 177.279 ms 177.128 ms 176.973 ms
Regards,
Shaun E
Can you believe This ??
FROM Qld to Syd to USA beck to Brisbane .This make perfect sense to me why my ping is so bad
There appears to be an issue within the Telstra network that is causing traffic to your IP range to be routed via the USA. This would be a routing issue caused by Telstra announcing an incorrect path for your IP range.
Here is the reverse path to your IP range:
traceroute to 149.167.139.211 (149.167.139.211), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.482 ms 0.544 ms 0.356 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
MPLS Label=1190 CoS=0 TTL=0 S=0
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
MPLS Label=18 CoS=0 TTL=0 S=0
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
13 10GigabitEthernet13-0.chw-core2.Sy dney.telstra.net (203.50.6.1) 164.315 ms 164.664 ms 164.597 ms
14 Pos-channel1.cha-core4.Brisbane.te lstra.net (203.50.6.226) 188.010 ms 176.472 ms 176.951 ms
15 TenGigabitEthernet7-1.cha30.Brisba ne.telstra.net (203.50.51.40) 176.936 ms 176.486 ms 177.272 ms
16 telstr269.lnk.telstra.net (139.130.3.134) 178.202 ms 178.351 ms 178.733 ms
17 61.9.209.5 (61.9.209.5) 178.608 ms 178.836 ms 178.520 ms
18 * * *
19 CPE-61-9-211-221.qld.bigpond.net.a u (61.9.211.221) 177.279 ms 177.128 ms 176.973 ms
Regards,
Shaun E
Can you believe This ??
FROM Qld to Syd to USA beck to Brisbane .This make perfect sense to me why my ping is so bad
Posted: 11 Mar 2006 06:50
lol
They will still deny it... heheheheh
lolol dat's sum funny shit man... gone fishing in the U.S of A.
lololol
They will still deny it... heheheheh
lolol dat's sum funny shit man... gone fishing in the U.S of A.
lololol
Posted: 11 Mar 2006 08:05
its probably because you download so much porn from usa the gave you a shorter path to your porn site lolol.
Posted: 11 Mar 2006 09:39
the trials & tribulations of having the male condition, aye? .gif "::notme::")
Posted: 11 Mar 2006 11:41
They will still deny it... heheheheh
They can't deny it
LOok at this TRACERT: i shoow you 2 ip adress . MY and JunkCrusader from whirlpool .
1st the TRACERT from Brisbane to OUTL server :
This one is My:
1,10.204.232.1,7ms,None,0%
2,61.9.211.194,9ms,CPE-61-9-211-19 4.qld.bigpond.net.au,0%
3,61.9.210.3,8ms,CPE-61-9-210-3.ql d.bigpond.net.au,0%
4,139.130.239.249,8ms,GigabitEther net3-3.woo4.Brisbane.telstra.net,0 %
5,203.50.51.129,9ms,GigabitEtherne t6-0.woo-core1.Brisbane.telstra.ne t,0%
6,203.50.6.221,28ms,Pos-channel1.k en-core4.Sydney.telstra.net,0%
7,203.50.20.33,22ms,TenGigabitEthe rnet7-1.ken23.Sydney.telstra.net,0 %
8,139.130.73.50,187ms,pinpoi7.lnk. telstra.net,0%
9,150.101.199.232,187ms,gi0-0.bdr1 .syd6.agile.on.net,0%
10,150.101.120.117,187ms,pos2-0.co r1.cbr1.agile.on.net,0%
11,150.101.195.3,187ms,gs2.mcgoohq .com.au,0
THis one is JunkCrusader :
Tracing route to gs2.mcgoohq.com.au [150.101.195.3] with TTL of 32:
1 0ms 0ms 0ms 192.168.2.1
2 8ms 9ms 8ms 10.204.48.1
3 9ms 8ms 9ms CPE-61-9-211-194.qld.bigpond.net.a u [61.9.211.194]
4 9ms 8ms 8ms CPE-61-9-210-3.qld.bigpond.net.au [61.9.210.3]
5 9ms 10ms 15ms GigEth3-2.woo4.Brisbane.telstra.ne t [139.130.126.5]
6 8ms 7ms 8ms GigabitEthernet6-0.woo-core1.Brisb ane.telstra.net [203.50.51.129]
7 19ms 19ms 22ms Pos-channel1.ken-core4.Sydney.tels tra.net [203.50.6.221]
8 20ms 19ms 20ms TenGigabitEthernet7-1.ken23.Sydney .telstra.net [203.50.20.33]
9 23ms 19ms 26ms pinpoi7.lnk.telstra.net [139.130.73.50]
10 26ms 20ms 21ms gi0-0.bdr1.syd6.agile.on.net [150.101.199.232]
11 24ms 28ms 25ms pos2-0.cor1.cbr1.agile.on.net [150.101.120.117]
12 25ms 27ms 23ms gs2.mcgoohq.com.au [150.101.195.3]
Traceroute complete.
OK and now the Traceroute fron OUTL server to Me:
traceroute to 149.167.139.211 (149.167.139.211), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.482 ms 0.544 ms 0.356 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
MPLS Label=1190 CoS=0 TTL=0 S=0
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
MPLS Label=18 CoS=0 TTL=0 S=0
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
13 10GigabitEthernet13-0.chw-core2.Sy dney.telstra.net (203.50.6.1) 164.315 ms 164.664 ms 164.597 ms
14 Pos-channel1.cha-core4.Brisbane.te lstra.net (203.50.6.226) 188.010 ms 176.472 ms 176.951 ms
15 TenGigabitEthernet7-1.cha30.Brisba ne.telstra.net (203.50.51.40) 176.936 ms 176.486 ms 177.272 ms
16 telstr269.lnk.telstra.net (139.130.3.134) 178.202 ms 178.351 ms 178.733 ms
17 61.9.209.5 (61.9.209.5) 178.608 ms 178.836 ms 178.520 ms
18 * * *
19 CPE-61-9-211-221.qld.bigpond.net.a u (61.9.211.221) 177.279 ms 177.128 ms 176.973 ms
And the Traceroute from OUTL server to JunkCrusader:
traceroute to 60.226.91.12 (60.226.91.12), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.595 ms 0.337 ms 0.447 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 4.624 ms 4.100 ms 4.077 ms
MPLS Label=2822 CoS=0 TTL=0 S=0
3 gi1.cor1.syd7.agile.on.net (150.101.199.237) 4.408 ms 4.317 ms 4.397 ms
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49) 4.742 ms 4.577 ms 4.299 ms
5 10GigabitEthernet15-0.ken-core4.Sy dney.telstra.net (203.50.20.1) 4.375 ms 4.453 ms 4.473 ms
6 Pos-channel1.woo-core1.Brisbane.te lstra.net (203.50.6.222) 15.709 ms 15.617 ms 15.570 ms
7 TenGigabitEthernet9-1.woo2.Brisban e.telstra.net (203.50.51.140) 15.697 ms 15.269 ms 15.279 ms
8 telstr190.lnk.telstra.net (139.130.239.246) 15.578 ms 15.556 ms 15.679 ms
9 CPE-61-9-210-5.qld.bigpond.net.au (61.9.210.5) 15.900 ms 15.714 ms 15.228 ms
10 CPE-61-9-211-212.qld.bigpond.net.a u (61.9.211.212) 16.015 ms 15.841 ms 15.501 ms
11 * * *
THis w hat Shaun E email me last nitge:
There appears to be an issue within the Telstra network that is causing traffic to your IP range to be routed via the USA. This would be a routing issue caused by Telstra announcing an incorrect path for your IP range.
Look's like Telstra f..k Up all customers on the 149.167.xxx.xxx IP address range .
I am on 149.167.xxx.xxx IP address range . So ar many many customers in Brisbane safring because Telstra made a fuckup .NOW sam one is gonna pay for this.GRRRRRRRRR
Posted: 11 Mar 2006 13:16
Now all we need is Nice 
long email to Telstra with the evidence.
Ask them for explanation,plus demand discounts from them ,Till they fix the f..k Up they created.
Demand from them to change IP address range to 60.226.91.xxx .
They got to do sum thing , but wen? i hope something get done soon
long email to Telstra with the evidence.
Ask them for explanation,plus demand discounts from them ,Till they fix the f..k Up they created.
Demand from them to change IP address range to 60.226.91.xxx .
They got to do sum thing , but wen? i hope something get done soon
Posted: 11 Mar 2006 13:20
will a router fix this problem as it will change your ip?
Posted: 11 Mar 2006 13:58
will a router fix this problem as it will change your ip?
Don't think soo ,router will chang my last 6 digits only but not the 1 st 6.Telstra need to change IP address range to 60.226. from 149.167
Posted: 11 Mar 2006 15:29
My last e-mail to Telastra:
Hello
To Telstra Network Technician :
As a loyal Telstra customer I asking for BigPond assistance with routing decisions made by other ISPs.
These decisions appear to be affecting anyone using the 149.167.139.xxx address range(ie multiple BigPond customers). Could you please investigate this as there appear to be many examples of other ISPs making the same bad routing decisions suggesting it is based on routing information provided by Telstra.
I am provide BigPond with the good and bad FORWARD tracert .
>>>>This good Tracing route is from 60.226.91.12 IP address range :<<<<
Tracing route to gs2.mcgoohq.com.au [150.101.195.3] with TTL of 32:
1 0ms 0ms 0ms 192.168.2.1
2 8ms 9ms 8ms 10.204.48.1
3 9ms 8ms 9ms CPE-61-9-211-194.qld.bigpond.net.a u [61.9.211.194]
4 9ms 8ms 8ms CPE-61-9-210-3.qld.bigpond.net.au [61.9.210.3]
5 9ms 10ms 15ms GigEth3-2.woo4.Brisbane.telstra.ne t [139.130.126.5]
6 8ms 7ms 8ms GigabitEthernet6-0.woo-core1.Brisb ane.telstra.net [203.50.51.129]
7 19ms 19ms 22ms Pos-channel1.ken-core4.Sydney.tels tra.net [203.50.6.221]
8 20ms 19ms 20ms TenGigabitEthernet7-1.ken23.Sydney .telstra.net [203.50.20.33]
9 23ms 19ms 26ms pinpoi7.lnk.telstra.net [139.130.73.50]
10 26ms 20ms 21ms gi0-0.bdr1.syd6.agile.on.net [150.101.199.232]
11 24ms 28ms 25ms pos2-0.cor1.cbr1.agile.on.net [150.101.120.117]
12 25ms 27ms 23ms gs2.mcgoohq.com.au [150.101.195.3]
Traceroute complete.
>>>>This bad Tracing route is from My PC 149.167.139.211 IP address range <<<<
1,10.204.232.1,8ms,None,0%
2,61.9.211.194,17ms,CPE-61-9-211-1 94.qld.bigpond.net.au,0%
3,61.9.210.3,17ms,CPE-61-9-210-3.q ld.bigpond.net.au,0%
4,139.130.239.249,8ms,GigabitEther net3-3.woo4.Brisbane.telstra.net,0 %
5,203.50.51.129,22ms,GigabitEthern et6-0.woo-core1.Brisbane.telstra.n et,0%
6,203.50.6.221,20ms,Pos-Channel1.k en-core4.Sydney.telstra.net,0%
7,203.50.20.33,20ms,TenGigabitEthe rnet7-1.ken23.Sydney.telstra.net,0 %
8,139.130.73.50,189ms,pinpoi7.lnk. telstra.net,0%
9,150.101.199.232,205ms,gi0-0.bdr1 .syd6.agile.on.net,0%
10,150.101.120.117,184ms,pos2-0.co r1.cbr1.agile.on.net,0%
11,150.101.195.3,185ms,gs2.mcgoohq .com.au,0%
And now I am provide BigPond with the good and bad REVERSE route,:
>>>>This good REVERSE Tracing route from aussiehq.net.au To 60.226.91.12 <<<<
traceroute to 60.226.91.12 (60.226.91.12), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.595 ms 0.337 ms 0.447 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 4.624 ms 4.100 ms 4.077 ms
MPLS Label=2822 CoS=0 TTL=0 S=0
3 gi1.cor1.syd7.agile.on.net (150.101.199.237) 4.408 ms 4.317 ms 4.397 ms
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49) 4.742 ms 4.577 ms 4.299 ms
5 10GigabitEthernet15-0.ken-core4.Sy dney.telstra.net (203.50.20.1) 4.375 ms 4.453 ms 4.473 ms
6 Pos-channel1.woo-core1.Brisbane.te lstra.net (203.50.6.222) 15.709 ms 15.617 ms 15.570 ms
7 TenGigabitEthernet9-1.woo2.Brisban e.telstra.net (203.50.51.140) 15.697 ms 15.269 ms 15.279 ms
8 telstr190.lnk.telstra.net (139.130.239.246) 15.578 ms 15.556 ms 15.679 ms
9 CPE-61-9-210-5.qld.bigpond.net.au (61.9.210.5) 15.900 ms 15.714 ms 15.228 ms
10 CPE-61-9-211-212.qld.bigpond.net.a u (61.9.211.212) 16.015 ms 15.841 ms 15.501 ms
11 * * *
>>>>This bad Tracing route from aussiehq.net.au To My PC 149.167.139.211<<<<
traceroute to 149.167.139.211 (149.167.139.211), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.482 ms 0.544 ms 0.356 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
MPLS Label=1190 CoS=0 TTL=0 S=0
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
MPLS Label=18 CoS=0 TTL=0 S=0
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
13 10GigabitEthernet13-0.chw-core2.Sy dney.telstra.net (203.50.6.1) 164.315 ms 164.664 ms 164.597 ms
14 Pos-channel1.cha-core4.Brisbane.te lstra.net (203.50.6.226) 188.010 ms 176.472 ms 176.951 ms
15 TenGigabitEthernet7-1.cha30.Brisba ne.telstra.net (203.50.51.40) 176.936 ms 176.486 ms 177.272 ms
16 telstr269.lnk.telstra.net (139.130.3.134) 178.202 ms 178.351 ms 178.733 ms
17 61.9.209.5 (61.9.209.5) 178.608 ms 178.836 ms 178.520 ms
18 * * *
19 CPE-61-9-211-221.qld.bigpond.net.a u (61.9.211.221) 177.279 ms 177.128 ms 176.973 ms
I don't think the problem is in the Telstra network, although the problem may be to do with what information Telstra provide to others about their IP ranges.
Consider this extract from a good route (to 60.226.91.12):
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 4.624 ms 4.100 ms 4.077 ms
3 gi1.cor1.syd7.agile.on.net (150.101.199.237) 4.408 ms 4.317 ms 4.397 ms
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49) 4.742 ms 4.577 ms 4.299 ms
5 10GigabitEthernet15-0.ken-core4.Sy dney.telstra.net (203.50.20.1) 4.375 ms 4.453 ms 4.473 ms
Now, consider the equivalent to My PC (it never quite gets back to the same routers as good route (to 60.226.91.12): but to where it hits the Telstra network again is good enough)
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
To look more specifically at where the bad routing decision is made, the good route:
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118)
3 gi1.cor1.syd7.agile.on.net (150.101.199.237)
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49)
and the bad route:
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118)
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66)
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41)
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154)
A different decision is made by pos1-3.bdr1.syd6.agile.on.net which is then further aggravated by pos2-0.bdr1.sjc2.agile.on.net routing the packet to the US.
So, the wrong decisions are being made in the Agile network.
However, this is probably based on information published by Telstra and is therefore affecting any traffic from outside Telstra to the 149.167.139.xxx subnet.
Could you please investigate this incident,or change my IP address range to ( 60.226.)
This will fix My problem I am currently experiencing.
To put it another way, other ISPs are doing something bad to some BigPond customers and we believe that BigPond may be able to do something about it (in the interest of helping their own customers). Get the angle? The others are the bad guys and we are calling the calvary (BigPond) to protect us. :-)
Regards,
PS:
I am attaching two e-mails from support@aussiehq.com.au ,which i recievsd last nitge.
Hello
To Telstra Network Technician :
As a loyal Telstra customer I asking for BigPond assistance with routing decisions made by other ISPs.
These decisions appear to be affecting anyone using the 149.167.139.xxx address range(ie multiple BigPond customers). Could you please investigate this as there appear to be many examples of other ISPs making the same bad routing decisions suggesting it is based on routing information provided by Telstra.
I am provide BigPond with the good and bad FORWARD tracert .
>>>>This good Tracing route is from 60.226.91.12 IP address range :<<<<
Tracing route to gs2.mcgoohq.com.au [150.101.195.3] with TTL of 32:
1 0ms 0ms 0ms 192.168.2.1
2 8ms 9ms 8ms 10.204.48.1
3 9ms 8ms 9ms CPE-61-9-211-194.qld.bigpond.net.a u [61.9.211.194]
4 9ms 8ms 8ms CPE-61-9-210-3.qld.bigpond.net.au [61.9.210.3]
5 9ms 10ms 15ms GigEth3-2.woo4.Brisbane.telstra.ne t [139.130.126.5]
6 8ms 7ms 8ms GigabitEthernet6-0.woo-core1.Brisb ane.telstra.net [203.50.51.129]
7 19ms 19ms 22ms Pos-channel1.ken-core4.Sydney.tels tra.net [203.50.6.221]
8 20ms 19ms 20ms TenGigabitEthernet7-1.ken23.Sydney .telstra.net [203.50.20.33]
9 23ms 19ms 26ms pinpoi7.lnk.telstra.net [139.130.73.50]
10 26ms 20ms 21ms gi0-0.bdr1.syd6.agile.on.net [150.101.199.232]
11 24ms 28ms 25ms pos2-0.cor1.cbr1.agile.on.net [150.101.120.117]
12 25ms 27ms 23ms gs2.mcgoohq.com.au [150.101.195.3]
Traceroute complete.
>>>>This bad Tracing route is from My PC 149.167.139.211 IP address range <<<<
1,10.204.232.1,8ms,None,0%
2,61.9.211.194,17ms,CPE-61-9-211-1 94.qld.bigpond.net.au,0%
3,61.9.210.3,17ms,CPE-61-9-210-3.q ld.bigpond.net.au,0%
4,139.130.239.249,8ms,GigabitEther net3-3.woo4.Brisbane.telstra.net,0 %
5,203.50.51.129,22ms,GigabitEthern et6-0.woo-core1.Brisbane.telstra.n et,0%
6,203.50.6.221,20ms,Pos-Channel1.k en-core4.Sydney.telstra.net,0%
7,203.50.20.33,20ms,TenGigabitEthe rnet7-1.ken23.Sydney.telstra.net,0 %
8,139.130.73.50,189ms,pinpoi7.lnk. telstra.net,0%
9,150.101.199.232,205ms,gi0-0.bdr1 .syd6.agile.on.net,0%
10,150.101.120.117,184ms,pos2-0.co r1.cbr1.agile.on.net,0%
11,150.101.195.3,185ms,gs2.mcgoohq .com.au,0%
And now I am provide BigPond with the good and bad REVERSE route,:
>>>>This good REVERSE Tracing route from aussiehq.net.au To 60.226.91.12 <<<<
traceroute to 60.226.91.12 (60.226.91.12), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.595 ms 0.337 ms 0.447 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 4.624 ms 4.100 ms 4.077 ms
MPLS Label=2822 CoS=0 TTL=0 S=0
3 gi1.cor1.syd7.agile.on.net (150.101.199.237) 4.408 ms 4.317 ms 4.397 ms
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49) 4.742 ms 4.577 ms 4.299 ms
5 10GigabitEthernet15-0.ken-core4.Sy dney.telstra.net (203.50.20.1) 4.375 ms 4.453 ms 4.473 ms
6 Pos-channel1.woo-core1.Brisbane.te lstra.net (203.50.6.222) 15.709 ms 15.617 ms 15.570 ms
7 TenGigabitEthernet9-1.woo2.Brisban e.telstra.net (203.50.51.140) 15.697 ms 15.269 ms 15.279 ms
8 telstr190.lnk.telstra.net (139.130.239.246) 15.578 ms 15.556 ms 15.679 ms
9 CPE-61-9-210-5.qld.bigpond.net.au (61.9.210.5) 15.900 ms 15.714 ms 15.228 ms
10 CPE-61-9-211-212.qld.bigpond.net.a u (61.9.211.212) 16.015 ms 15.841 ms 15.501 ms
11 * * *
>>>>This bad Tracing route from aussiehq.net.au To My PC 149.167.139.211<<<<
traceroute to 149.167.139.211 (149.167.139.211), 30 hops max, 46 byte packets
1 gw-150-101-195.aussiehq.net.au (150.101.195.30) 0.482 ms 0.544 ms 0.356 ms
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
MPLS Label=1190 CoS=0 TTL=0 S=0
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
MPLS Label=18 CoS=0 TTL=0 S=0
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
13 10GigabitEthernet13-0.chw-core2.Sy dney.telstra.net (203.50.6.1) 164.315 ms 164.664 ms 164.597 ms
14 Pos-channel1.cha-core4.Brisbane.te lstra.net (203.50.6.226) 188.010 ms 176.472 ms 176.951 ms
15 TenGigabitEthernet7-1.cha30.Brisba ne.telstra.net (203.50.51.40) 176.936 ms 176.486 ms 177.272 ms
16 telstr269.lnk.telstra.net (139.130.3.134) 178.202 ms 178.351 ms 178.733 ms
17 61.9.209.5 (61.9.209.5) 178.608 ms 178.836 ms 178.520 ms
18 * * *
19 CPE-61-9-211-221.qld.bigpond.net.a u (61.9.211.221) 177.279 ms 177.128 ms 176.973 ms
I don't think the problem is in the Telstra network, although the problem may be to do with what information Telstra provide to others about their IP ranges.
Consider this extract from a good route (to 60.226.91.12):
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 4.624 ms 4.100 ms 4.077 ms
3 gi1.cor1.syd7.agile.on.net (150.101.199.237) 4.408 ms 4.317 ms 4.397 ms
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49) 4.742 ms 4.577 ms 4.299 ms
5 10GigabitEthernet15-0.ken-core4.Sy dney.telstra.net (203.50.20.1) 4.375 ms 4.453 ms 4.473 ms
Now, consider the equivalent to My PC (it never quite gets back to the same routers as good route (to 60.226.91.12): but to where it hits the Telstra network again is good enough)
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118) 163.476 ms 163.768 ms 163.759 ms
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66) 163.667 ms 163.758 ms 163.549 ms
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41) 163.788 ms 164.158 ms 163.569 ms
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154) 170.025 ms 169.911 ms 169.833 ms
6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 179.208 ms 170.129 ms 170.399 ms
7 so-0-0-0.mpr3.sjc2.us.above.net (64.125.30.1) 172.113 ms 172.393 ms 172.044 ms
8 so-4-0-0.mpr3.pao1.us.above.net (64.125.28.221) 172.812 ms 172.640 ms 172.901 ms
9 i-4-3.paix05.net.reach.com (134.159.62.17) 165.083 ms 164.354 ms 163.976 ms
10 unknown.net.reach.com (202.84.251.97) 163.689 ms 163.855 ms 164.058 ms
11 i-4-0.syd-core04.net.reach.com (202.84.144.153) 164.798 ms 164.207 ms 164.190 ms
12 10GigabitEthernet5-0.oxf-core1.Syd ney.telstra.net (203.50.13.33) 164.405 ms 164.248 ms 164.525 ms
To look more specifically at where the bad routing decision is made, the good route:
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118)
3 gi1.cor1.syd7.agile.on.net (150.101.199.237)
4 FastEthernet2-26.pic2.Sydney.telst ra.net (139.130.73.49)
and the bad route:
2 pos1-3.bdr1.syd6.agile.on.net (150.101.120.118)
3 gi0-1.bdr1.syd7.agile.on.net (150.101.120.66)
4 pos2-0.bdr1.sjc2.agile.on.net (203.16.213.41)
5 490.ge-6-0-0.mpr1.sjc7.us.above.ne t (64.124.57.154)
A different decision is made by pos1-3.bdr1.syd6.agile.on.net which is then further aggravated by pos2-0.bdr1.sjc2.agile.on.net routing the packet to the US.
So, the wrong decisions are being made in the Agile network.
However, this is probably based on information published by Telstra and is therefore affecting any traffic from outside Telstra to the 149.167.139.xxx subnet.
Could you please investigate this incident,or change my IP address range to ( 60.226.)
This will fix My problem I am currently experiencing.
To put it another way, other ISPs are doing something bad to some BigPond customers and we believe that BigPond may be able to do something about it (in the interest of helping their own customers). Get the angle? The others are the bad guys and we are calling the calvary (BigPond) to protect us. :-)
Regards,
PS:
I am attaching two e-mails from support@aussiehq.com.au ,which i recievsd last nitge.
Posted: 11 Mar 2006 17:27
kAoS-Rage wrote:its probably because you download so much porn from usa the gave you a shorter path to your porn site lolol.
Ohh fuck dat is funny
lololol
Posted: 11 Mar 2006 17:37
Could you please investigate this as there appear to be many examples of other ISPs making the same bad routing decisions suggesting it is based on routing information provided by Telstra
They will deny it. You're hypothesizing as to what other ISP's do with the information they provide.
Let's hope they just change you IP range and cut the crap.
I'll cross my fingers for ya.
