Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: shaun1264 on September 03, 2021, 08:09:55 PM
-
Bit of a strange one. Recently flashed a Hg612 modem with the unlocked SP08 webgui firmware and this website and forum is not accessible using it. I've turned off the the firewall, the router firewall and still no joy. I've checked DNS servers, all seems fine. This problem seems to be on all devices. On my debian system using wget command I get a very long connecting to www.kitz.co.uk with a eventual failure 443 error. All other websites seem to be working fine.
-
Edit... using wget again I'm just getting constant tries and nothing else.
-
That's a strange one as in bridge mode there is no way it could do that, it merely passes a stream of data from one side to the other, it has no idea what that data is.
-
Bit of a strange one. Recently flashed a Hg612 modem with the unlocked SP08 webgui firmware and this website and forum is not accessible using it.
Very odd. ???
Give the HG612 a long press of the reset button (at least 20 seconds), release the button, wait for the HG612 to fully re-initialise and then power it off. Wait a couple of minutes, power it on and check again.
-
At least 20 sec reset press doesn't do anything but a 8 sec reset did work. Still no joy. Kitz websites eventually time out. Other websites work fine. This is a very strange fault.
-
Do bear in mind the Kitz site often lags, so even a slightly higher lag on top could possibly timeout.
-
Tried again earlier this time with a different router VMG1312-B10D with the HG612. Still the same. All other websites work fine.
-
Hi
I hope you do not mind, but there is 1 thing which comes to mind, but maybe not the answer and 1 thing is even more strange if I read correctly.
What size is your MTU
if 1500, set lower say 1492
is it just kitz.co.uk with the time out/failure or is it forum.kitz.co.uk (I am thinking it is kitz.co.uk only as you are posting on forum.) and if so, both kitz and forum.kitz are on same IP address
Do you use any blocking software or have any other devices connected between your computer to router/outside world.
Have you cleared your browser cache
Does it do the same in private browser mode
Many thanks
John
-
Hi John. It's both sites. I've tried adjusting MTU size but still the same. I'm accessing this forum via 5G. Both routers do seem to block the sites. I've tried with a laptop, computer and mobile. All do the same. Just time out.
-
Hi Shaun
Many thanks and it was worth a try. What is your current MTU set to
Do you have a static IP address with your ISP
can you ping 185.24.98.37
do you see the same in browser if you try http://185.24.98.37
I am thinking your are dynamic on IP address with ISP and perhaps your current external IP address has been blocked - the ping above would give a good indicator
if dynamic, can you:
take a note of your current external IP address
fully disconnect the router from the master socket, wait at least 30 minutes (maybe an Hour to be sure)
plug back into master socket and turn on router
compare external IP address to make sure is different external IP address
if different
ping 185.24.98.37
if ping is replied to, test in browser for normal access to kitz and forum.kitz
Many thanks
John
-
Hi John. It's both sites. I've tried adjusting MTU size but still the same. I'm accessing this forum via 5G. Both routers do seem to block the sites. I've tried with a laptop, computer and mobile. All do the same. Just time out.
Hi,
What are you using for DNS?
If your mobile is working and it's an android, the fall back is Google DNS, 8.8.8.8 and 8.8.4.4
If both the hg612 and vmg1312 were set to automatically pick up ISP DNS, it would be interesting to hear if setting Google DNS on both routers solve it.
My next question would be why would Kitz be content or adult filtered.
-
Switched off modem and router for over 1 hour whilst I went shopping. No change. I'm with IDNET and have a static address. I tried first with the automatic obtain DNS and then Google DNS and still the same. Nothing. Ping 185.24.98.37 returns 56 (84) bytes of data.
On my old Technicolor DG4132 unlocked box this site and website worked fine. Only when I switched to HG612 I've had issues.
A little more background. Two weeks I had a line issue where I couldn't not authtiecate a connection. It would sync (see line rate) but couldn't connect. IDNET declared an issue at the exchange. Openreach Engineer phoned me up the next day to tell me the fault had been fixed when it wasn't. IDNET again did a test of the line and said if was fine then later sent me an email to say there was still a fault! Openreach Engineer spent an hour trying to sort problem out at exchange where he said he had to put in a work around the fix the issue. Line finally fixed.
-
Out of interest can you reach http://www.emotionless.co.uk/emotes/index.php
Its really old and no longer used but may be useful as a diagnostic test because it is on the same server but under a different account.
It should help identify if it is the server or domain issue.
-
Hi Kitz. Nope, that address also didn't work.
-
ok cheers, so at least we have identified that its not domain name specific and more likely to be reaching the server.
It also rules out any IP bans that are related to the site/forum. I don't usually block any UK IPs, but I am aware that there has been cases where some IPs have been re-assigned from elsewhere due to IPv4 shortages.
My next question would be why would Kitz be content or adult filtered.
I've no idea - although saying that, many years ago (>10) Orange mobile added the site to their adult content list purely because of a post someone had made on the forum. I can't recall exactly what it was now as , other than it wasnt really rude and I had a heck of a job trying to convince Orange to remove it.
What do your tracerts look like?
Tracing route to kitz.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 16 ms 13 ms 252.core.plus.net [195.166.130.252]
3 13 ms 13 ms 14 ms 84.93.253.103
4 16 ms 14 ms 14 ms 195.99.125.138
5 15 ms 15 ms 14 ms peer7-et-3-0-2.telehouse.ukcore.bt.net [109.159.252.180]
6 15 ms 15 ms 14 ms 166-49-214-194.gia.bt.net [166.49.214.194]
7 14 ms 15 ms 14 ms 80.157.200.225
8 14 ms 14 ms 15 ms 80.157.204.158
9 14 ms 15 ms 14 ms ae1.sr-loki.slo1.dcnet-emea.godaddy.com [87.230.113.11]
10 38 ms 36 ms 42 ms 185.24.99.67
11 16 ms 15 ms 15 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
Trace complete.
-
shaun@debian:~$ traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 192.168.1.2 (192.168.1.2) 0.692 ms 0.877 ms 1.196 ms
2 redbus-gw11-10G.idnet.net (212.69.63.36) 8.804 ms 9.183 ms 9.611 ms
3 212.69.63.140 (212.69.63.140) 9.906 ms 10.307 ms 10.574 ms
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
shaun@debian:~$
-
If I understand correctly then a tracert resolves to [185.24.98.37] which would seem to imply that DNS is OK
Last hop belongs to IDnet (212.69.63.140) Infinity Developments Static IP, Lambeth. I don't see anything past that point responding.
I would at least expect to see some sort of CoLo/peer point/ internet exchange before it hits one of the vidahost (now go daddy :( ) edge routers... but there's nothing and it doesnt even appear to reach my webhosts, nvm my server.
I'd expect there to be at least a couple of routers between IDnet and my server but there is nothing.
Anyone have an ideas please to narrow it down further?
-
I agree with your analysis but can't think of anything else to try . . . other than showing the traceroute output to IDNet.
For comparison purposes, here is the traceroute from "The Cattery" --
[bcat ~]# traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 ap (W.X.Y.Z) 4.002 ms 3.972 ms 4.094 ms
2 ae50-ner002.loh.as13285.net (78.144.1.23) 10.379 ms 9.679 ms 10.979 ms
3 ae50-scr102.loh.as13285.net (78.144.1.22) 11.528 ms 11.512 ms 11.889 ms
4 ae62-scr101.thw.as13285.net (78.144.1.114) 12.320 ms 12.301 ms 37.846 ms
5 ae1.cr-sargas.lon1.bb.godaddy.com (195.66.225.173) 12.585 ms 13.035 ms 13.429 ms
6 ae1.sr-loki.slo1.dcnet-emea.godaddy.com (87.230.113.11) 13.423 ms 9.909 ms 10.327 ms
7 185.24.99.67 (185.24.99.67) 49.101 ms 44.525 ms 43.380 ms
8 kitz.co.uk (185.24.98.37) 9.824 ms 10.408 ms 10.830 ms
[bcat ~]#
-
I'm just really confused how this could only happen on the HG612, it shouldn't be possible for it to make any difference.
-
I'm just really confused how this could only happen on the HG612, it shouldn't be possible for it to make any difference.
Agreed.
In its default configuration it is just a VDSL2 (ITU-T G.993.2) end-point, a PTM end-point and a VLAN end-point passing frames to its LAN1 port.
???
-
I would suspect something isn't "Factory" although I'm not sure what could block an IP. If the firewall was enabled I still don't know how that could block at this level. Might the OP have it router mode ?
-
Hi
There are couple of points I find strange but agreed, it needs referring to IDnet to resolve, unless wrong credentials are been used, but then I would not expect any website to show in that instance
quote
On my old Technicolor DG4132 unlocked box this site and website worked fine. Only when I switched to HG612 I've had issues.
have you plugged the dg4132 back in and does it work normally
If so, check all details are correct on the hg612 and your other router you tried
I have seen where wrong credentials (or credentials which are for non static IP) stops correct throughput due to wrong routing - even on FTTP (happened to me when we had full fibre installed and wrong credentials were given)
Many thanks
John
-
Hi G3uiss
The block is not on the OP side, as seen from traceroute
I mentioned an IP block as all our platforms have edge protections for IDS/IPS and auto block on criteria say of failed attempts to login. This is what I was thinking may have happened
I suspect it is a routing issue with IDnet and tried testing if dynamic IP by allowing the session to cease and picking up an new IP and/or gateway but it is static and OP stated no resolve
Many thanks
John
-
John
You asked a good question to clarify. It might rule out something even if the block is down the hops as you say.
-
>> The block is not on the OP side, as seen from traceroute
I'm puzzled why the trace didn't even show up even the edge routing. The absence of these 2 hops show that it is failing further up the line than at my server
87.230.113.11 ae1.sr-loki.slo1.dcnet-emea.godaddy.com
185.24.99.67 Host Europe
There should also be another hop or two before that which will depend upon the type of internet exchange used by the ISP. If anyone else is with IDnet can post their tracert to this site we may be able to track down at which point the routing is failing. I'm beginning to think that the type of modem may be a red herring. From the info gathered so far, traffic is not going any further than ID-net.
I have seen where wrong credentials (or credentials which are for non static IP) stops correct throughput due to wrong routing - even on FTTP (happened to me when we had full fibre installed and wrong credentials were given)
This is possible. Also.. it's highly likely that the swapping over of router has caused Shaun to connect to a different ISP gateway.
I'm not sure how many gateways IDnet have now, they used to have 4 based at 2 different locations.... and depending on location may use a different internet exchange for traffic out on to the Internet.
It's weird that this should fall on the back of not being able to authenticate a connection. That too could be linked to gateway issues. Traffic can be steered towards different gateways and routing to can be different depending upon which gateway the EU connects to. I suspect its far more likely that successful routing depends upon the ISP gateway you connect to, rather than the type of modem.
-
I'm with IDNet. Here's what I get:
root@nuthatch:~# traceroute 185.24.98.37
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 OpenWrt.lan (192.168.1.254) 0.292 ms 0.349 ms 0.446 ms
2 redbus-gw11-10G.idnet.net (212.69.63.36) 7.693 ms 7.708 ms 9.480 ms
3 redbus-gw7-10G.idnet.net (212.69.63.138) 9.439 ms 9.429 ms 9.413 ms
4 redbus-gw6-10G.idnet.net (212.69.63.74) 9.466 ms 9.425 ms 9.384 ms
5 et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com (80.81.192.239) 21.115 ms 21.119 ms 21.208 ms
6 ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74) 22.428 ms 20.448 ms 20.569 ms
7 ae5.ams3-ibrsa0105-01.bb.gdinf.net (188.121.32.206) 21.518 ms 21.041 ms 21.147 ms
8 ae8.lon1-cr-sargas.bb.gdinf.net (188.121.32.69) 19.496 ms 19.830 ms 19.826 ms
9 ae1.sr-loki.slo1.dcnet-emea.godaddy.com (87.230.113.11) 20.549 ms 20.551 ms 20.550 ms
10 185.24.99.67 (185.24.99.67) 58.696 ms 42.432 ms 42.300 ms
11 kitz.servers.eqx.misp.co.uk (185.24.98.37) 20.767 ms 20.853 ms 20.728 ms
root@nuthatch:~#
-
So it's starting to like a problem at IDnet? I'll be over at my parents later down near Bognor. They also have IDnet so I'll check using their service.
-
Here's a trace from my BT connection if it adds anything:
Tracing route to kitz.servers.eqx.misp.co.uk [185.24.98.37]
over a maximum of 30 hops:
1 4 ms 2 ms 2 ms 192.168.1.1
2 7 ms 10 ms 7 ms 172.16.14.115
3 * * * Request timed out.
4 8 ms 9 ms 8 ms 62.172.102.76
5 10 ms 10 ms 10 ms peer7-et3-0-7.telehouse.ukcore.bt.net [62.172.102.15]
6 9 ms 10 ms 10 ms 166-49-214-194.gia.bt.net [166.49.214.194]
7 10 ms * 11 ms 80.157.200.225
8 11 ms 10 ms 11 ms 80.157.204.158
9 21 ms 10 ms 10 ms ae1.sr-loki.slo1.dcnet-emea.godaddy.com [87.230.113.11]
10 50 ms 98 ms 18 ms 185.24.99.67
11 11 ms 10 ms 10 ms kitz.servers.eqx.misp.co.uk [185.24.98.37]
-
Works fine here at my parents place with IDnet. So looks like an email to IDnet support will be needed
-
From looking at the relevant hops in Eric's tracert
2 redbus-gw11-10G.idnet.net (212.69.63.36) 7.693 ms 7.708 ms 9.480 ms
3 redbus-gw7-10G.idnet.net (212.69.63.138) 9.439 ms 9.429 ms 9.413 ms
4 redbus-gw6-10G.idnet.net (212.69.63.74) 9.466 ms 9.425 ms 9.384 ms
5 et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com (80.81.192.239) 21.115 ms 21.119 ms 21.208 ms
Compare to yours
2 redbus-gw11-10G.idnet.net (212.69.63.36) 8.804 ms 9.183 ms 9.611 ms
3 212.69.63.140 (212.69.63.140) 9.906 ms 10.307 ms 10.574 ms
This is really useful as you both connect to the same gateway at IDnet, so you would expect the rest of the routing after gw11 to be the same too.
Eric bounces around a few other IDnet gateways which is perfectly normal, yet you end up at 212.69.63.140 (Infinity Developments) and nothing after that point responds. This information is definitely worth pointing out to your ISP.
-
PS Had a thought.
Would be interesting to see if you are able to perform a tracert to 80.81.192.239 which is one of godaddy's edge routers.
-
Email from IDNET
Hi Shaun,
The sites are reachable from our network. It may be the server has blocked your IP address for some reason or perhaps a caching issue within the router. It might be worth resetting your router to factory default settings and reconfiguring it from scratch.
Kind regards,
Brian
IDNet
-
As someone else asked, have you tried going back to the original router or the VMG1312-B10D using its VDSL modem rather than the HG612?
Also as mentioned, check what IP address you are getting. As the only way I can possibly think this is happening is if there is some sort of routing error for certain IP addresses on IDnet.
-
Are you using the HG612 as a router, if not what are you using as the router?
-
Would be interesting to see if you are able to perform a tracert to 80.81.192.239 which is one of godaddy's edge routers.
Just to add a datum point, a traceroute to 80.81.192.239 just times out for me, a TalkTalk user, as expected.
-
Just to add a datum point, a traceroute to 80.81.192.239 just times out for me, a TalkTalk user, as expected.
On Zen all traffic to this location is immediately dropped. Looks like a BGP ROA/RPKI issue.
The range 80.81.192.0/21 is announced by 3 AS numbers (AS1257, AS52320 & AS61568), each announcement is signed but invalid. Looks like the signature/ROA is claiming AS0 is the correct origin? Looks like any network that validates announcements will drop traffic to this range.
https://bgp.he.net/ip/80.81.192.239 (https://bgp.he.net/ip/80.81.192.239)
https://rpki.cloudflare.com/?view=validator&validateRoute=1257_80.81.192.0%2F21 (https://rpki.cloudflare.com/?view=validator&validateRoute=1257_80.81.192.0%2F21)
-
On Zen all traffic to this location is immediately dropped. Looks like a BGP ROA/RPKI issue.
Thank you.
-
Not sure what's happened or changed but this site is now working for me. Thanks to whoever.
-
Hi
glad its now working
would you be able to post a tracert to forum.kitz.co.uk so we can see your routing (I suspect you will match very closely to roseway and not nnt)
Many thanks
John
-
traceroute to 185.24.98.37 (185.24.98.37), 30 hops max, 60 byte packets
1 modemtim.homenet.telecomitalia.it (192.168.1.2) 0.841 ms 0.879 ms 0.962 ms
2 redbus-gw11-10G.idnet.net (212.69.63.36) 10.557 ms 10.571 ms 10.546 ms
3 212.69.63.140 (212.69.63.140) 10.562 ms 10.586 ms 10.560 ms
4 et-7-0-0-u100.cr-polaris.fra1.bb.godaddy.com (80.81.192.239) 23.110 ms 23.740 ms 24.161 ms
5 ae14.ams3-ibrsa0108-01.bb.gdinf.net (188.121.32.74) 24.242 ms 24.154 ms 24.183 ms
6 ae5.ams3-ibrsa0105-01.bb.gdinf.net (188.121.32.206) 24.210 ms 24.639 ms 24.507 ms
7 ae8.lon1-cr-sargas.bb.gdinf.net (188.121.32.69) 20.790 ms 21.266 ms 21.108 ms
8 ae1.sr-loki.slo1.dcnet-emea.godaddy.com (87.230.113.11) 23.040 ms 22.934 ms 21.991 ms
9 185.24.99.67 (185.24.99.67) 38.148 ms 38.165 ms 38.190 ms
10 kitz.servers.eqx.misp.co.uk (185.24.98.37) 22.520 ms 22.660 ms 22.460 ms
shaun@debian:~$