connection with netgear wg111v2

English Network/Internet
1

Hi,
I have problems connection my wg111v2 to my AP. I am running opensuse 11.2 with kernel 2.6.31.12-0.2 The AP itselfe is working fine - as I am using it to access the inet with it from my laptop. However I also tried different channels and encryption schemes with no result.
But with my Desktop it is really strange. When I boot up it seems as if I have a connection for a short time (I can start loading a webside but it will stop in the process before it is finished).
I have searched for similar problems and found this post:
Netgear WG111v2 RTL8187 - openSUSE Forums
but some things are different:
but I thing the comand line output will tell you more than my talking…

My device:

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0846:6a00 NetGear, Inc. WG111v2 54 Mbps Wireless [RealTek RTL8187L]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

at startup:

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # ifup wlan0
    wlan0     name: WG111 WiFi (v2)
    wlan0     warning: WPA configured but may be unsupported
    wlan0     warning: by this device
    wlan0     warning: wpa_supplicant already running on interface
DHCP4 client is already running on wlan0
IP address: 192.168.0.151/24

I can ping the AP: (at the beginning)

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=12.0 ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.71 ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=3.71 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=3.83 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=3.83 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=3.71 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=3.83 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=3.95 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=9.46 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=11.6 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=3.09 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=3.20 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=3.20 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=13.9 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=4.61 ms
64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=2.14 ms
64 bytes from 192.168.0.1: icmp_seq=70 ttl=64 time=2.97 ms
^C
--- 192.168.0.1 ping statistics ---
107 packets transmitted, 17 received, 84% packet loss, time 106023ms
rtt min/avg/max/mdev = 2.142/5.470/13.962/3.625 ms

I get in IP address:

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

wmaster0  no wireless extensions.

wlan0     IEEE 802.11bg  ESSID:"gutach"  
          Mode:Managed  Frequency:2.462 GHz  Access Point: Not-Associated   
          Tx-Power=20 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

scanning works also:

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # iwlist scan
lo        Interface doesn't support scanning.

eth0      Interface doesn't support scanning.

wmaster0  Interface doesn't support scanning.

wlan0     Scan completed :
          Cell 01 - Address: 00:1B:11:FE:A7:7A
                    Channel:11
                    Frequency:2.462 GHz (Channel 11)
                    Quality=37/70  Signal level=-73 dBm  
                    Encryption key:on
                    ESSID:"gutach"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000d1ea53c19
                    Extra: Last beacon: 807ms ago
                    IE: Unknown: 0006677574616368
                    IE: Unknown: 010482848B96
                    IE: Unknown: 03010B
                    IE: Unknown: 2A0100
                    IE: Unknown: 32080C1218243048606C
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK

The problem is the high packet lose. I think this is the reason:

linux-tn7m:/home/ava # dmesg | egrep "rtl|wlan"
  164.585838] phy0: hwaddr 00:18:4d:07:f8:83, RTL8187vB (default) V1 + rtl8225z2
  164.596804] rtl8187: Customer ID is 0xFF
  164.596856] Registered led device: rtl8187-phy0::tx
  164.596875] Registered led device: rtl8187-phy0::rx
  164.596904] usbcore: registered new interface driver rtl8187
  166.636661] ADDRCONF(NETDEV_UP): wlan0: link is not ready
  204.611349] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  204.613348] wlan0: authenticated
  204.613350] wlan0: associate with AP 00:1b:11:fe:a7:7a
  204.616477] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  204.616481] wlan0: associated
  204.618522] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  209.068426] martian source 255.255.255.255 from 192.168.0.1, on dev wlan0
  209.079892] martian source 255.255.255.255 from 192.168.0.1, on dev wlan0
  214.739011] wlan0: no IPv6 routers present
  248.844020] wlan0: no probe response from AP 00:1b:11:fe:a7:7a - disassociating
  257.984218] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  257.986724] wlan0: authenticated
  257.986726] wlan0: associate with AP 00:1b:11:fe:a7:7a
  257.990092] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  257.990095] wlan0: associated
  261.615462] wlan0: disassociated (Reason: 3)
  262.615023] wlan0: associate with AP 00:1b:11:fe:a7:7a
  262.622244] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1)
  262.622247] wlan0: AP denied association (code=17)
  262.815016] wlan0: associate with AP 00:1b:11:fe:a7:7a
  262.818261] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  262.818263] wlan0: AP denied association (code=17)
  263.015016] wlan0: associate with AP 00:1b:11:fe:a7:7a
  263.018376] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  263.018379] wlan0: AP denied association (code=17)
  263.215014] wlan0: association with AP 00:1b:11:fe:a7:7a timed out
  265.785345] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  265.788731] wlan0: authenticated
  265.788733] wlan0: associate with AP 00:1b:11:fe:a7:7a
  265.798345] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  265.798348] wlan0: associated
  269.765225] wlan0: disassociated (Reason: 3)
  270.765262] wlan0: associate with AP 00:1b:11:fe:a7:7a
  270.769265] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1)
  270.769268] wlan0: AP denied association (code=17)
  270.965017] wlan0: associate with AP 00:1b:11:fe:a7:7a
  270.967390] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  270.967394] wlan0: AP denied association (code=17)
  271.165014] wlan0: associate with AP 00:1b:11:fe:a7:7a
  271.167149] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  271.167152] wlan0: AP denied association (code=17)
  271.365014] wlan0: association with AP 00:1b:11:fe:a7:7a timed out
  273.785357] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  273.790231] wlan0: authenticated
  273.790233] wlan0: associate with AP 00:1b:11:fe:a7:7a
  273.792986] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  273.792989] wlan0: associated
  575.209962] wlan0: disassociated (Reason: 4)
  576.209020] wlan0: associate with AP 00:1b:11:fe:a7:7a
  576.211123] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1)
  576.211126] wlan0: AP denied association (code=17)
  576.409015] wlan0: associate with AP 00:1b:11:fe:a7:7a
  576.411373] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  576.411376] wlan0: AP denied association (code=17)
  576.609015] wlan0: associate with AP 00:1b:11:fe:a7:7a
  576.611136] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  576.611138] wlan0: AP denied association (code=17)
  576.809014] wlan0: association with AP 00:1b:11:fe:a7:7a timed out
  579.081338] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  579.087212] wlan0: authenticated
  579.087215] wlan0: associate with AP 00:1b:11:fe:a7:7a
  579.091715] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  579.091718] wlan0: associated
  878.747885] wlan0: disassociated (Reason: 4)
  879.747018] wlan0: associate with AP 00:1b:11:fe:a7:7a
  879.749415] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1)
  879.749419] wlan0: AP denied association (code=17)
  879.947014] wlan0: associate with AP 00:1b:11:fe:a7:7a
  879.948925] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  879.948927] wlan0: AP denied association (code=17)
  880.147261] wlan0: associate with AP 00:1b:11:fe:a7:7a
  880.151678] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
  880.151680] wlan0: AP denied association (code=17)
  880.347013] wlan0: association with AP 00:1b:11:fe:a7:7a timed out
  883.081399] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
  883.083035] wlan0: authenticated
  883.083038] wlan0: associate with AP 00:1b:11:fe:a7:7a
  883.085649] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
  883.085652] wlan0: associated
 1183.040456] wlan0: disassociated (Reason: 4)
 1184.040021] wlan0: associate with AP 00:1b:11:fe:a7:7a
 1184.042118] wlan0: RX ReassocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1)
 1184.042122] wlan0: AP denied association (code=17)
 1184.240016] wlan0: associate with AP 00:1b:11:fe:a7:7a
 1184.242493] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
 1184.242496] wlan0: AP denied association (code=17)
 1184.440015] wlan0: associate with AP 00:1b:11:fe:a7:7a
 1184.442004] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=17 aid=1073)
 1184.442006] wlan0: AP denied association (code=17)
 1184.640015] wlan0: association with AP 00:1b:11:fe:a7:7a timed out
 1187.082337] wlan0: authenticate with AP 00:1b:11:fe:a7:7a
 1187.086087] wlan0: authenticated
 1187.086089] wlan0: associate with AP 00:1b:11:fe:a7:7a
 1187.088091] wlan0: RX AssocResp from 00:1b:11:fe:a7:7a (capab=0x431 status=0 aid=1)
 1187.088094] wlan0: associated
 1686.475040] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.151 DST=130.57.4.24 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=65343 DF PROTO=TCP SPT=58835 DPT=80 WINDOW=437 RES=0x00 ACK FIN URGP=0 
 1758.283040] SFW2-OUT-ERROR IN= OUT=wlan0 SRC=192.168.0.151 DST=130.57.4.24 LEN=40 TOS=0x00 PREC=0x00 TTL=64 ID=65344 DF PROTO=TCP SPT=58835 DPT=80 WINDOW=437 RES=0x00 ACK FIN URGP=0

I don’t know how to circumvent this problem. please help.
Greetings.
Philipp

2

On 06/29/2010 08:46 AM, skynet4ever wrote:

There are reports of problems with the minstrel rate-setting mechanism for
these devices when the signal strength is less than -70 dBm.

Try fixing the rate using the command


sudo /usr/sbin/iwconfig wlan0 rate 1M

If that works reliably with no ping losses, then replace the 1M with 2M,
5.5M, 11M, 18M, 24M, 36M, 48M, or 54M until you find the speed that breaks
the network.

BTW, I am unable to duplicate this result on my device.

3

Hi iwfinger,
even with the 1M setting I have a average packet loss of 50% :’(
I wanted to download the latest rtl driver and use them instead of the default one, but somehow they dont want to compile on my system…
any other things I can try?
thank you for your help!

4

On 06/29/2010 01:36 PM, skynet4ever wrote:
>
> Hi iwfinger,
> even with the 1M setting I have a average packet loss of 50% :’(
> I wanted to download the latest rtl driver and use them instead of the
> default one, but somehow they dont want to compile on my system…
> any other things I can try?
> thank you for your help!

How far are from the AP, and what obstacles are in the way?

Getting the Realtek driver to compile is not difficult. What version are
you trying to build, and what kernel do you have (uname -r)?

I’ll grab it and post the patches.

5

The AP is only approximatly 15-20 meter away - but there are a solid wall and two closets in the way.

I try to build rev 52 from Download - Realtek Linux wireless driver
but I get make-errors. I have done some stuff with makefiles in the past but it is easyer when you know what is going on :wink:
In the readme there is no note of dependencies but it looks like I miss a package or something.

My kernel is 2.6.31.12-0.2 with opensuse 11.2.

In the moment I try to check the device with a windows system to see if it is simply broken.

6

On 06/30/2010 03:16 AM, skynet4ever wrote:
>
> The AP is only approximatly 15-20 meter away - but there are a solid
> wall and two closets in the way.
>
> I try to build rev 52 from ‘Download - Realtek Linux wireless driver’
> (http://rtl-wifi.sourceforge.net/wiki/Download)
> but I get make-errors. I have done some stuff with makefiles in the
> past but it is easyer when you know what is going on :wink:
> In the readme there is no note of dependencies but it looks like I miss
> a package or something.
>
> My kernel is 2.6.31.12-0.2 with opensuse 11.2.
>
> In the moment I try to check the device with a windows system to see if
> it is simply broken.

That driver is really old (2007) and is suffering from bitrot. I’ll try to
fix it to compile on 2.6.31, but it will take a while.

7

On 06/30/2010 09:17 AM, Larry Finger wrote:
>
> That driver is really old (2007) and is suffering from bitrot. I’ll try to
> fix it to compile on 2.6.31, but it will take a while.

Instead of trying to fix that file, you should go to

http://www.realtek.com/downloads/downloadsView.aspx?Langid=1&PNid=1&PFid=1&Level=6&Conn=5&DownTypeID=3&GetDown=false&Downloads=true#RTL8187L

and download the Linux driver there. It is much newer and compiles on my
2.6.35-rc3 kernel. It should build on your system with no trouble.

8

I recently found that driver too. (but Same problem)

linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # make
make: *** /lib/modules/2.6.31.12-0.2-desktop/build: No such file or directory.  Stop.
make: *** [all] Error 2

I have tried to create the directory but then other errors occur…

you were right with the assumption that this error is a range problem: I moved the desktop nearer to the AP and the conection works. (Now 5 meter only air between)
However I still have a high package loss:
At ‘ping -c 1200 -s 1300 192.168.0.1’ I got:

--- 192.168.0.1 ping statistics ---
1200 packets transmitted, 893 received, 25% packet loss, time 1200283ms
rtt min/avg/max/mdev = 3.532/7.964/173.067/11.184 ms

and when i switch to 1M

--- 192.168.0.1 ping statistics ---
1200 packets transmitted, 1149 received, 4% packet loss, time 1200717ms
rtt min/avg/max/mdev = 14.526/16.189/55.692/1.927 ms

As sitting on the flor is not an option for working purpuse :stuck_out_tongue: … How can I lower this value even further? What rate is still ok?
(I will work on the range issue. maybe drill the wall or someting)

thank you.
Philipp

9

On 07/01/2010 04:06 AM, skynet4ever wrote:
>
> I recently found that driver too. (but Same problem)
>
> Code:
> --------------------
> linux-tn7m:/home/ava/sourcecode/rtl8187L_linux_26.1039.0104.2010.release # make
> make: *** /lib/modules/2.6.31.12-0.2-desktop/build: No such file or directory. Stop.
> make: *** [all] Error 2
>
> --------------------
>
> I have tried to create the directory but then other errors occur…

You need to install the kernel headers. That link will then point to the
directory containing the “include” directory with the headers in it.

> you were right with the assumption that this error is a range problem:
> I moved the desktop nearer to the AP and the conection works. (Now 5
> meter only air between)
> However I still have a high package loss:
> At ‘ping -c 1200 -s 1300 192.168.0.1’ I got:
>
> Code:
> --------------------
> — 192.168.0.1 ping statistics —
> 1200 packets transmitted, 893 received, 25% packet loss, time 1200283ms
> rtt min/avg/max/mdev = 3.532/7.964/173.067/11.184 ms
> --------------------
>
> and when i switch to 1M
>
> Code:
> --------------------
> — 192.168.0.1 ping statistics —
> 1200 packets transmitted, 1149 received, 4% packet loss, time 1200717ms
> rtt min/avg/max/mdev = 14.526/16.189/55.692/1.927 ms
> --------------------
>
>
> As sitting on the flor is not an option for working purpuse :stuck_out_tongue: … How
> can I lower this value even further? What rate is still ok?
> (I will work on the range issue. maybe drill the wall or someting)

Those losses are still too high. I think your device is defective. At 5 m
through two walls, I get the following:

, I do not lose a single packet when pinging, and that is through 2
walls.


100 packets transmitted, 100 received, 0% packet loss, time 99140ms
rtt min/avg/max/mdev = 0.816/5.657/228.797/28.102 ms
finger@larrylap:~/wireless-testing> iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

vboxnet0  no wireless extensions.

wlan2     IEEE 802.11bg  ESSID:
Mode:Managed  Frequency:2.412 GHz  Access Point:
Bit Rate=54 Mb/s   Tx-Power=20 dBm
Retry  long limit:7   RTS thr:off   Fragment thr:off
Power Management:off
Link Quality=51/70  Signal level=-59 dBm
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:0   Missed beacon:0

If you have a little money available, these devices are available on Ebay
for about $10 US with free shipping.

10

I don’t think the stick is broken. I had the chance to test it at a friends house. He uses the same device on a windows machine with no problems (Using WEP encryption - 20 meter distance with two walls). I plugged my one in and the connections worked without any additional changes.

But I am giving up now. I think I try to use an other router as an AP and connect it to the AP with the internet connection. (I don’t know why I didn’t think of that in the first place).
Thank you again for your help iwfinger.

p.s.: of cause the headers :stuck_out_tongue: that one was stupid

11

i found them though after hours of searching for developers!! nothing else worked after wasting time.

go to www.weinsteinsolutions.com/wg111v2.html

sorted me out and saved me hours of work (whos got time to spend doing all this!)
has instructions to follow for Windows 7 and vista and friend also confirmed it works on 64bit as well as 32bit. cost is nothing compared to time one could spend.
highly recommend! :slight_smile:

12

On 07/21/2010 12:23 PM, danrobin101 wrote:
>
> i found them though after hours of searching for developers!! nothing
> else worked after wasting time.
>
> go to ‘www.weinsteinsolutions.com/wg111v2.html’
> (http://www.weinsteinsolutions.com/wg111v2.html)
>
> sorted me out and saved me hours of work (whos got time to spend doing
> all this!)
> has instructions to follow for Windows 7 and vista and friend also
> confirmed it works on 64bit as well as 32bit. cost is nothing compared
> to time one could spend.
> highly recommend! :slight_smile:

As a coauthor of the driver for that device, I also recommend it.

Be aware that there are some problems reported with the Linux driver when the
signal strength is less than -70 dBm. I cannot reproduce the problem, thus it
has not been fixed. Under 4 pounds seems like the right price - these devices
are likely surplus.