Unable to visit certain websites (depending on IP address)

[GRES]

http://skif.biz

 

[Base122]

freeverse, chroniclesofgeorge and skif all working ok on Virgin Mobile Prepaid with IP address 10.168.93.225 at the moment.

 

[The_Unbeliever]

Will check tonight at home.

Hit me if I forget

By the by, was operating on the 'unrestricted apn' for this weekend, no problems encountered.

 

[The_Unbeliever]

Testing [from restricted APN] indicates that the issue seems to be resolved.

Many thanks to the team!

 

[ginggs]

Testing [from restricted APN] indicates that the issue seems to be resolved.

Err, what was your IP address when you tested, 41.x or 197.x?

 

[Base122]

My unrestricted APN IP addresses always seem to be in the 41.55.x.x range.
Probably the reason why The_Librarian did not have an issue over the weekend.

 

[The_Unbeliever]

Updated :

PPP adapter Cell C:

        Connection-specific DNS Suffix  . :
        IP Address. . . . . . . . . . . . : 41.49.33.82
        Subnet Mask . . . . . . . . . . . : 255.255.255.255
        Default Gateway . . . . . . . . . : 41.49.33.82

Same thing happened to me just now whilst trying to post to chroniclesofgeorge - the dreaded timeout.

This is via the restricted APN.

Back to the drawing board...

 

[The_Unbeliever]

Unrestricted APN gives this IP : 41.55.252.32


Methinks I'll go and play around tonight, see just what the diddle is going on here...

 

[Base122]

Did a bit of testing around this 197.x IP range access issue.

This was a very time consuming and tedious procedure trying to get 197.x range addresses among all the 41.x addresses for testing.

The following 197.x IP addresses DID NOT allow access to the unrestricted APN 41.55.x.x or freeverse.com(but ok on a few other websites tested):
197.104.76.193
197.106.133.103
197.107.1.165
197.106.253.164

The following IP addresses DID allow access to both (and other websites):
197.171.36.76
197.170.74.15
197.168.91.198
197.170.163.1

Can you see the pattern in the second octet of each address?
Wonder why there is a difference in access between the lower and higher second octet ranges?
Is the 197 range divided somehow, with different configs applied?

Hope Cell C's network specialists will be able to make sense of and resolve this, without interfering with the Gtalk, etc. timing issues.

 

[ginggs]

Is the 197 range divided somehow, with different configs applied?

Yes, they are two different netblocks.

Information from AfriNIC's whois database:

inetnum: 197.104.0.0 - 197.107.255.255
netname: CELLC-20110310
descr: 3G Subscribers
country: ZA
admin-c: CC3-AFRINIC
tech-c: CC3-AFRINIC
status: ASSIGNED PA
mnt-by: AFRINIC-HM-MNT
changed: jcameron@cellc.co.za 20110815
source: AFRINIC
parent: 197.104.0.0 - 197.111.255.255

inetnum: 197.168.0.0 - 197.171.255.255
netname: CELLC-20100922
descr: 3G Subscribers
country: ZA
admin-c: CC3-AFRINIC
tech-c: CC3-AFRINIC
status: ASSIGNED PA
mnt-by: AFRINIC-HM-MNT
changed: jcameron@cellc.co.za 20110815
source: AFRINIC
parent: 197.168.0.0 - 197.175.255.255

 

[Cell_C]

Good day All

freeverse.com website is available for use via the 197.x.x. range.
Please can you test and let me know.

Regards
AM~

 

[ginggs]

Current IP address: 197.173.160.48.
http://freeverse.com working
http://www.skif.biz not working (works on iBurst though)

/home/user # tcptraceroute freeverse.com
Selected device gprs0, address 197.173.160.48, port 53672 for outgoing packets
Tracing the path to freeverse.com (216.220.102.10) on TCP port 80 (www), 30 hops max
 1  * * *
 2  41.157.83.14  87.494 ms  79.162 ms  67.871 ms
 3  41.157.83.14  109.131 ms  97.718 ms  99.030 ms
 4  41.157.72.3  98.938 ms  86.609 ms  99.304 ms
 5  41.157.64.3  109.161 ms  97.870 ms  88.989 ms
 6  41.48.253.34  109.405 ms  97.900 ms  89.111 ms
 7  83.231.233.141  319.580 ms  317.474 ms  358.704 ms
 8  ae-1.r02.londen03.uk.bb.gin.ntt.net (129.250.5.25)  328.277 ms  317.810 ms  319.275 ms
 9  xe-0.level3.londen03.uk.bb.gin.ntt.net (129.250.8.138)  338.868 ms  396.424 ms  309.510 ms
10  ae-52-52.csw2.London1.Level3.net (4.69.139.120)  359.497 ms  316.071 ms  318.542 ms
11  ae-57-222.ebr2.London1.Level3.net (4.69.153.133)  308.532 ms  327.759 ms  329.407 ms
12  ae-41-41.ebr1.NewYork1.Level3.net (4.69.137.66)  658.721 ms  396.210 ms  399.445 ms
13  ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66)  428.955 ms  397.735 ms  389.587 ms
14  ae-14-60.car4.NewYork1.Level3.net (4.69.155.6)  420.196 ms  404.724 ms  390.503 ms
15  CO-LOCATION.car4.NewYork1.Level3.net (4.53.92.74)  417.847 ms  406.128 ms  399.078 ms
16  www.freeverse.com (216.220.102.10) [open]  469.452 ms  438.354 ms
    CO-LOCATION.car4.NewYork1.Level3.net (4.53.92.74)  450.195 ms

/home/user # tcptraceroute www.skif.biz
Selected device gprs0, address 197.173.160.48, port 50068 for outgoing packets
Tracing the path to www.skif.biz (88.212.201.105) on TCP port 80 (www), 30 hops max
 1  * * *
 2  41.157.83.14  78.094 ms  76.508 ms  88.287 ms
 3  41.157.83.14  99.457 ms  377.716 ms  89.325 ms
 4  41.157.72.3  139.283 ms  87.372 ms  88.378 ms
 5  41.157.64.3  98.266 ms  120.636 ms  177.918 ms
 6  41.48.253.34  89.478 ms  84.503 ms  99.731 ms
 7  83.231.233.141  319.794 ms  319.061 ms  309.662 ms
 8  ae-1.r02.londen03.uk.bb.gin.ntt.net (129.250.5.25)  329.559 ms  327.515 ms  329.742 ms
 9  te1-4-10G.ar6.LON3.gblx.net (208.50.13.145)  440.491 ms  326.203 ms  440.948 ms
10  ae3-20G.scr3.LON3.gblx.net (67.17.73.94)  419.220 ms  316.101 ms  539.216 ms
11  lag1.ar9.LON3.gblx.net (67.17.72.21)  328.949 ms  314.453 ms  309.997 ms
12  CJSC-SYNTERRA.TenGigabitEthernet9-3.ar9.LON3.gblx.net (208.178.246.218)  368.958 ms  465.576 ms  1183.410 ms
13  * * *
14  83.229.192.186  356.965 ms  375.336 ms  438.019 ms
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *
Destination not reached

 

[ginggs]

On Saturdar, December 17, I tried to visit mybroadband.co.za but the page did not load.

# tcptraceroute mybroadband.co.za
Selected device gprs0, address 41.49.172.7, port 64979 for outgoing packets
Tracing the path to mybroadband.co.za (41.203.21.137) on TCP port 80 (www), 30 hops max
1 * * *
2 41.48.23.1 120.758 ms 76.447 ms 78.827 ms
3 10.228.223.70 88.623 ms 89.203 ms 89.416 ms
4 41.48.16.1 99.121 ms * *
5 41.48.0.3 95.367 ms * *
6 41.48.253.36 91.614 ms * *
7 41.181.47.223 135.895 ms * *
8 rb-cr-2.za--rb-dca-2.za-b.mtnns.net (196.44.0.155) 1915.496 ms * *
9 rb-cr-1.za--rb-cr-2.za-a.mtnns.net (196.44.31.26) 100.067 ms * *
10 196.44.31.97 118.653 ms * *
11 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 97.016 ms * *
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 97.138 ms * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not reached

I disconnected and reconnected and the page loaded fine.

# tcptraceroute mybroadband.co.za
Selected device gprs0, address 197.109.209.1, port 63897 for outgoing packets
Tracing the path to mybroadband.co.za (41.203.21.137) on TCP port 80 (www), 30 hops max
1 * * *
2 41.50.20.33 120.300 ms 127.838 ms 660.950 ms
3 10.220.231.70 887.360 ms 139.191 ms 118.256 ms
4 41.50.16.1 107.331 ms 116.363 ms 86.792 ms
5 41.50.0.3 89.478 ms 77.118 ms 79.224 ms
6 41.48.253.36 250.030 ms 358.307 ms 200.012 ms
7 41.181.47.223 98.023 ms 158.508 ms 86.792 ms
8 rb-cr-2.za--rb-dca-2.za-b.mtnns.net (196.44.0.155) 142.364 ms 126.771 ms 141.205 ms
9 rb-cr-1.za--rb-cr-2.za-a.mtnns.net (196.44.31.26) 149.109 ms 98.236 ms 129.944 ms
10 196.44.31.97 198.120 ms 170.654 ms 197.022 ms
11 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 120.484 ms 95.673 ms 110.474 ms
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 97.962 ms 73.425 ms 86.731 ms
13 core-router1.jnb2.host-h.net (196.30.213.108) 80.902 ms 81.024 ms 88.074 ms
14 41.72.136.53 99.671 ms 99.884 ms 90.576 ms
15 mybroadband.co.za (41.203.21.137) [open] 127.716 ms 105.377 ms
41.72.136.53 89.325 ms

Still some differences between the 41.x and 197.x ranges?

 

[ginggs]

Same problem again this evening around 20:00:

# tcptraceroute mybroadband.co.za
Selected device gprs0, address 41.51.3.129, port 50939 for outgoing packets
Tracing the path to mybroadband.co.za (41.203.21.137) on TCP port 80 (www), 30 hops max
1 * * *
2 41.48.23.33 76.020 ms 74.249 ms 128.479 ms
3 10.228.223.70 98.877 ms 88.868 ms 89.356 ms
4 41.48.16.1 99.487 ms * *
5 * 41.48.0.3 1886.657 ms *
6 41.48.253.36 117.004 ms * *
7 41.181.47.223 95.063 ms * *
8 xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 96.222 ms * *
9 * rb-cr-1.za--rb-cr-2.za-a.mtnns.net (196.44.31.26) 2167.755 ms *
10 196.44.31.97 179.962 ms * *
11 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 766.754 ms * *
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 91.095 ms * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not reached

Second attempt:

# tcptraceroute mybroadband.co.za
Selected device gprs0, address 41.49.254.165, port 65334 for outgoing packets
Tracing the path to mybroadband.co.za (41.203.21.137) on TCP port 80 (www), 30 hops max
1 * * *
2 41.48.23.33 74.219 ms 76.629 ms 79.224 ms
3 10.228.223.70 119.538 ms 99.091 ms 101.136 ms
4 41.48.16.1 117.706 ms * *
5 41.48.0.3 1727.326 ms * *
6 * 41.48.253.36 1727.509 ms *
7 41.181.47.223 94.635 ms * *
8 xp-dca-1.za--xp-cr-1.za-a.mtnns.net (196.44.0.155) 90.485 ms * *
9 rb-cr-1.za--rb-cr-2.za-a.mtnns.net (196.44.31.26) 117.340 ms * *
10 196.44.31.97 1893.189 ms * *
11 ge11-0-0.gw2.jnb6.za.mtnbusiness.net (196.30.1.22) 109.253 ms * *
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 91.369 ms * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
Destination not reached

Third time lucky I hit a 197.x address:

# tcptraceroute mybroadband.co.za
Selected device gprs0, address 197.173.28.45, port 54050 for outgoing packets
Tracing the path to mybroadband.co.za (41.203.21.137) on TCP port 80 (www), 30 hops max
1 * * *
2 41.50.20.1 64.301 ms 67.902 ms 74.646 ms
3 10.220.231.70 73.608 ms 78.613 ms 89.600 ms
4 41.50.16.1 89.478 ms 88.959 ms 200.104 ms
5 41.50.0.3 195.587 ms 87.891 ms 89.447 ms
6 41.48.253.36 110.657 ms 86.670 ms 99.578 ms
7 41.181.47.223 89.020 ms 128.724 ms 86.426 ms
8 rb-cr-2.za--rb-dca-2.za-b.mtnns.net (196.44.0.155) 98.053 ms 88.440 ms 67.993 ms
9 rb-cr-1.za--rb-cr-2.za-a.mtnns.net (196.44.31.26) 107.971 ms 87.860 ms 88.317 ms
10 196.44.31.97 109.588 ms 76.935 ms 95.459 ms
11 ge4-0-0.gw17.jnb6.za.mtnbusiness.net (196.30.1.37) 141.784 ms 86.151 ms 95.185 ms
12 vlan9.hr3.jnb6.za.mtnbusiness.net (196.30.156.136) 98.206 ms 88.287 ms 84.687 ms
13 core-router1.jnb2.host-h.net (196.30.213.108) 88.623 ms 78.186 ms 86.456 ms
14 41.72.136.53 99.549 ms 89.203 ms 89.539 ms
15 mybroadband.co.za (41.203.21.137) [open] 103.607 ms 82.641 ms
41.72.136.53 81.726 ms

 

[sajunky]

ginggs, why is different port for ping every time? It shouldn't matter of course, just curious.

 

[ginggs]

ginggs, why is different port for ping every time? It shouldn't matter of course, just curious.

Your TCP/IP stack creates each outgoing connection on a free port chosen at random. Tcptraceroute requests a free outgoing port just like your browser would, but it has a command line option to specify a port if you so wish.

 

[sajunky]

Windows tracert or ping doesn't display any port number nor allows to select one. I remember in OS/2 it was possible. Anyway, thank you.

 

[ginggs]

Windows tracert or ping doesn't display any port number nor allows to select one.

Windows ping and tracert and Linux traceroute use ICMP not TCP. ICMP does not have a port number.

I've heard from Cell-C that this recent problem has been resolved.

 

[Sinbad]

Windows ping and tracert and Linux traceroute use ICMP not TCP. ICMP does not have a port number.

I've heard from Cell-C that this recent problem has been resolved.

Linux traceroute uses udp and all traceroutes rely on an icmp ttl exceeded message back from each router along the path in succession.

 

[ginggs]

Linux traceroute uses udp and all traceroutes rely on an icmp ttl exceeded message back from each router along the path in succession.

Linux traceroute does ICMP or UDP, and the very latest versions can do TCP as well.
The point is tcptraceroute uses TCP which makes it useful when tracing networks where ICMP packets may be blocked or where TCP traffic on certain ports may take different routes, e.g. transparent HTTP proxies.