Page 1 of 1

IP address ranges

Posted: Fri Sep 28, 2012 9:34 pm
by localhost
I notice that when I go to the "Change IP" section of the member's facilities, the IP always belongs in 115.70.0.0/16. My problem with that is, reverse routing, especially from Europe, comes in via NTT, which has a tendency to patch Europe-Asia via the US then route traffic back to Australia, instead of routing from the US directly to Australia. Doing a few reverse traces to Exetel's other IP ranges 220.233.0.0/16 and 58.96.0.0/17 show that the routing is much better.

Highly doubting that Exetel can do anything to tell NTT to change its routing policy, is there a specific reason why new IP addresses in the members facilities belong to this range?

Here's a traceroute from a Linode in London to my endpoint, which blocks pings:

Code: Select all

traceroute to 115.70.* (115.70.*), 30 hops max, 60 byte packets
 1  router1-lon.linode.com (212.111.33.229) [AS15830]  0.584 ms  79.910 ms  0.725 ms
 2  212.111.33.233 (212.111.33.233) [AS15830]  0.525 ms  0.414 ms  0.427 ms
 3  te3-1-border76-01.lon2.telecity.net (217.20.44.217) [AS15830]  0.836 ms  0.803 ms *
 4  85.90.238.45 (85.90.238.45) [AS15830]  1.077 ms  0.968 ms  167.293 ms
 5  * * *
 6  ge-0.linx.london03.uk.bb.gin.ntt.net (195.66.224.138) [AS10026/AS4637]  8.091 ms  8.054 ms  7.973 ms
 7  ae-0.r23.londen03.uk.bb.gin.ntt.net (129.250.4.86) [AS2914]  8.139 ms  8.240 ms  8.204 ms
 8  as-0.r22.osakjp01.jp.bb.gin.ntt.net (129.250.5.35) [AS2914]  270.563 ms  273.431 ms  277.992 ms
 9  ae-5.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.221) [AS2914]  282.104 ms  279.897 ms  279.250 ms
10  ae-6.r23.tokyjp01.jp.bb.gin.ntt.net (129.250.3.158) [AS2914]  272.786 ms  274.128 ms  272.332 ms
11  as-2.r05.sydnau01.au.bb.gin.ntt.net (129.250.3.238) [AS2914]  392.045 ms  395.496 ms  394.521 ms
12  xe-1-1-0.a00.sydnau02.au.ra.gin.ntt.net (202.68.64.163) [AS2914]  402.382 ms  408.192 ms  400.682 ms
13  202.68.67.51 (202.68.67.51) [AS9822/AS2914]  394.238 ms  400.519 ms  471.519 ms
14  149.6.96.58.static.exetel.com.au (58.96.6.149) [AS10143]  347.471 ms  346.269 ms  340.728 ms
15  * * *
Comparison trace to sip1.*:

Code: Select all

traceroute to 58.96.1.2 (58.96.1.2), 30 hops max, 60 byte packets
 1  router1-lon.linode.com (212.111.33.229) [AS15830]  0.773 ms  0.976 ms  0.977 ms
 2  212.111.33.233 (212.111.33.233) [AS15830]  0.662 ms  0.937 ms  0.934 ms
 3  * * *
 4  85.90.238.45 (85.90.238.45) [AS15830]  1.057 ms * *
 5  85.90.238.69 (85.90.238.69) [AS15830]  1.324 ms  1.321 ms  1.353 ms
 6  212.113.15.169 (212.113.15.169) [AS9057/AS3356]  1.078 ms  1.048 ms  0.902 ms
 7  vl-3602-ve-226.csw2.London1.Level3.net (4.69.166.149) [AS3356]  146.940 ms  146.966 ms  147.327 ms
 8  ae-59-224.ebr2.London1.Level3.net (4.69.153.141) [AS3356]  138.530 ms  138.262 ms  138.246 ms
 9  ae-43-43.ebr1.NewYork1.Level3.net (4.69.137.74) [AS3356]  138.207 ms  138.222 ms  138.197 ms
10  ae-81-81.csw3.NewYork1.Level3.net (4.69.134.74) [AS3356]  138.274 ms  138.222 ms  138.196 ms
11  ae-82-82.ebr2.NewYork1.Level3.net (4.69.148.41) [AS3356]  137.576 ms  137.712 ms  137.557 ms
12  4.69.135.185 (4.69.135.185) [AS3356]  138.317 ms  138.340 ms  138.371 ms
13  ae-91-91.csw4.SanJose1.Level3.net (4.69.153.14) [AS3356]  141.599 ms  141.522 ms  141.504 ms
14  ae-32-90.car2.SanJose2.Level3.net (4.69.152.204) [AS3356]  214.183 ms  214.103 ms  205.682 ms
15  TELECOM-NEW.car2.SanJose2.Level3.net (4.59.4.94) [AS3356]  138.099 ms  138.104 ms  137.900 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  po6.sglebdist01.aapt.net.au (202.10.14.6) [AS2764]  288.888 ms  289.799 ms  289.772 ms
21  * * *
22  * * *
23  * * *
24  ipll-5017319-154.gw.aapt.com.au (203.174.185.154) [*]  289.736 ms  289.721 ms  289.729 ms
25  57.1.96.58.static.exetel.com.au (58.96.1.57) [AS56106]  309.921 ms  308.997 ms  308.999 ms
26  sip1.exetel.com.au (58.96.1.2) [AS56106]  307.812 ms  298.239 ms  298.274 ms
Comparison trace to http://www.*:

Code: Select all

traceroute to exetel.com.au (220.233.0.9), 30 hops max, 60 byte packets
 1  router1-lon.linode.com (212.111.33.229) [AS15830]  86.172 ms  0.498 ms  34.663 ms
 2  212.111.33.233 (212.111.33.233) [AS15830]  1.258 ms  0.483 ms  0.400 ms
 3  * * *
 4  85.90.238.45 (85.90.238.45) [AS15830]  0.992 ms  0.974 ms  1.009 ms
 5  * 217.20.44.194 (217.20.44.194) [AS15830]  0.910 ms *
 6  ge-0.linx.london03.uk.bb.gin.ntt.net (195.66.224.138) [AS10026/AS4637]  7.939 ms  8.015 ms  7.993 ms
 7  as-0.r22.nycmny01.us.bb.gin.ntt.net (129.250.3.254) [AS2914]  76.236 ms  75.519 ms  75.598 ms
 8  ae-4.r21.sttlwa01.us.bb.gin.ntt.net (129.250.2.51) [AS2914]  157.753 ms  155.114 ms  155.376 ms
 9  ae-0.r20.sttlwa01.us.bb.gin.ntt.net (129.250.2.53) [AS2914]  178.960 ms  160.510 ms  153.053 ms
10  ae-5.r21.snjsca04.us.bb.gin.ntt.net (129.250.3.39) [AS2914]  171.874 ms  167.858 ms  162.903 ms
11  ae-2.r07.snjsca04.us.bb.gin.ntt.net (129.250.5.57) [AS2914]  169.046 ms  176.697 ms  177.715 ms
12  ae-4.r06.plalca01.us.bb.gin.ntt.net (129.250.4.118) [AS2914]  168.419 ms  168.775 ms  177.931 ms
13  xe-0-0-0-1.r06.plalca01.us.ce.gin.ntt.net (140.174.21.18) [AS2914]  159.376 ms  151.845 ms  158.295 ms
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  po6.sglebdist01.aapt.net.au (202.10.14.6) [AS2764]  302.507 ms  309.240 ms  302.077 ms
21  * * *
22  * * *
23  * * *
24  ipll-5017319-154.gw.aapt.com.au (203.174.185.154) [*]  320.278 ms  314.820 ms  308.485 ms
25  139.6.96.58.static.exetel.com.au (58.96.6.139) [AS10143]  309.519 ms  305.261 ms  302.368 ms
26  candlenut-web.exetel.com.au (220.233.0.9) [AS10143/AS4826]  311.775 ms  314.486 ms  305.494 ms
It's still carried by NTT, but it takes a decent physical path.

Trace from my computer:

Code: Select all

  1     1 ms    <1 ms    <1 ms  192.168.1.254
  2    35 ms    35 ms    34 ms  199.1.233.220.static.exetel.com.au [220.233.1.199]
  3    33 ms    34 ms    34 ms  129.6.96.58.static.exetel.com.au [58.96.6.129]
  4    44 ms     *        *     PE-5017319.sclarinte01.gw.aapt.com.au [203.174.185.153]
  5    35 ms    35 ms    35 ms  te3-3.sclardist02.aapt.net.au [203.131.60.32]
  6    52 ms    35 ms    43 ms  te4-2.sglebdist01.aapt.net.au [202.10.12.132]
  7    35 ms    34 ms    35 ms  po6.sglebbrdr01.aapt.net.au [202.10.14.7]
  8    46 ms    41 ms    45 ms  xe7-0-0-420.sebr2.global-gateway.net.nz [202.50.238.213]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   190 ms   188 ms   188 ms  te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
 13   327 ms   334 ms   327 ms  vlan80.csw3.SanJose1.Level3.net [4.69.152.190]
 14   321 ms   322 ms   322 ms  ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9]
 15   325 ms   321 ms   322 ms  ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
 16   329 ms   324 ms   322 ms  ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]
 17   327 ms   326 ms   327 ms  ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69]
 18   323 ms   322 ms   324 ms  ae-41-41.ebr2.London1.Level3.net [4.69.137.65]
 19   324 ms   326 ms   322 ms  ae-58-223.csw2.London1.Level3.net [4.69.153.138]
 20   323 ms   323 ms   322 ms  ae-228-3604.edge3.London1.Level3.net [4.69.166.158]
 21   384 ms   383 ms   384 ms  212.113.15.170
 22   367 ms   366 ms   367 ms  85.90.238.66
 23     *        *        *     Request timed out.
 24   375 ms   374 ms   374 ms  te4-1-dist65-01.lon10.telecity.net [217.20.44.218]
 25   378 ms   371 ms   383 ms  212.111.33.234
 26     *        *        *     Request timed out.
At hop 21, the latency inflates, indicating that the reverse route is most likely NTT's. It would also be safe to assume that hops 13-20 are inflated because of MPLS.

Re: IP address ranges

Posted: Fri Sep 28, 2012 10:19 pm
by ShaminG
localhost wrote:I notice that when I go to the "Change IP" section of the member's facilities, the IP always belongs in 115.70.0.0/16. My problem with that is, reverse routing, especially from Europe, comes in via NTT, which has a tendency to patch Europe-Asia via the US then route traffic back to Australia, instead of routing from the US directly to Australia. Doing a few reverse traces to Exetel's other IP ranges 220.233.0.0/16 and 58.96.0.0/17 show that the routing is much better.
If required, we could assign you a 220.233.x.x range IP. Please confirm whether you wish go ahead with the IP change.

Re: IP address ranges

Posted: Sat Sep 29, 2012 1:22 pm
by localhost
If it is at no cost, then I would like to be moved to a 220.233.x.x IP. Thanks

Re: IP address ranges

Posted: Sat Sep 29, 2012 2:16 pm
by EroshanJ
localhost wrote:If it is at no cost, then I would like to be moved to a 220.233.x.x IP. Thanks
I have changed your IP address to 220.233 range :D

Please power cycle the modem in order for this change to take effect.

Re: IP address ranges

Posted: Sat Sep 29, 2012 3:58 pm
by localhost
All good! Thanks a lot.