cancel
Showing results for 
Search instead for 
Did you mean: 

Routing issue[Solved]

Newbie
Posts: 3
Registered: ‎28-01-2010

Routing issue[Solved]

Hi,
Im having trouble viewing slashdot.org . It appears that Im unable to communicate with a.fsdn.com which is used by the site. when running a traceroute for the a.fsdn.com I get the following:
traceroute to e872.g.akamaiedge.net (88.221.179.172), 30 hops max, 38 byte packets
1  lo0-central2.pcl-ag04.plus.net (195.166.128.242)  10.000 ms  20.000 ms  20.000 ms
2  gi1-12-421.pcl-gw01.plus.net (84.92.6.232)  10.000 ms  10.000 ms  10.000 ms
3  te2-2.pte-gw1.plus.net (212.159.0.186)  10.000 ms  20.000 ms  10.000 ms
4  te2-4.pte-gw2.plus.net (212.159.1.102)  10.000 ms  10.000 ms  10.000 ms
5  te3-2.ptn-gw02.plus.net (212.159.1.105)  10.000 ms  20.000 ms  10.000 ms
6  195.66.226.168 (195.66.226.168)  10.000 ms  10.000 ms  10.000 ms
7  * * *
.....
I am able to browse the site via my mobile phone, so I think the site must be ok. Any ideas?

Thanks
Kihon
4 REPLIES 4
Community Veteran
Posts: 5,608
Thanks: 365
Fixes: 6
Registered: ‎11-08-2007

Re: Routing issue

It loads OK for me !
What DNS settings are you using ?
Plusnet FTTC 80/20 IPv4/30, Hurricane Electric 6in4 IPv6/48, Pulse8 landline & calls, SamKnows 600N
Vigor 130 modem, pfSense 2.4.5-p1 router, 5 WAPs, Devolo dLAN 500, Gigaset N300A-IP VoIP DECT
Community Veteran
Posts: 5,608
Thanks: 365
Fixes: 6
Registered: ‎11-08-2007

Re: Routing issue

> tracert a.fsdn.com
Tracing route to e872.g.akamaiedge.net [92.123.83.172]
over a maximum of 30 hops:
 1     2 ms     2 ms     2 ms  My_ADSL_Gateway [192.168.xxx.xxx]
 2    15 ms    14 ms    15 ms  lo0-homesurf.pcl-ag03.plus.net [195.166.128.110]
 3    13 ms    14 ms    14 ms  gi1-6-705.pcl-gw02.plus.net [84.92.0.188]
 4    14 ms    14 ms    14 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
 5    16 ms    15 ms    16 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
 6    14 ms    14 ms    14 ms  linxnap.netarch.akamai.com [195.66.224.168]
 7    15 ms    14 ms    14 ms  a92-123-83-172.deploy.akamaitechnologies.com [92.123.83.172]
Trace complete.
Plusnet FTTC 80/20 IPv4/30, Hurricane Electric 6in4 IPv6/48, Pulse8 landline & calls, SamKnows 600N
Vigor 130 modem, pfSense 2.4.5-p1 router, 5 WAPs, Devolo dLAN 500, Gigaset N300A-IP VoIP DECT
Community Veteran
Posts: 5,608
Thanks: 365
Fixes: 6
Registered: ‎11-08-2007

Re: Routing issue

> pathping a.fsdn.com
Tracing route to e872.g.akamaiedge.net [92.123.83.172]
over a maximum of 30 hops:
  0  My_PC [192.168.xxx.xxx]
  1  My_ADSL_Gateway [192.168.xxx.xxx]
  2  lo0-homesurf.pcl-ag03.plus.net [195.166.128.110]
  3  gi1-6-705.pcl-gw02.plus.net [84.92.0.188]
  4  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  te2-4.pte-gw2.plus.net [212.159.1.102]
  6  linxnap.netarch.akamai.com [195.66.224.168]
  7  a92-123-83-172.deploy.akamaitechnologies.com [92.123.83.172]
Computing statistics for 175 seconds...
            Source to Here  This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                                            My_PC [192.168.xxx.xxx]
  1    2ms    0/ 100 =  0%    0/ 100 =  0%  My_ADSL_Gateway [192.168.xxx.xxx]
  2  18ms    0/ 100 =  0%    0/ 100 =  0%  lo0-homesurf.pcl-ag03.plus.net [195.166.128.110]
  3  22ms    0/ 100 =  0%    0/ 100 =  0%  gi1-6-705.pcl-gw02.plus.net [84.92.0.188]
  4  25ms    0/ 100 =  0%    0/ 100 =  0%  te2-2.pte-gw1.plus.net [212.159.0.186]
  5  20ms    0/ 100 =  0%    0/ 100 =  0%  te2-4.pte-gw2.plus.net [212.159.1.102]
  6  15ms    0/ 100 =  0%    0/ 100 =  0%  linxnap.netarch.akamai.com [195.66.224.168]
  7  15ms    0/ 100 =  0%    0/ 100 =  0%  a92-123-83-172.deploy.akamaitechnologies.com [92.123.83.172]
Trace complete.
Plusnet FTTC 80/20 IPv4/30, Hurricane Electric 6in4 IPv6/48, Pulse8 landline & calls, SamKnows 600N
Vigor 130 modem, pfSense 2.4.5-p1 router, 5 WAPs, Devolo dLAN 500, Gigaset N300A-IP VoIP DECT
Newbie
Posts: 3
Registered: ‎28-01-2010

Re: Routing issue

Found the issue - my router is blocking the site for some reason (not configured to block it, it just decided to). Tried a different router, and everything works.
Thanks anyway.
Kihon