Quoting "Andrew McGlashan"
> On 26/11/2013 11:10 AM, Petros wrote:
>> Weird that only some worksites don't work.. it's a bit how a friend
>> living over in China describes it - randomly some stuff is blocked. I
>> hope we are not there yet..
>
> Yes, well, I had an issue with getting to the Billion website in AU ...
> the ISP claimed no block, Billion claimed no block -- I got a temporary
> extra block of IPs to test and another IP was fine from the same ISP,
> but they never did find out what was blocking my normal IP, not the ISP,
> nor Billion.  In the end I just routed the connection via another
> service, but most people don't have multiple services to /choose/ from.

True. At the moment I have two links but one should be decommissioned soon.

Interesting the difference between traceroute when using ICMP and TCP port 80:

$ traceroute -I www.zeit.de
traceroute to www.zeit.de (217.13.68.220), 64 hops max, 72 byte packets
  1  115.186.196.105 (115.186.196.105)  20.636 ms  20.494 ms  20.224 ms
  2  3812.Gi0.br1.cit190.uecomm.net.au (218.185.31.142)  19.917 ms   
20.789 ms  20.960 ms
  3  VLAN323.o3mlc76f05.optus.net.au (61.88.143.197)  20.641 ms   
22.014 ms  21.419 ms
  4  203.208.192.241 (203.208.192.241)  195.414 ms  194.884 ms  195.379 ms
  5  203.208.172.242 (203.208.172.242)  194.133 ms
     203.208.172.238 (203.208.172.238)  194.407 ms
     203.208.172.246 (203.208.172.246)  194.606 ms
  6  80.150.171.41 (80.150.171.41)  196.557 ms  197.589 ms  196.317 ms
  7  bs-ea1-i.BS.DE.NET.DTAG.DE (62.154.99.34)  357.788 ms  358.499 ms  
  364.120 ms
  8  dtag.gaertner.de (80.150.168.230)  353.579 ms  354.360 ms  354.330 ms
  9  www.zeit.de (217.13.68.220)  355.478 ms  355.685 ms  358.413 ms

BTW: I can ping www.zeit.de on both without packet loss..

Here for the new link if I do a traceroute using TCP port 80:

$ traceroute -P tcp -p 80 www.zeit.de                                   
  traceroute to www.zeit.de (217.13.68.220), 64 hops max, 64 byte  
packets
  1  115.186.196.105 (115.186.196.105)  21.767 ms  20.853 ms  20.700 ms
  2  3812.Gi0.br1.cit190.uecomm.net.au (218.185.31.142)  20.425 ms   
21.105 ms  21.113 ms
  3  VLAN323.o3mlc76f05.optus.net.au (61.88.143.197)  21.699 ms   
20.173 ms  22.365 ms
  4  203.208.192.241 (203.208.192.241)  196.148 ms  195.114 ms  195.871 ms
  5  203.208.172.242 (203.208.172.242)  194.133 ms
     so-1-0-3-0.toknf-cr2.ix.singtel.com (203.208.173.22)  200.944 ms
     203.208.172.246 (203.208.172.246)  193.771 ms
  6  80.150.171.41 (80.150.171.41)  198.757 ms  195.419 ms  196.833 ms
  7  bs-ea1-i.BS.DE.NET.DTAG.DE (62.154.99.34)  357.401 ms  359.721 ms  
  356.776 ms
  8  dtag.gaertner.de (80.150.168.230)  354.517 ms  353.234 ms  355.168 ms
  9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
..
54  * * *
..

I don't understand it.. Why do the port 80 packets loop forever?

I never worked for an ISP so maybe people with this background have  
seen this before?

I also see that the old link is using US addresses, the new one Singapore..

Regards
Peter

_______________________________________________
luv-main mailing list
[email protected]
http://lists.luv.asn.au/listinfo/luv-main

Reply via email to