Advice for potential new customer!

Azazel · 15-08-2008, 12:21

Recently had the Cable Broadband enabled in my area, probabaly 6-12 months ago if im being honest and i was thinking about taking up the service, i am in the harrow area does anyone have anything to report regarding the status of the UBR any overcrowding around??

Also any advice on which router to use with the cable service, i was looking for something that can use the DD WRT, i am particularly tempted with the Linksys ones with the storage support to plug in USB devices as a network drive.

The only thing that i need is a gigabit switch really for transferring large files over the network.

Any advice is appreciated.

Axegrinder · 15-08-2008, 12:25

If you want gigabit connectivity, try looking at a Netgear RangeMax NEXT WNR854T. Or a D-Link DIR-655. Many others to choose from .

HTH

Fatec · 15-08-2008, 12:29

To offer you any advice we need to know what you'll use the connection for, do you download at all? during hours you are actually awake? then virginmedia isnt for you.

If you download overnight then i'd recommend cable.

What's your distance from the exchange? maybe ADSL is a better option?

Azazel · 15-08-2008, 13:45

Already got ADSL and im just over 3.5km from the exchange via cable length, 1.5km as the crow flys I do download abit but im at work most of the daytime hours, evenings till 11pm i play online games and then i do abit of downloading overnight, i get 7mb from a 24mb Be*there line and its fairly decent just not the best speed wise because of my distance from the exchange.

Fatec · 15-08-2008, 13:48

Then it seems like 20Mbit Would be a better option for you, especially considering the problems Be are having as of late.

Expect higher pings on cable though.

Azazel · 15-08-2008, 13:55

I get pings of 22-30 currently on Be* from what i have seen the pings are very similar, and my online gaming is mainly MMO based with abit of FPS action thrown in, so ping is not so much and issue in MMO games at least.

what are the usualy ping results to jolt and multiplay servers if anyone can oblige, and if you could throw in the usual checks to google and bbc.co.uk just for comparison.

Also any advice on routers?

Cheers

Zhadnost · 16-08-2008, 16:17

Okay here's some results, I threw in bulldog ones for completeness. They seemed to have the least latency (I know, I was surprised too).

My VM connection (southampton ubr, either ex-nynex or ex-videotron) compares quite well.
Other connections are all to the southampton exchange.

From Bulldog:

PING www.bbc.net.uk (212.58.251.195) 56(84) bytes of data.
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=1 ttl=119 time=29.0 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=2 ttl=119 time=13.2 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=3 ttl=119 time=12.7 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=4 ttl=119 time=12.9 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=5 ttl=119 time=13.1 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=6 ttl=119 time=19.0 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=7 ttl=119 time=13.0 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=8 ttl=119 time=12.4 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=9 ttl=119 time=12.9 ms
64 bytes from www-vip.telhc.bbc.co.uk (212.58.251.195): icmp_seq=10 ttl=119 time=12.9 ms

--- www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9000ms
rtt min/avg/max/mdev = 12.497/15.153/29.050/4.989 ms

From Be:

PING www.bbc.net.uk (212.58.253.67) 56(84) bytes of data.
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=1 ttl=124 time=22.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=2 ttl=124 time=22.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=3 ttl=124 time=22.6 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=4 ttl=124 time=22.3 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=5 ttl=124 time=22.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=6 ttl=124 time=22.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=7 ttl=124 time=22.9 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=8 ttl=124 time=22.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=9 ttl=124 time=22.4 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=10 ttl=124 time=22.4 ms

--- www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 8997ms
rtt min/avg/max/mdev = 22.347/22.701/22.921/0.237 ms

From ex-ntl:

PING www.bbc.net.uk (212.58.253.67) 56(84) bytes of data.
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=1 ttl=118 time=14.5 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=2 ttl=118 time=14.8 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=3 ttl=118 time=16.0 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=4 ttl=118 time=12.7 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=5 ttl=118 time=23.5 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=6 ttl=118 time=23.0 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=7 ttl=118 time=14.4 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=8 ttl=118 time=13.2 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=9 ttl=118 time=25.5 ms
64 bytes from www-vip.cwwtf.bbc.co.uk (212.58.253.67): icmp_seq=10 ttl=118 time=15.8 ms

--- www.bbc.net.uk ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9003ms
rtt min/avg/max/mdev = 12.701/17.381/25.512/4.497 ms

Bulldog:

PING www.l.google.com (216.239.59.99) 56(84) bytes of data.
64 bytes from 216.239.59.99: icmp_seq=1 ttl=245 time=39.5 ms
64 bytes from 216.239.59.99: icmp_seq=2 ttl=245 time=22.6 ms
64 bytes from 216.239.59.99: icmp_seq=3 ttl=245 time=23.1 ms
64 bytes from 216.239.59.99: icmp_seq=4 ttl=245 time=21.8 ms
64 bytes from 216.239.59.99: icmp_seq=5 ttl=245 time=23.2 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 21.813/26.068/39.502/6.738 ms

Be:
PING www.l.google.com (66.249.91.99) 56(84) bytes of data.
64 bytes from ik-in-f99.google.com (66.249.91.99): icmp_seq=1 ttl=249 time=32.9 ms
64 bytes from ik-in-f99.google.com (66.249.91.99): icmp_seq=2 ttl=249 time=32.9 ms
64 bytes from ik-in-f99.google.com (66.249.91.99): icmp_seq=3 ttl=249 time=32.9 ms
64 bytes from ik-in-f99.google.com (66.249.91.99): icmp_seq=4 ttl=249 time=32.2 ms
64 bytes from ik-in-f99.google.com (66.249.91.99): icmp_seq=5 ttl=249 time=32.6 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4002ms
rtt min/avg/max/mdev = 32.202/32.758/32.997/0.318 ms

ex-ntl:

PING www.l.google.com (216.239.59.147) 56(84) bytes of data.
64 bytes from gv-in-f147.google.com (216.239.59.147): icmp_seq=1 ttl=244 time=25.9 ms
64 bytes from gv-in-f147.google.com (216.239.59.147): icmp_seq=2 ttl=244 time=23.6 ms
64 bytes from gv-in-f147.google.com (216.239.59.147): icmp_seq=3 ttl=244 time=22.9 ms
64 bytes from gv-in-f147.google.com (216.239.59.147): icmp_seq=4 ttl=244 time=24.3 ms
64 bytes from gv-in-f147.google.com (216.239.59.147): icmp_seq=5 ttl=244 time=32.9 ms

--- www.l.google.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
rtt min/avg/max/mdev = 22.925/25.954/32.955/3.639 ms

Bulldog: (jolt server)

PING 213.208.119.122 (213.208.119.122) 56(84) bytes of data.
64 bytes from 213.208.119.122: icmp_seq=1 ttl=120 time=29.1 ms
64 bytes from 213.208.119.122: icmp_seq=2 ttl=120 time=12.9 ms
64 bytes from 213.208.119.122: icmp_seq=3 ttl=120 time=12.9 ms
64 bytes from 213.208.119.122: icmp_seq=4 ttl=120 time=12.1 ms
64 bytes from 213.208.119.122: icmp_seq=5 ttl=120 time=12.8 ms

--- 213.208.119.122 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3996ms
rtt min/avg/max/mdev = 12.124/15.991/29.128/6.575 ms

Be: (jolt server)

PING 213.208.119.122 (213.208.119.122) 56(84) bytes of data.
64 bytes from 213.208.119.122: icmp_seq=1 ttl=117 time=36.0 ms
64 bytes from 213.208.119.122: icmp_seq=2 ttl=117 time=35.6 ms
64 bytes from 213.208.119.122: icmp_seq=3 ttl=117 time=36.3 ms
64 bytes from 213.208.119.122: icmp_seq=4 ttl=117 time=36.4 ms
64 bytes from 213.208.119.122: icmp_seq=5 ttl=117 time=36.3 ms

--- 213.208.119.122 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 35.681/36.198/36.438/0.354 ms

ex-ntl: (jolt server)

PING 213.208.119.122 (213.208.119.122) 56(84) bytes of data.
64 bytes from 213.208.119.122: icmp_seq=1 ttl=119 time=14.1 ms
64 bytes from 213.208.119.122: icmp_seq=2 ttl=119 time=13.3 ms
64 bytes from 213.208.119.122: icmp_seq=3 ttl=119 time=13.4 ms
64 bytes from 213.208.119.122: icmp_seq=4 ttl=119 time=17.7 ms
64 bytes from 213.208.119.122: icmp_seq=5 ttl=119 time=13.1 ms

--- 213.208.119.122 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 13.121/14.378/17.787/1.741 ms