User comments on ISPs
  >> Zen Internet


Register (or login) on our website and you will not see this ad.


  Print Thread
Standard User paulsmith109
(experienced) Sun 05-May-19 14:48:54
Print Post

Routing Issues on FTTC


[link to this post]
 
Guys, I am having issues connecting to forums.overclockers.co.uk
I `ve never had problems before and I strongly suspect that the problem is NOT with my setup.
Could someone please try the site and perhaps also post a ping or a traceroute?
Thanks in advance!
Standard User paulsmith109
(experienced) Sun 05-May-19 16:07:12
Print Post

Re: Routing Issues on FTTC


[re: paulsmith109] [link to this post]
 
Further to my last post, I have tried `gateway hopping`.
Interestingly I can reach the website instantly via `dsl7` but cannot reach it via `dsl6` or `dsl8`.
Have Zen introduced new gateways recently? If so, there may be some routing issues with some of these new gateways.
Standard User Sandgrounder
(knowledge is power) Sun 05-May-19 19:25:07
Print Post

Re: Routing Issues on FTTC


[re: paulsmith109] [link to this post]
 
The website seems to respond OK (Firefox on Windoze XP)

Ping says destination port unreachable

Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Vigor 130.router
2 16 ms 22 ms 15 ms vt1.cor1.lond2.ptn.zen.net.uk
3 16 ms 16 ms 16 ms ae-17.agg3.lond2.ptn.zen.net.uk
4 16 ms 35 ms 28 ms e1-3.er1.thn.as50056.net
5 16 ms 22 ms 24 ms ve160.er2.thn.as50056.net
6 16 ms 19 ms 16 ms ve940.er11.ldx.as50056.net
7 16 ms 16 ms 16 ms ve933.er8.vta.as50056.net
8 forums.overclockers.co.uk [185.103.4.11] reports: Destination protocol unreachable.



Line One:- Zen Fibre 1 - DrayTek Vigor 2860ac
Line Two:- Andrews and Arnold - DrayTek Vigor 130 Modem
Mobile:- EE PAYG - TP-Link Archer MR200


Register (or login) on our website and you will not see this ad.

Standard User chris6273
(committed) Sun 05-May-19 21:50:55
Print Post

Re: Routing Issues on FTTC


[re: Sandgrounder] [link to this post]
 
In reply to a post by Sandgrounder:
The website seems to respond OK (Firefox on Windoze XP)

Ping says destination port unreachable


Same thing on Virgin Media:

Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms moorland-rtr1.core.
2 * * * Request timed out.
3 9 ms 10 ms 10 ms cosh-core-2a-xe-823-0.network.virginmedia.net [80.0.142.73]
4 * * * Request timed out.
5 * * * Request timed out.
6 18 ms 17 ms 19 ms tcl5-ic-6-ae0-0.network.virginmedia.net [62.254.85.66]
7 28 ms 24 ms 24 ms e1-3.er1.thn.as50056.net [195.66.225.217]
8 21 ms 26 ms 20 ms ve160.er2.thn.as50056.net [178.18.119.90]
9 19 ms 17 ms 17 ms ve940.er11.ldx.as50056.net [31.28.67.58]
10 35 ms 22 ms 34 ms ve933.er8.vta.as50056.net [31.28.68.46]
11 forums.overclockers.co.uk [185.103.4.11] reports: Destination protocol unreachable.

Website loads okay though

-------------------------------------------------------------------
A.K.A: Chrisszzyy

Telewest (2004-2006): 256Kbps -> 512Kbps
University of Portsmouth's Horrible Network (2013 - 2014) - Supposedly 100/100Mbps
BT (2006 - Present): 8128/448 -> 22494/1211 -> 79987/20000Kbps (BT Infinity 2 on Huawei Cab)
Virgin Media VIVID 350 (2014 - Present): 402/38.5Mbps
Standard User billford
(elder) Sun 05-May-19 22:13:17
Print Post

Re: Routing Issues on FTTC


[re: Sandgrounder] [link to this post]
 
Using macOS 10.13.6 (High Sierra) via IDNet, ping gives:

PING forums.overclockers.co.uk (185.103.4.11): 56 data bytes
92 bytes from forums.overclockers.co.uk (185.103.4.11): Destination Port Unreachable
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 5400 b780   0 0000  38  01 4bf6 192.168.1.24  185.103.4.11


Maybe the last two lines mean something to somebody crazy

Traceroute works and gives:

traceroute to forums.overclockers.co.uk (185.103.4.11), 64 hops max, 52 byte packets
 1  www.asusnetwork.net (192.168.1.1)  3.587 ms  1.132 ms  1.244 ms
 2  redbus-gw11-10g.idnet.net (212.69.63.36)  11.592 ms  9.577 ms  12.813 ms
 3  redbus-gw7-10g.idnet.net (212.69.63.138)  10.446 ms  9.402 ms  9.482 ms
 4  redbus-gw6-10g.idnet.net (212.69.63.74)  9.086 ms  15.543 ms  62.483 ms
 5  lonap-tfm71.as50506.net (5.57.80.13)  41.463 ms  14.146 ms  9.371 ms
 6  ve160.er2.thn.as50056.net (178.18.119.90)  10.696 ms  10.666 ms  14.445 ms
 7  ve940.er11.ldx.as50056.net (31.28.67.58)  10.544 ms  10.035 ms  15.567 ms
 8  ve933.er8.vta.as50056.net (31.28.68.46)  12.869 ms  10.188 ms  14.227 ms
 9  forums.overclockers.co.uk (185.103.4.11)  9.864 ms  9.892 ms  9.617 ms


Web page is fine (Chrome).

Bill
A level playing field is level in both directions.

_______________________________________Planes and Boats and ... ______________BQMs: IPv4 IPv6
Standard User AndrewNi
(regular) Mon 06-May-19 11:38:59
Print Post

Re: Routing Issues on FTTC


[re: paulsmith109] [link to this post]
 
Seems to load fine here on Zen ADSL.

Text
1
23
45
67
89
1011
1213
1415
Tracing route to 185.103.4.11 [forums.overclockers.co.uk] on port 80
Over a maximum of 30 hops.1       1 ms    1 ms    1 ms    192.168.0.1
2       22 ms   22 ms   22 ms   62.3.80.21      [losubs.subs.bng2.th-lon.zen.net.uk]3       22 ms   22 ms   22 ms   62.3.86.82      [ae1-183.cr2.th-lon.zen.net.uk]
4       *       *       *       Request timed out.5       23 ms   23 ms   23 ms   51.148.73.7     [ae-4.cor1.lond1.ptn.zen.net.uk]
6       23 ms   26 ms   23 ms   51.148.73.3     [ae-2.cor1.lond2.ptn.zen.net.uk]7       *       *       *       Request timed out.
8       52 ms   40 ms   53 ms   195.66.225.217  [e1-3.er1.thn.as50056.net]9       23 ms   23 ms   24 ms   178.18.119.90   [ve160.er2.thn.as50056.net]
10      23 ms   30 ms   152 ms  31.28.67.58     [ve940.er11.ldx.as50056.net]11      24 ms   23 ms   23 ms   31.28.68.46     [ve933.er8.vta.as50056.net]
12      Destination Reached in 23 ms. Connection established to 185.103.4.11Trace Complete.
Standard User busterboy
(member) Mon 06-May-19 17:05:04
Print Post

Re: Routing Issues on FTTC


[re: paulsmith109] [link to this post]
 
BT Internet Windows 10

Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms BThomehub.home [192.168.1.254]
2 61 ms 54 ms 68 ms 172.16.13.184
3 * * * Request timed out.
4 25 ms 24 ms 25 ms 81.139.56.164
5 25 ms 25 ms 25 ms core1-hu0-6-0-7.colindale.ukcore.bt.net [213.121.192.2]
6 26 ms 27 ms 25 ms 195.99.127.83
7 26 ms 25 ms 25 ms t2c3-et-7-3-0-0.uk-lon1.eu.bt.net [166.49.211.230]
8 34 ms 33 ms 33 ms hu0-6-0-4.ccr22.lon01.atlas.cogentco.com [130.117.14.65]
9 26 ms 36 ms 25 ms 149.11.143.94
10 26 ms 25 ms 25 ms ve160.er1.the.as50056.net [178.18.119.89]
11 31 ms 26 ms 25 ms ve160.er2.thn.as50056.net [178.18.119.90]
12 26 ms 26 ms 26 ms ve940.er11.ldx.as50056.net [31.28.67.58]
13 25 ms 26 ms 26 ms ve933.er8.vta.as50056.net [31.28.68.46]
14 forums.overclockers.co.uk [185.103.4.11] reports: Destination protocol unreachable.

Trace complete.

BTBroadband
Standard User hoopla
(member) Sat 01-Jun-19 20:46:00
Print Post

Re: Routing Issues on FTTC


[re: busterboy] [link to this post]
 
Tracing route to forums.overclockers.co.uk [185.103.4.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms fritz.box [192.168.0.254]
2 13 ms 13 ms 13 ms losubs.subs.bng1.th-lon.zen.net.uk [62.3.80.17]
3 13 ms 13 ms 13 ms ae1-177.cr2.th-lon.zen.net.uk [62.3.80.38]
4 14 ms 14 ms 14 ms vl-50.ae43.agg2.lond1.ptn.zen.net.uk [51.148.73.54]
5 14 ms 13 ms 17 ms ae-9.cor2.lond1.ptn.zen.net.uk [51.148.73.17]
6 26 ms 24 ms 14 ms ae-7.cor2.lond2.ptn.zen.net.uk [51.148.73.13]
7 15 ms 22 ms 15 ms ae-21.agg3.lond2.ptn.zen.net.uk [51.148.73.40]
8 23 ms 14 ms 16 ms e1-3.er1.thn.as50056.net [195.66.225.217]
9 22 ms 15 ms 14 ms 31.28.79.54
10 forums.overclockers.co.uk [185.103.4.11] reports: Destination protocol unreachable.

Note that it is the protocol that is unreachable, not the address. Pings fail as well
Standard User bsdnazz
(regular) Sun 02-Jun-19 13:14:05
Print Post

Re: Routing Issues on FTTC


[re: hoopla] [link to this post]
 
It's working for me right now. Perhaps the forums server was dropping ICMP traffic rather than responding to it.

It's worth noting that the traceroute protocol ( ICMP ) can be potentially be filtered as each hop ( although this does made debugging harder ) and it's often treated as lower priority than TCP and UDP traffic.

$ traceroute forums.overclockers.co.uk
traceroute to forums.overclockers.co.uk (185.103.4.11), 64 hops max, 40 byte packets
1 kyleakin (194.32.67.8) 0.519 ms 0.428 ms 0.349 ms
2 losubs.subs.bng1.th-lon.zen.net.uk (62.3.80.17) 5.781 ms 5.893 ms 6.047 ms
3 ae1-177.cr2.th-lon.zen.net.uk (62.3.80.38) 5.971 ms 5.753 ms 5.855 ms
4 * * *
5 ae-9.cor2.lond1.ptn.zen.net.uk (51.148.73.17) 6.423 ms
ae-4.cor1.lond1.ptn.zen.net.uk (51.148.73.7) 6.449 ms 6.437 ms
6 ae-7.cor2.lond2.ptn.zen.net.uk (51.148.73.13) 10.470 ms
ae-2.cor1.lond2.ptn.zen.net.uk (51.148.73.3) 6.955 ms
ae-7.cor2.lond2.ptn.zen.net.uk (51.148.73.13) 6.766 ms
7 * * *
8 e1-3.er1.thn.as50056.net (195.66.225.217) 8.530 ms 9.754 ms 6.417 ms
9 31.28.79.54 (31.28.79.54) 6.853 ms 6.956 ms 25.727 ms
10 forums.overclockers.co.uk (185.103.4.11) 6.587 ms 6.469 ms 7.046 ms
$

Edited by bsdnazz (Sun 02-Jun-19 13:14:24)

  Print Thread

Jump to