Routing issue since 1 AM

silverblade · Apr 13, 2013, 15:58:55

Been trying to access a system at home a few times in the past few hours without success. Normally it is OK.

Ping suggests "no route to host" for my IP along with any similar IPs. Whilst a traceroute hits telehouse and then bounces between the next two hops until Max number of hops is reached.

Anyone else getting similar problems?

The IP I'm trying to connect to begins 91.135.14.

These appear to be the two nodes that traceroute bounces between:

216.66.86.45
216.66.86.46

Both look like hurricane electric nodes.

Simon · Apr 13, 2013, 16:42:57

Sorry, most of that means nothing to me, and I thought hurricanes were strong winds!

I am on an IP in the range you're trying to reach, though, but as I'm actually here, at the IP address, is there anything I can do in the way of a test?

I should mention, I'm on an iPhone at the moment, and won't be able to access the main PC until later.

Steve · Apr 13, 2013, 17:22:18

We all lost routing yesterday evening my guess and it is a guess is that this is a hangover from this.

silverblade · Apr 13, 2013, 17:23:35

Could you try pinging/tracerouting to 91.135.14.x ?
Port 22 is open for SSH connections, if you connect it should kick you out complaining that passwords aren't acceptable.

Here's the traceroute log for anyone interested:
Destination unreachable
1.   192.168.1.1
2.   -
3.   10.193.231.245
4.   218.102.40.58 wtsc3a058.netvigator.com
5.   63.218.254.125 tenge2-3.br02.hkg05.pccwbtn.net
6.   216.218.244.53 v312.core1.sjc2.he.net
7.   184.105.213.198 10gigabitethernet14-2.core1.nyc4.he.net
8.   72.52.92.242 10gigabitethernet1-2.core1.lon1.he.net
9.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
10.   216.66.86.45 v225.core1.lon1.he.net
11.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
12.   216.66.86.45 v225.core1.lon1.he.net
13.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
14.   216.66.86.45 v225.core1.lon1.he.net
15.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
16.   216.66.86.45 v225.core1.lon1.he.net
17.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
18.   216.66.86.45 v225.core1.lon1.he.net
19.   216.66.86.46 idnet.10gigabitethernet5-4.core1.lon1.he.net
...

Simon · Apr 13, 2013, 17:27:35

I can try later, but I don't think I can from my phone. You might also not want to display your full IP address in a post - I'd advise you edit that.

nowster · Apr 13, 2013, 17:30:32

Access to this forum from a Virgin cable connection was not possible last night either.

silverblade · Apr 13, 2013, 17:33:07

Ok I removed the last part of the address, but I get random connection attempts from all over the world anyway so I figured it'd make little difference.

Anyway thanks for testing it - if you need the full IP again later just let me know.

Steve · Apr 13, 2013, 17:43:08

I've tried ping, trace route and SSH to that IP address and get no further than yourself, I found the IP address as the forum keeps track of IP addressees an individual uses for access.

Simon · Apr 13, 2013, 17:50:04

I think Steve has done what I would have done, plus the SSH test.

Simon · Apr 13, 2013, 17:53:11

Steve, would it be worth you running the same tests on my IP?

Steve · Apr 13, 2013, 18:03:43

Quote from: Simon on Apr 13, 2013, 17:53:11
Steve, would it be worth you running the same tests on my IP?

Not unless you've changed the settings on your router to let it respond to a ping from the outside (wan),whereas mine should respond.

Simon · Apr 13, 2013, 18:09:48

Ah...

I like to be stealthed.

silverblade · Apr 13, 2013, 18:28:01

Quote from: Steve on Apr 13, 2013, 17:43:08
I've tried ping, trace route and SSH to that IP address and get no further than yourself, I found the IP address as the forum keeps track of IP addressees an individual uses for access.

Are you on the same IP range as me? If so... What do you get as traceroute output? The same bouncing between two nodes?

If you are on a different IP range I'd be interested still in Simon's testing, in case the fact he is on a similar range allows connectivity.

Steve · Apr 13, 2013, 18:43:19

I'm on a different IP range. I've been running some reverse traceroutes to my own IP address myself and not succeeding except on one occasion using the "Nice Trace" app on the iPad via the Three network.

ie https://mebsd.com/ipv6-ping-and-traceroute (just select IPv4 from the protocol list

traceroute -a -q 3 -w 3 -m 30 93.89.131.xx
1 [AS8468] gi3-4.telford-dc1.core.enta.net (78.33.39.217) 0.371 ms 0.365 ms 0.199 ms
2 [AS8468] te4-4.wolv-te.core.enta.net (87.127.236.18) 0.823 ms 0.825 ms 0.666 ms
3 [AS8468] te4-3.birmingham-te.core.enta.net (87.127.236.149) 1.135 ms 1.138 ms 1.134 ms
4 [AS8468] te3-1.bir.core.enta.net (87.127.236.113) 1.134 ms 1.138 ms 1.135 ms
5 [AS8468] te2-2.interxion.core.enta.net (78.33.141.30) 4.724 ms 4.416 ms 4.254 ms
6 [AS8468] te4-2.telehouse-east.core.enta.net (87.127.236.137) 4.568 ms 4.414 ms 4.411 ms
7 [AS10026] telehouse-gw.idnet.net (195.66.224.181) 7.375 ms 7.220 ms 6.906 ms
8 [AS12496] telehouse-gw2-gi0-2-400.idnet.net (212.69.63.242) 69.167 ms 7.539 ms 25.628 ms
9 ***

etc

My IP address is pingable and the ThinkBroadBand Quality monitor is still working . I'm surprised that I've not been successful running these reverse routes.

Steve · Apr 13, 2013, 18:46:39

@SilverBlade Traceroute to your IP address
Traceroute has started...

traceroute to 91.135.14.xxx (91.135.14.xxx), 64 hops max, 72 byte packets
1 router.asus.com (192.168.1.1) 2.050 ms 0.791 ms 0.757 ms
2 telehouse-gw2-lo1.idnet.net (212.69.63.51) 11.412 ms 10.646 ms 10.460 ms
3 telehouse-gw5-gi7-401.idnet.net (212.69.63.181) 16.308 ms 10.586 ms 9.819 ms
4 telehouse-gw6-gi4-400.idnet.net (212.69.63.246) 10.518 ms 10.411 ms 13.679 ms
5 v225.core1.lon1.he.net (216.66.86.45) 13.132 ms 21.431 ms 10.415 ms
6 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 10.779 ms 12.857 ms 11.423 ms
7 v225.core1.lon1.he.net (216.66.86.45) 11.205 ms 15.416 ms 10.824 ms
8 * idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 11.732 ms 14.266 ms
9 v225.core1.lon1.he.net (216.66.86.45) 11.767 ms 17.027 ms 30.853 ms
10 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 10.671 ms 12.655 ms 12.703 ms
11 v225.core1.lon1.he.net (216.66.86.45) 14.072 ms 16.094 ms 12.454 ms
12 * idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 14.278 ms 12.734 ms
13 v225.core1.lon1.he.net (216.66.86.45) 13.446 ms 12.343 ms 11.734 ms
14 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 12.525 ms 12.579 ms 12.955 ms
15 v225.core1.lon1.he.net (216.66.86.45) 13.480 ms 21.598 ms 26.215 ms
16 * idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 16.473 ms 10.877 ms
17 v225.core1.lon1.he.net (216.66.86.45) 20.412 ms 22.133 ms 12.570 ms
18 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 16.810 ms 12.713 ms 14.653 ms
19 v225.core1.lon1.he.net (216.66.86.45) 17.785 ms 26.770 ms 22.775 ms
20 * idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 14.932 ms 11.877 ms
21 v225.core1.lon1.he.net (216.66.86.45) 23.637 ms 20.942 ms 24.558 ms
22 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 11.364 ms 12.490 ms 11.798 ms
23 v225.core1.lon1.he.net (216.66.86.45) 14.939 ms 23.394 ms 13.602 ms
24 * idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 13.284 ms 11.666 ms
25 v225.core1.lon1.he.net (216.66.86.45) 150.292 ms 11.332 ms 20.726 ms
26 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 167.623 ms 13.867 ms 12.009 ms
27 v225.core1.lon1.he.net (216.66.86.45) 14.951 ms 82.747 ms 11.103 ms
28 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 12.963 ms * 15.469 ms
29 v225.core1.lon1.he.net (216.66.86.45) 16.392 ms 23.743 ms 25.201 ms
30 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 13.069 ms 14.411 ms 14.499 ms
31 v225.core1.lon1.he.net (216.66.86.45) 12.721 ms 20.157 ms 22.793 ms
32 idnet.10gigabitethernet5-4.core1.lon1.he.net (216.66.86.46) 14.237 ms

silverblade · Apr 13, 2013, 20:18:35

Yup that's exactly the same "symptoms" I get.

I've tried pings/traceroutes from several different systems located in various places throughout the world, and just get the same thing from each.

If you have anything running as a listening service on those IPs, are you able to connect to them from the internet?

Simon · Apr 13, 2013, 21:51:59

I had issues with this, as at first, the tracert through the commend prompt was timing out at every step, but it worked direct through the router interface. Seems my security product, BitDefender, blocks incoming ICMP by default, so the tracert wouldn't work until I allowed ICMP. Haven't a clue what that's all about, but here goes:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Simon>tracert 91.135.14.***

Tracing route to cust************.idnet.net [91.135.14.***]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.254
2 20 ms 19 ms 25 ms telehouse-gw2-lo1.idnet.net [212.69.63.51]
3 19 ms 19 ms 20 ms telehouse-gw5-gi4-400.idnet.net [212.69.63.245]
4 20 ms 20 ms 20 ms telehouse-gw6-gi4-400.idnet.net [212.69.63.246]
5 20 ms 21 ms 25 ms v225.core1.lon1.he.net [216.66.86.45]
6 20 ms 20 ms 19 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
7 21 ms 21 ms 21 ms v225.core1.lon1.he.net [216.66.86.45]
8 21 ms 21 ms 20 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
9 26 ms 24 ms 25 ms v225.core1.lon1.he.net [216.66.86.45]
10 20 ms 21 ms 21 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
11 30 ms 26 ms 23 ms v225.core1.lon1.he.net [216.66.86.45]
12 20 ms 22 ms * idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
13 20 ms 21 ms 21 ms v225.core1.lon1.he.net [216.66.86.45]
14 21 ms 22 ms 20 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
15 23 ms 23 ms 25 ms v225.core1.lon1.he.net [216.66.86.45]
16 20 ms 22 ms 21 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
17 30 ms 24 ms 27 ms v225.core1.lon1.he.net [216.66.86.45]
18 22 ms 23 ms 23 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
19 26 ms 25 ms 24 ms v225.core1.lon1.he.net [216.66.86.45]
20 20 ms 23 ms 22 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
21 27 ms 24 ms 25 ms v225.core1.lon1.he.net [216.66.86.45]
22 24 ms 24 ms * idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
23 22 ms 24 ms 20 ms v225.core1.lon1.he.net [216.66.86.45]
24 21 ms 21 ms 22 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
25 24 ms 22 ms 23 ms v225.core1.lon1.he.net [216.66.86.45]
26 21 ms 22 ms 20 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
27 25 ms 25 ms 24 ms v225.core1.lon1.he.net [216.66.86.45]
28 21 ms 20 ms 22 ms idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]
29 29 ms 25 ms 25 ms v225.core1.lon1.he.net [216.66.86.45]
30 23 ms 22 ms * idnet.10gigabitethernet5-4.core1.lon1.he.net [216.66.86.46]

Trace complete.

C:\Documents and Settings\Simon>

Simon · Apr 14, 2013, 23:00:34

Can we assume that this issue is now resolved?

silverblade · Apr 15, 2013, 06:53:25

It's not resolved, no. I am still unable to connect to the system at home remotely.
Traceroute still bounces between the same two nodes over and over until it gives up.

I mailed support after I first spotted the problem the other day but have not had a reply yet.
Bit frustrating but I guess it's the weekend so nobody about.

Simon · Apr 15, 2013, 07:10:45

Hopefully you'll get a response today.

silverblade · Apr 15, 2013, 11:09:02

I got a reply saying there was a temporary (and now fixed) network issue. However it still does not work.

Thanks for testing btw. Been a bit busy so didn't get much chance to check back.

Simon · Apr 15, 2013, 11:21:11

I guess it's possible your router may need a reboot?

Simon_idnet · Apr 15, 2013, 11:30:14

It was a bad session, we reset the session and all apperars to be OK for this router now. If it happens again a router reboot would probably resolve the problem.

silverblade · Apr 15, 2013, 19:07:44

Thanks - it's working fine now!

Unfortunately I couldn't get anyone to reboot anything whilst I have been away from home - plus I didn't consider that it might fix this problem as to me it looked like it was just a broken route somewhere at IDNet or elsewhere.

I must admit though I am always confused when I read these forums - are Simon and Simon_idnet the same person? The signature suggests this might be the case but I'm never sure

Glenn · Apr 15, 2013, 19:14:48

Simon is an admin of the forum,

whereas,

Simon_IDNet is one of the director/owners of IDNet.