Superhub Superhub Router Problem

badgeruk · 12-01-2013, 22:28

The last couple of days i've only been able to access www.compila.com in modem mode. Anyone got any ideas why?

Regards
badgeruk

Sephiroth · 13-01-2013, 00:32

Not on the scant information you've provided.

I think you mean that you can't access compila.com in router mode. So you've got a lot more to tell us - like what's changed; what's reported on your screen in router mode? Can you access other sites in router mode?

badgeruk · 13-01-2013, 11:47

Hi Seph.

I did lend the hub to a friend to test their internet connection a few days ago.

Get this message in router mode

The connection was reset
The connection to the server was reset while the page was loading.
The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer's network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

It's only www.compila.com I can't access in router mode. When I switch to modem mode or use a proxy the site loads fine.

Pinging www.compila.com [195.238.172.150] with 32 bytes of data&colon;
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Tracing route to www.compila.com [195.238.172.150]
over a maximum of 30 hops:

1 19 ms 11 ms 7 ms cpc12-warw13-2-0-gw.3-2.cable.virginmedia.com [8
1.108.218.1]
2 10 ms 10 ms 18 ms brhm-core-2b-ae3-2813.network.virginmedia.net [2
13.105.114.109]
3 27 ms 19 ms 11 ms brhm-bb-1b-ae8-0.network.virginmedia.net [62.253
.174.77]
4 31 ms 21 ms 23 ms ae1.lon25.ip4.tinet.net [77.67.65.161]
5 21 ms 23 ms 22 ms xe-9-2-0.lon21.ip4.tinet.net [89.149.180.106]
6 22 ms 39 ms 24 ms sl-gw11-lon-4-1-3.sprintlink.net [213.206.159.97
]
7 36 ms 25 ms 31 ms 89.191.197.146
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

Regards
badgeruk

Sephiroth · 13-01-2013, 11:56

Thanks for that, Badger. It seems to me (at this distance) that the difference between router mode and modem mode are the settings available to you in router mode. For example, what happens in router mode if the SH Firewall is turned off?

When you can't access a specific site, it'll be some kind of permission or a port that is blocked. I assume it worked before ("last coupkle of days"). So what might have changed on the SH? A factory reset?

Anyway, modem mode is the only trouble free mode with that thing albeit shelling out for your own router.

badgeruk · 13-01-2013, 12:38

Hi Seph

Thanks for the quick reply. Tried a factory reset and disabling the firewall. Had nothing but problems since virgin swapped my modem for the superhub. Going to switch to modem mode and buy a new router. Thanks for your help.

Regards
badgeruk

Sephiroth · 13-01-2013, 15:15

Great. Maplins closes at 18:00!!

ferretuk · 13-01-2013, 18:36

Quote:

Originally Posted by Sephiroth

Thanks for that, Badger. It seems to me (at this distance) that the difference between router mode and modem mode are the settings available to you in router mode. For example, what happens in router mode if the SH Firewall is turned off?

When you can't access a specific site, it'll be some kind of permission or a port that is blocked. I assume it worked before ("last coupkle of days"). So what might have changed on the SH? A factory reset?

Anyway, modem mode is the only trouble free mode with that thing albeit shelling out for your own router.

The practical difference between router and modem mode is that the IP address of your connection will change!

VM have occasional routing issues which means that some IP ranges can't access certain sites. These problems resolve themselves eventually...

Sephiroth · 13-01-2013, 18:46

Quote:

Originally Posted by ferretuk

The practical difference between router and modem mode is that the IP address of your connection will change!

VM have occasional routing issues which means that some IP ranges can't access certain sites. These problems resolve themselves eventually...

That's a bit enigmatic, Ferret. Can you please explain deeper? Is it per National Head End? What are those routing issues?

ferretuk · 13-01-2013, 19:10

Similar issues have been reported before e.g

http://www.cableforum.co.uk/board/12...o-connect.html

If a site works from one IP but not another then an intermediate router somewhere in the path from the user to the destination server has incorrect information in its routing table.

Use of OSPF and BGP etc allows routing tables to be dynamic but odd errors seem to occur from time to time...

Sephiroth · 13-01-2013, 20:39

That's why I asked. "odd errors occurring from time to time" needs an explanation. But nobody's fingered it. I've never seen a BGP enabled network screw up its routing tables. So how that happens is the enigma.

ferretuk · 13-01-2013, 21:23

Indeed - One only VM's network department, or that of their transit peers, will be able to answer.

However, back to the OP's issue - The problem is more than likely one of routing rather than SH setup.

qasdfdsaq · 14-01-2013, 18:11

Quote:

Originally Posted by Sephiroth

I've never seen a BGP enabled network screw up its routing tables. So how that happens is the enigma.

I have. Many times.