WGR614v9 router woes

kinchyuk · 28-01-2010, 23:45

Right, I've just about had it with my VM-provided WGR614v9 router. Seems to be at least once a day - usually during the evening - throughput on wireless grinds to an absolute snails pace. Ping times to the router go through the roof, download speed goes down to sub 400kbit/s, and it's totally unusable.

Power cycling the router and everything goes back to normal, usually for around 24 hours. Back to getting around 9.8Mbit/s on a 10Mbit/s service of an evening.

It's on a fixed wireless channel, so it's not a reboot causing a change of channel that's making it all work again. And yes, I upgraded the firmware a while back. Before then it was even more atrocious, consistently locking up at the first sniff of high-ish traffic or a lot of ports being mapped. And don't even get me started on what happens when you have a mix of static and dynamic assigned addresses and happen to map a port to a static IP..

Anyway, tech aside.. I'd rather not spend two hours on the phone to a scripted 1st line 'tech' in India (no disrespect, but you know what I mean - and yes I know there are some very good people out there, but being told to turn it off and on again and move my laptop a bit closer to the router when you've got more than 20 years IP engineering experience is frustrating to say the least!). I can list many reasons why it's a woefully underpowered router, but how can I translate that into 'can you send me one with a bit more oomph?'

Of course I could just bite the bullet and buy an Airport Extreme.. but seeing as this damn lump of useless plastic is technically part of the service VM provide I thought I'd give this a go first.

Sephiroth · 28-01-2010, 23:55

Are you sure it's the router? Is a wired connexion also suffering? It is wireless that's the problem, there's quite a discussion on wireless here: http://www.cableforum.co.uk/board/12...wn-page-3.html

Not the same condition as yours (which might yet turn out to be peak time congestion on VM - but then only if wired is as bad), but it's informative.

The acid test as to whether or not it's the router would be a direct connexion to the modem at the time of day you experience the problem.

pabscars · 28-01-2010, 23:56

bite the bullet, the router is pants and the fact youve changed the firmware would probably mean vm wont support it anyway.

Ive had 3 different routers supplied by vm (FREE SO i CANT COMPLAIN) and needless to say I still went out and bought one

kinchyuk · 29-01-2010, 00:13

Quote:

Originally Posted by Sephiroth

Are you sure it's the router? Is a wired connexion also suffering?

Wired seems to be fine when I dip in and check it, but I'm wireless most of the time. Not a very technical investigation, but at the first sign of a problem (usually when I'm watching iPlayer and it starts buffering, or Spotify starts stuttering) I reset the router. Around 2-3 minutes later (walk to other room, reboot, walk back, wait for wireless to reconnect, etc) and it's absolutely fine.

Quote:

It is wireless that's the problem, there's quite a discussion on wireless here: http://www.cableforum.co.uk/board/12...wn-page-3.html

Not the same condition as yours (which might yet turn out to be peak time congestion on VM - but then only if wired is as bad), but it's informative.

Guess I need to do a bit more wired testing to prove it's the router. There's only three other visible AP's nearby, and I've tried to avoid their actual and overlap channels. Maybe 5GHz is another reason to bite the bullet and go for the Extreme. However persuading the other half that we 'need' this new shiny expensive toy is tricky when I haven't exactly tried to get a new one from VM.

Touch wood haven't seen any congestion in this area - although everything (including telly) did die for a little while for two mornings running earlier this week at about 1am. I'll put that down to an upgrade, and VM assuming most people are in bed at this time of night

Sephiroth · 29-01-2010, 09:39

Yes - you do have to bottom out if it's the router or not. It's time consuming. In any case the VM supplied router is bottom of the range and not good for multiple wireless users. In fact, if you bite the bullet, go for a Buffalo 'n' router.

As I said, the easiest method for eliminating the router is to connect direct to the modem and prove that there is no performance degradation of the type described. Then work back to the router, wired and finally revert to wireless.

As a parallel track, if you wish to post your modem stats (including event log but removing any MAC address information for your cable modem), feel free becasue then we can quickly see if there is an obvious network or modem issue.

Cheers

kinchyuk · 30-01-2010, 11:22

Hi Seph,

Here we go - stats. I reckon they're ok based on some brief reading on here - but a second set of eyes would be welcome

Downstream Lock : Locked
Downstream Channel Id : 3
Downstream Frequency : 330750000 Hz
Downstream Modulation : QAM64
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 7.6 dBmV
Downstream SNR : 41.2 dB

Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 25800000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 54.5 dBmV
Upstream Mini-Slot Size : 2

Event log

Thu Jan 28 20:30:58 2010 Thu Jan 28 20:30:58 2010 Warning (5) DHCP RENEW WARNING - Field invalid in response
Wed Jan 27 02:07:32 2010 Wed Jan 27 02:07:32 2010 Information (7) Downstream sync ok
Wed Jan 27 02:07:32 2010 Wed Jan 27 02:07:32 2010 Information (7) locked and synced to rescue CMTS...all is well!
Wed Jan 27 02:07:32 2010 Wed Jan 27 02:07:32 2010 Information (7) Downstream sync ok
Wed Jan 27 02:07:32 2010 Wed Jan 27 02:07:32 2010 Information (7) Locked on the rescue CMTS ds. try to re-acquire ds sync...
Wed Jan 27 02:07:31 2010 Wed Jan 27 02:07:31 2010 Information (7) Downstream lock ok
Wed Jan 27 02:07:31 2010 Wed Jan 27 02:07:31 2010 Information (7) Downstream lock failed
Wed Jan 27 02:06:36 2010 Wed Jan 27 02:06:36 2010 Information (7) Downstream sync ok
Wed Jan 27 02:06:36 2010 Wed Jan 27 02:06:36 2010 Information (7) locked and synced to rescue CMTS...all is well!
Wed Jan 27 02:06:36 2010 Wed Jan 27 02:06:36 2010 Information (7) Downstream sync ok
Wed Jan 27 02:06:35 2010 Wed Jan 27 02:06:35 2010 Information (7) Locked on the rescue CMTS ds. try to re-acquire ds sync...
Wed Jan 27 02:06:35 2010 Wed Jan 27 02:06:35 2010 Information (7) Downstream lock ok
Wed Jan 27 02:06:34 2010 Wed Jan 27 02:06:34 2010 Information (7) Downstream lock failed
Wed Jan 27 02:07:31 2010 Wed Jan 27 02:07:31 2010 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Wed Jan 27 02:06:18 2010 Wed Jan 27 02:06:18 2010 Information (7) Downstream lock failed
Wed Jan 27 02:00:27 2010 Wed Jan 27 02:00:27 2010 Information (7) The s/w filename specified in the config file is the same as ...
Wed Jan 27 02:00:27 2010 Wed Jan 27 02:00:27 2010 Information (7) A software upgrade filename was specified in the config file.
Wed Jan 27 02:00:27 2010 Wed Jan 27 02:00:27 2010 Information (7) Authorized
Wed Jan 27 02:00:27 2010 Wed Jan 27 02:00:27 2010 Information (7) Registration complete!
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) We registered with a DOCSIS 1.0 config file!
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) Received a REG-RSP message from the CMTS...
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) Sending a REG-REQ to the CMTS...
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) CableModem SNMP configure complete
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) IP init completed ok
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) CableModem TFTP init ok
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Information (7) CableModem DHCP client init ok
Wed Jan 27 02:00:26 2010 Wed Jan 27 02:00:26 2010 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Wed Jan 27 02:00:15 2010 Wed Jan 27 02:00:15 2010 Information (7) MAP w/initial maintenance region received
Wed Jan 27 02:00:14 2010 Wed Jan 27 02:00:14 2010 Critical (3) No Ranging Response received - T3 time-out
Wed Jan 27 02:00:14 2010 Wed Jan 27 02:00:14 2010 Information (7) MAP w/initial maintenance region received
Wed Jan 27 02:00:13 2010 Wed Jan 27 02:00:13 2010 Critical (3) No Ranging Response received - T3 time-out
Wed Jan 27 02:00:13 2010 Wed Jan 27 02:00:13 2010 Information (7) MAP w/initial maintenance region received

---------- Post added at 12:22 ---------- Previous post was at 12:22 ----------

PS: Bromley network & platform if that's any help.

ZrByte · 30-01-2010, 12:33

Quote:

Originally Posted by Sephiroth

Yes - you do have to bottom out if it's the router or not. It's time consuming. In any case the VM supplied router is bottom of the range and not good for multiple wireless users. In fact, if you bite the bullet, go for a Buffalo 'n' router.

As I said, the easiest method for eliminating the router is to connect direct to the modem and prove that there is no performance degradation of the type described. Then work back to the router, wired and finally revert to wireless.

As a parallel track, if you wish to post your modem stats (including event log but removing any MAC address information for your cable modem), feel free becasue then we can quickly see if there is an obvious network or modem issue.

Cheers

Buffalo? Really? I have a buffalo N based router and it is awful. Gets reasonable wireless bandwidth, functions well with multiple users etc but if my internet connection drops (Modem reset etc) I have to manually re-establish the connection in the config, reboot or wait until the lease expires.

Sephiroth · 30-01-2010, 14:57

Glad you posted the stats - but it's not conclusive. The event log shows destructive instability on 27-Jan. The CMTS is demanding 54.5 dBmv which is high-ish and indicates all may not not perfect on the upstream There is no evidence of it having recurred since 27-Jan.

And the above is totally irrelevant to wireless, obviously.

So we need to press on, for now, with eliminating the wireless and/or router. If/when you report this to VM, that's what they'll want you to do.

We have to take the wired connexion seriously. There's no diagnosis possible of your condition without exhausting the wired options.

kinchyuk · 28-02-2010, 20:29

Well that only took a month. Not the record for the longest it's taken me to reply to something, but getting close

After a little reorganisation here I've been on wired for the past 24 hours or so. It's been absolutely stable and good throughput since the last reboot which, was funnily enough, about 24 hours ago - the wireless went to pot back then, signal strength went through the floor and packet loss just got ridiculously silly.

Still think this router is a pile of smelly brown stuff, but at least we can be specific now and elaborate on reasons for its rubbishness.

Was contemplating firing up a Cisco 2620 to do the job as a home router, but a little overkill.. not to mention noisy! Still toying with the idea of an Airport Extreme, but I've heard bad things about its 5GHz performance.

Anyway, back on topic.. it appears the WGR614v9 is rubbish for wireless. I'll give it a few more days on wired before I decide whether it's useless at that too

---------- Post added at 21:29 ---------- Previous post was at 21:23 ----------

PS: latest modem stats in case you fancy a read.. I've noticed some interesting differences between this set and the last lot - power levels have changed as have both downstream and upstream modulation.

Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 30
Downstream Frequency : 298750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 2.0 dBmV
Downstream SNR : 39.4 dB

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 4
Upstream Frequency : 46200000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 51.0 dBmV
Upstream Mini-Slot Size : 2

Welshchris · 28-02-2010, 21:01

got to be honest i didnt have an issue with the Netgear WGR614V9 on wireless but then again mine wasnt a Virgin supplied one with Locked firmware.

I used to get a rock solid 19mb almost all the time wireless on 20mb.

kinchyuk · 28-02-2010, 21:17

Strangeness, maybe it's just my configuration. Running V1.2.24_37.0.35 here (i.e. not the original VM firmware), but as per my first post it was even worse before de-VMing.

---------- Post added at 22:17 ---------- Previous post was at 22:13 ----------

At risk of sliding slightly off-topic, in addition to the modulation changes my traceroutes are looking rather different lately. And my IP addresses are reversing to .virginmedia.com addresses (and not ntl.com as they were until recently).

Bromley had a little upgrade lately? Or is it just me..

Welshchris · 28-02-2010, 21:20

u have been taken off the UBR CISCO kit and put onto the newer Motorolla BSR kit.

Proberbly network relief work was done.

Peter_ · 28-02-2010, 21:27

Quote:

Originally Posted by Welshchris

u have been taken off the UBR CISCO kit and put onto the newer Motorolla BSR kit.

Proberbly network relief work was done.

He could also be on an resegmented Cisco uBR and the are 3 versions in use at the moment.

Just because work has been done in an areas it does not mean that they have installed BSR's.

kinchyuk · 28-02-2010, 21:30

Does:

bmly-core-1a-ge-300-682.network.virginmedia.net

Shed any light on what/how/where/when? Not in the habit of storing my traceroutes and having a memory like a sieve I can't remember exactly what it was before

III · 28-02-2010, 21:44

Quote:

Originally Posted by kinchyuk

Does:

bmly-core-1a-ge-300-682.network.virginmedia.net

Shed any light on what/how/where/when? Not in the habit of storing my traceroutes and having a memory like a sieve I can't remember exactly what it was before

Can you click the connection link at the top of the forum please, you should remove any IP address from the link when you post back.