[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Technical help required to check routing or filtering of Gobal IP routing range: 1.128.0.0 - 1.159.255.255 in the Level 3 Network Space.



http://lookingglass.level3.net/

Should get U what U need.

Robert D. Scott            Robert at ufl.edu
Senior Network Engineer    352-273-0113 Phone
UF Information Technology  352-392-2061 CNS Phone Tree
CNS - Network Services     352-273-0743 FAX
University of Florida      352-294-3571 FLR NOC
Florida Lambda Rail        321-663-0421 Cell
Gainesville, FL  32611     3216630421 at messaging.sprintpcs.com


-----Original Message-----
From: Attila Vekas [mailto:attilavekas at gmail.com] 
Sent: Tuesday, November 20, 2012 1:18 AM
To: NANOG at nanog.org
Subject: Technical help required to check routing or filtering of Gobal IP routing range: 1.128.0.0 - 1.159.255.255 in the Level 3 Network Space.

Hi All,

I need technicial assistance with either a routing or ip restrication
problem impacting our mobile ip customers in Australia.

Customers using our Mobile Network are allocated an address in the
1.128.0.0 - 1.159.255.255 range to allow communication on the internet.

I have a customer's who can't reach websites hosted oversea where the like
cause appears to be some were in the Level 3 routing domain (I suspect).
1. Customer A trying to get www.readingeggs.com.au fails when using a
Mobile Internet connection.

C:\Documents and Settings\c832677>tracert www.readingeggs.com.au



Tracing route to readingeggs.com.au [209.251.186.131]

over a maximum of 30 hops:



  1   458 ms   419 ms   539 ms  10.5.81.50

  2     *        *        *     Request timed out.

  3     *        *        *     Request timed out.

  4   350 ms   659 ms   659 ms  bundle-ether12.pie8.perth.telstra.net[120.151.2
55.17]

  5   578 ms   629 ms   449 ms  bundle-ether1.pie-core1.perth.telstra.net[203.5
0.6.221]

  6   448 ms   509 ms   539 ms  bundle-ether6.way-core4.adelaide.telstra.net[20
3.50.11.16]

 7   457 ms   549 ms   529 ms  bundle-ether9.exi-core1.melbourne.telstra.net[2
03.50.11.93]

  8   468 ms   509 ms   539 ms  bundle-ether12.chw-core2.sydney.telstra.net[203
.50.11.74]

  9   458 ms   709 ms   559 ms  bundle-ether1.oxf-gw2.sydney.telstra.net[203.50
.6.90]

10   448 ms   519 ms   789 ms  203.50.13.174

11   597 ms   759 ms   709 ms  i-0-0-0-0.paix-core01.bx.telstraglobal.net[202.
84.140.145]

12   649 ms   659 ms   730 ms  i-0-0-0-0.eqnx-core01.bi.telstraglobal.net[202.
84.140.142]

13   579 ms   719 ms   709 ms  i-0-0-0-3.eqnx03.bi.telstraglobal.net[202.84.25
1.126]

14   599 ms   689 ms   689 ms  l3-peer.eqnx03.pr.telstraglobal.net[134.159.61.
6]

15   618 ms   689 ms   689 ms  ae-22-70.car2.SanJose1.Level3.net[4.69.152.68]

16     *        *        *     Request timed out.

17     *        *        *     Request timed out.

18     *        *        *     Request timed out.

19     *        *        *     Request timed out.

20     *        *        *     Request timed out.

21     *        *        *     Request timed out.

22     *        *        *     Request timed out.

23     *        *        *     Request timed out.

24     *        *        *     Request timed out.

25     *        *        *     Request timed out.

26     *        *        *     Request timed out.

27     *        *        *     Request timed out.

28     *        *        *     Request timed out.

29     *        *        *     Request timed out.

30     *        *        *     Request timed out.

 Trace complete.
A successful traceroute to www.readingeggs.com is shown below and was
obtained from a fix-line connection to the internet:

C:\Documents and Settings\c832677>tracert www.readingeggs.com.au



Tracing route to readingeggs.com.au [209.251.186.131]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  10.0.0.1

  2     1 ms     1 ms     1 ms
gigabitethernet2-16.lon69.melbourne.telstra.net[139.130.43.29]

  3     4 ms     2 ms     3 ms
bundle-ether3.exi-core1.melbourne.telstra.net [203.50.80.1]

  4    23 ms    23 ms    23 ms  bundle-ether12.chw-core2.sydney.telstra.net[203
.50.11.74]

  5    22 ms    23 ms    23 ms  bundle-ether1.oxf-gw2.sydney.telstra.net[203.50
.6.90]

  6    16 ms    16 ms    16 ms
tengigabitethernet14-0.sydo-core01.sydney.reach.com [203.50.13.42]

  7   159 ms   158 ms   158 ms  i-0-6-2-0.paix-core01.bx.telstraglobal.net[202.
84.140.90]

  8   193 ms   192 ms   192 ms  i-0-7-2-0.eqnx-core01.bi.telstraglobal.net[202.
84.140.30]

  9   193 ms   193 ms   193 ms  i-0-0-0-1.eqnx03.bi.telstraglobal.net[202.84.25
1.50]

10   208 ms   191 ms   208 ms  l3-peer.eqnx03.pr.telstraglobal.net[134.159.61.
6]

11   209 ms   209 ms   209 ms  ae-42-90.car2.SanJose1.Level3.net[4.69.152.196]

12   193 ms   193 ms   193 ms  DATA-RETURN.car2.SanJose1.Level3.net[4.53.18.13
4]

13   234 ms   234 ms   234 ms  t0-0-0-1.br1.stc.terremark.net[66.165.161.169]

14   235 ms   234 ms   234 ms  po14.br1.mia.terremark.net [66.165.160.225]

15   359 ms   248 ms   250 ms  t8-1.gw1.mia.terremark.net [66.165.161.82]

16   234 ms   234 ms   237 ms  66.165.170.14

17   229 ms   229 ms   229 ms  72.46.239.94

18   233 ms   233 ms   232 ms  209.251.186.131



In the above examples the source IP for the failed traceroute from the
Australia's Mobile Network was a 1.126.42.153 address (Telstra) and for the
working

traceroute from the fix-line it was 139.130.43.29.

It appears the path is being treated differently between routers:
ae-22-70.car2.SanJose1.Level3.net [4.69.152.68] &
ae-42-90.car2.SanJose1.Level3.net [4.69.152.196] from the

Telstra Global Router.

I am looking for network help  and confirmation  that the source
network 1.128.0.0
- 1.159.255.255 is being routed correctly back to Telstra's network in
Australia correctly on the

SanJose - Level3 routers. Also check if any bogan filtering is in the
network that could be blocking the source ranges from reaching the hosting
URL.



Regards,

Attila Vekas

Telstra