Netgear WGR614 - Wireless Problems

[[BTF]adam]

Hey, i've purchased a http://www.ebuyer.com/product/48546/ (Netgear WGR614) and I have ran into a few headaches.

Firstly, I should have read more. it requires a modem to connect to it, which I didn't have before as I was using a BT Home Hub (router+modem). so I've tried connecting the WGR614 to the home hub through its internet port to the home hubs ethernet port. at first I had a bunch of problems but somehow I got it to work, the wireless PC's downstairs connected to the NETGEAR wireless network and we were all gravy, till I realised it was an open network and needed some security, I tried to apply the WEP key and whatnot, now since then for about an hour I haven't been able to even find the thing, neither the vista laptop, xp desktop or xp laptop will even see the NETGEAR wireless to connect to. I have tried turning the router on and off, factory resetting, going through the smart wizard again, ensuring broadcasting is on on the router admin panel, tbh I would like to return this thing but since Ebuyer only accept returns if they are damaged or unused if you change your mind, fat fucking chance.

I also tried turning the wireless interface off the home hub, no dice.

Any ideas? or should I just reside myself to the fact I spent £35 and need to spend more in the new year to get a new router/modem. (the home hub is AWFUL)

[[BTF]adam]

Okay so I've made the connection and both computers downstairs are connected to it, but it's unsecure again. and trying to secure it last time was what fucked it up and made it dissapear :/

[QwazyWabbit]

There are two secure modes, WEP and WPA. WPA is more secure. The wireless node has an ID, called an SSID and this ID is broadcast periodically from the node but it can also be disabled or blanked so the node becomes hidden.

If the SSID is being broadcast you should be able to see the node regardless of the security setting of the node, you just won't be able to connect through it without the passwords or WEP keys.

WPA keys are hashes based on a password or phrase. Doing a factory reset should clear the keys and return the node to default state and you should be able to see it on your computer again under the default SSID. You should be able to connect to and configure the node via a USB or Ethernet port regardless. Some wireless nodes create a random SSID that you must know in advance to connecting to the node.

The procedure should be outlined in the manual but the steps are roughly:

Turn on the WEP or WPA security and establish the password via a hard wired computer.
Make a note of the SSID.
Use the wireless connection configuration on the wireless computers to set the same mode and password and connect to the known SSID of the node.

You cannot connect wirelessly and wired to the node simultaneously, it's redundant and messes up your routing in the computer. Windows will actually end up preferring the wired connection.

[[BTF]adam]

thx for the reply, that part I kind of understood how to do but when I did it, it stopped the router from appearing and being able to be seen on the wireless network list, I need to get a proper, normal ADSL modem really instead of using this halfbreed piece of shit home hub routermodem, but the only ones I find, you can buy better modem/router integrated devices for the same or very slightly more! ugh

[[BTF]adam]

On a related note, since using this new router, I have found it impossible to play quake. My netgraph looks like this: It appears to be worse when I start jumping around/moving at high speed. Any ideas as to why? though I think I just made a connection, my PC seems to be stuttering a bit as well. Restart time!

[QwazyWabbit]

i have never seen anyone happy with their Q2 game performance on wireless connections.

[[BTF]adam]

My pc is on ethernet though

[UUD-40]

Just out of curiosity, does your ISP provide the router/modem, or did you buy it? 

[[BTF]adam]

The ISP provided the Home Hub (router + modem combined), I purchased the router without realising I needed a seperate ADSL Modem. So it's hooked up to the homehub. r1ch and quadz said it wasn't good because it was double NAT and other stuff

[R1CH]

i have never seen anyone happy with their Q2 game performance on wireless connections.

You've seen me .

Even with double NAT you shouldn't get lag like that with a wired connection. Try ping -t gateway_ip and check for any ping variation. Your gateway IP is the first > 1-2ms hop in a trace, eg

Code: [Select]

>tracert tastyspleen.net

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.2.1
  2    15 ms    11 ms    11 ms  10.98.0.153
...
My gateway IP would be 10.98.0.153.

[[BTF]adam]

Tracerouting Tastyspleen.net doesen't even complete xD

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Adam>ping -t gateway_ip
Ping request could not find host gateway_ip. Please check the name and try again
.

C:\Users\Adam>ping tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:
Reply from 74.54.186.226: bytes=32 time=127ms TTL=41
Reply from 74.54.186.226: bytes=32 time=126ms TTL=41
Reply from 74.54.186.226: bytes=32 time=122ms TTL=41
Reply from 74.54.186.226: bytes=32 time=126ms TTL=41

Ping statistics for 74.54.186.226:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 127ms, Average = 125ms

C:\Users\Adam>tracert tastyspleen.net

Tracing route to tastyspleen.net [74.54.186.226]
over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  10.0.0.1
  2     8 ms    99 ms    98 ms  api.home [192.168.1.254]
  3    14 ms    12 ms    13 ms  217.47.111.122
  4    19 ms    13 ms    14 ms  217.47.110.161
  5    12 ms    14 ms    13 ms  217.47.73.170
  6    15 ms    12 ms    14 ms  217.41.176.17
  7    12 ms    13 ms    14 ms  217.41.176.138
  8    13 ms    13 ms    13 ms  217.41.176.34
  9    13 ms    13 ms    13 ms  217.32.96.177
 10    13 ms    14 ms    14 ms  core1-pos4-2.sheffield.ukcore.bt.net [217.32.171
.161]
 11    19 ms    17 ms    18 ms  core1-pos-0-14-5-0.ilford.ukcore.bt.net [62.172.
102.53]
 12    19 ms    18 ms    18 ms  core1-pos9-1.telehouse.ukcore.bt.net [194.74.65.
114]
 13    18 ms    19 ms    18 ms  ge-2-1-0.mpr1.lhr2.uk.above.net [195.66.224.76]

 14    91 ms    91 ms    92 ms  64.125.27.57
 15  api.home [192.168.1.254]  reports: Destination host unreachable.

Trace complete.

C:\Users\Adam>stop
'stop' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\Adam>ping -t 10.0.0.1

Pinging 10.0.0.1 with 32 bytes of data:
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=4ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=2ms TTL=64
Reply from 10.0.0.1: bytes=32 time=15ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time=1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64
Reply from 10.0.0.1: bytes=32 time<1ms TTL=64

Ping statistics for 10.0.0.1:
    Packets: Sent = 18, Received = 18, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 15ms, Average = 1ms
Control-C
^C
C:\Users\Adam>

[ToxicMonkey^MZC]

What's wrong with the router built into the BT Homehub?

Setting up encryption on the WGR614 is pretty easy - access the router config pages (192.168.1.1) - select 'Wireless Settings'
Make yourself an SSID in the appropriate space.  Select WPA/PSK security and assign a Network Key (Passphrase).  Apply settings and bingo...secured network.

We had the same lag problem as you did with wireless, don't think we ever got fully round it, try turning off Broadcast SSID in router.   We ended up running ethernet cables round the house to the router.  The lag only seemed to occur when a Vista machine was connected wirelessly.  It's a weird fault.

[[BTF]adam]

I'm not sure exactly whats wrong with it, but its one of the earliest versions and frequently dropping connection, poor wireless signal to downstairs so my family was bitching at me about it because they couldnt connect to it half the time.

Thanks for the info.

[QwazyWabbit]

gateway_ip is supposed to be the 2nd hop in the route out. In your case it's the api.home [192.168.1.254] which appears to be the IP address of the modem/router rather than the WAN side gateway which would normally be the first router/gateway of you ISP to you. This is hop number 3 = 217.47.111.122

Do ping -n 30 217.47.111.122, this will give you a 30 count ping history.
Also do ping -n 30 tastyspleen.net and see what that shows.

What's also interesting about the traceroute to tastyspleen is that it comes back with host unreachable from the modem IP, this is strange. I don't know what would be causing this. It's not unusual to see "request timed out" where networks block pings but "host unreachable" is an outright rejection of the route.

[[BTF]adam]

im such a cmd mong what is pretty weird is, if I log onto a server it can be hit and miss. sometimes it can be smooth till I inevitably get a dropped connection (every 10-30 minutes or so, homehub problem I think), then other times it can be like that screenshot. totally shit. sometimes if I wait a few minutes it calms down and goes smooth. its just.. odd :/ secured the network thanks for the help in that regard everyone.


edit: ffs, I need to learn to read stuff redoing it.

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Adam>ping -n 30 217.47.111.122

Pinging 217.47.111.122 with 32 bytes of data:
Reply from 217.47.111.122: bytes=32 time=14ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=15ms TTL=125
Reply from 217.47.111.122: bytes=32 time=14ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=33ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=11ms TTL=125
Reply from 217.47.111.122: bytes=32 time=51ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=10ms TTL=125
Reply from 217.47.111.122: bytes=32 time=47ms TTL=125
Reply from 217.47.111.122: bytes=32 time=112ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125
Reply from 217.47.111.122: bytes=32 time=13ms TTL=125
Reply from 217.47.111.122: bytes=32 time=14ms TTL=125
Reply from 217.47.111.122: bytes=32 time=12ms TTL=125

Ping statistics for 217.47.111.122:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 10ms, Maximum = 112ms, Average = 18ms

C:\Users\Adam>ping -n tastyspleen.net
Bad value for option -n, valid range is from 1 to 4294967295.

C:\Users\Adam>ping -n 30 tastyspleen.net

Pinging tastyspleen.net [74.54.186.226] with 32 bytes of data:
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=126ms TTL=38
Reply from 74.54.186.226: bytes=32 time=131ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=127ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=125ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=129ms TTL=38
Reply from 74.54.186.226: bytes=32 time=129ms TTL=38
Reply from 74.54.186.226: bytes=32 time=131ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=166ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38
Reply from 74.54.186.226: bytes=32 time=124ms TTL=38
Reply from 74.54.186.226: bytes=32 time=122ms TTL=38
Reply from 74.54.186.226: bytes=32 time=123ms TTL=38

Ping statistics for 74.54.186.226:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 122ms, Maximum = 166ms, Average = 126ms

C:\Users\Adam>