Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[shaun1264]

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:~$

[kitz]

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? 

[burakkucat]

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 ~]#

[Alex Atkin UK]

I'm just really confused how this could only happen on the HG612, it shouldn't be possible for it to make any difference.

[burakkucat]

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.

 

[g3uiss]

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 ?

[d2d4j]

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

[d2d4j]

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

[g3uiss]

John

You asked a good question to clarify. It might rule out something even if the block is down the hops as you say.

[kitz]

>> 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.   

[roseway]

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:~#

[shaun1264]

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.

[tubaman]

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]

[shaun1264]

Works fine here at my parents place with IDnet.  So  looks like an email to IDnet support will be needed

[kitz]

From looking at the relevant hops in Eric's tracert

Code: [Select]

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

Code: [Select]

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.