Superhub R36 Firmware Beta Test (was R35) - Page 32

qasdfdsaq · 11-07-2012, 15:08

Load balancing.

Your gateway will be the first hop after the SH and should always be the same, hops afterwards may change.

That's unless they've secretly built advanced load-balancing into the Superhub itself...

thenry · 11-07-2012, 16:48

here you go qas. googles 8.8.8.8 via ge16, bbc via ge17, google.co.uk via ge18

Quote:

>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 * * 17 ms 10.87.232.1
2 17 ms 21 ms 11 ms craw-geam-1a-ge16.network.virginmedia.net [81.96.224.218]
3 30 ms 11 ms 11 ms croy-core-1a-tenge71.network.virginmedia.net [62.30.242.45]
4 11 ms 16 ms 16 ms croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82]
5 18 ms 12 ms 13 ms brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1]
6 130 ms 13 ms 16 ms glfd-bb-1b-as1-0.network.virginmedia.net [212.43.163.105]
7 16 ms 16 ms 27 ms manc-bb-1a-ae3-0.network.virginmedia.net [213.105.175.145]
8 20 ms 16 ms 44 ms manc-bb-1b-ae0-0.network.virginmedia.net [62.253.187.178]
9 22 ms 17 ms 83 ms manc-bb-1c-ae1-0.network.virginmedia.net [213.105.159.90]
10 23 ms 21 ms 40 ms know-core-1b-pc200.network.virginmedia.net [195.182.178.150]
11 20 ms 18 ms 40 ms wb7301a.network.virginmedia.net [62.30.0.204]
12 27 ms 31 ms 49 ms brhm-bb-1a-ge-720-0.network.virginmedia.net [62.30.249.46]
13 30 ms 40 ms 46 ms 0.ae1.mpr1.lhr1.uk.above.net [213.161.65.149]
14 87 ms 95 ms 92 ms 72.14.217.85
15 22 ms 30 ms 24 ms 209.85.252.188
16 46 ms 33 ms 30 ms 209.85.253.196
17 34 ms 34 ms 38 ms 209.85.240.28
18 33 ms 42 ms 43 ms 216.239.49.28
19 45 ms 36 ms * 209.85.255.126
20 33 ms 34 ms 76 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.

Quote:

>tracert www.google.co.uk

Tracing route to www-cctld.l.google.com [173.194.78.94]
over a maximum of 30 hops:

1 833 ms 13 ms 7 ms 10.87.232.1
2 8 ms 11 ms 8 ms craw-geam-1a-ge18.network.virginmedia.net [81.96.225.65]
3 13 ms 9 ms 10 ms croy-core-1a-tenge71.network.virginmedia.net [62.30.242.45]
4 8 ms 9 ms 12 ms croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82]
5 29 ms 8 ms 38 ms brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1]
6 31 ms 26 ms 18 ms manc-bb-1b-as5-0.network.virginmedia.net [62.252.192.90]
7 33 ms 27 ms 25 ms tele-ic-3-ae0-0.network.virginmedia.net [212.43.163.70]
8 77 ms 76 ms 84 ms 138-14-250-212.static.virginmedia.com [212.250.14.138]
9 39 ms 22 ms 25 ms 209.85.240.63
10 21 ms 29 ms 24 ms 209.85.253.92
11 54 ms 33 ms 35 ms 66.249.95.173
12 23 ms 26 ms 28 ms 216.239.49.45
13 * * * Request timed out.
14 26 ms 40 ms 28 ms wg-in-f94.1e100.net [173.194.78.94]

Trace complete.

Quote:

>tracert www.bbc.co.uk

Tracing route to www.bbc.net.uk [212.58.246.93]
over a maximum of 30 hops:

1 762 ms 7 ms 15 ms 10.87.232.1
2 18 ms 8 ms 7 ms craw-geam-1a-ge17.network.virginmedia.net [81.96.224.222]
3 9 ms 9 ms 12 ms croy-core-1a-tenge71.network.virginmedia.net [62.30.242.45]
4 30 ms 26 ms 31 ms croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82]
5 11 ms 9 ms 9 ms brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1]
6 16 ms 59 ms 10 ms glfd-bb-1b-as1-0.network.virginmedia.net [212.43.163.105]
7 30 ms 31 ms 12 ms glfd-tmr-1-ae5-0.network.virginmedia.net [213.105.159.46]
8 16 ms 16 ms 13 ms tcl5-ic-1-as0-0.network.virginmedia.net [62.253.185.78]
9 36 ms 12 ms 11 ms 212.58.239.249
10 * * * Request timed out.
11 29 ms 21 ms 17 ms ae0.er01.cwwtf.bbc.co.uk [132.185.254.93]
12 36 ms 17 ms 19 ms 132.185.255.165
13 12 ms 16 ms 12 ms bbc-vip014.cwwtf.bbc.co.uk [212.58.246.93]

Trace complete.

---------- Post added at 17:48 ---------- Previous post was at 17:47 ----------

same as before...

Quote:

Originally Posted by thenry

qas why am I getting different results via tracert. using 8.8.8.8 via craw-geam-1a-ge16 - www.bbc.co.uk via craw-geam-1a-ge17

qasdfdsaq · 11-07-2012, 17:03

10.87.232.1 is your default gateway. It's always the same. That is the first hop after your modem/router and the first hop on VM's network. Unfortunately it's responding using its local (internal) interface address rather than the real one.

From there your traffic is load balanced across different downstream routers, which is quite common on any big network.

thenry · 11-07-2012, 17:09

how do i find the real one?

qasdfdsaq · 11-07-2012, 17:28

Hack the Superhub or be really clever.

Or just try the first IP of your public subnet.

thenry · 11-07-2012, 17:43

all i want to do is ping the damn thing! i cant be bothered anymore. third party router is the only option now

qasdfdsaq · 11-07-2012, 17:50

Subnetting is so easy...

thenry · 11-07-2012, 18:02

.... ?

qasdfdsaq · 11-07-2012, 18:09

1) Figure out your IP
2) Change the last number to 1
3) If that doesn't work www.subnet-calculator.com

thenry · 11-07-2012, 18:16

thanks

vmfriend · 11-07-2012, 19:53

Meanwhile back on topic any more news as to whether the new firmware is being released publicly tomorrow ?

thenry · 11-07-2012, 19:59

err it is on topic! all routers have all connection details. so did the SH prior to R36!

vmfriend · 11-07-2012, 20:02

Subnetting, pinging an IP, I don't consider it to be related to the new firmware but that's just my opinion ;-)

thenry · 11-07-2012, 20:05

having detailed info on your connection is

babis3g · 11-07-2012, 20:16

Quote:

Originally Posted by vmfriend

Meanwhile back on topic any more news as to whether the new firmware is being released publicly tomorrow ?

Quote:

Re: R36 PUBLIC PILATE
Options
on 09-07-2012 18:04

We get the final call about this on Thursday, but if we get the thumbs up it should be available pretty quickly via a reboot for everyone.

Thanks
Mark Wilkin
Help & Support Forum Manager