Hi! Some general question + Wifi USB Realtek RTL8191S

[matzi]

That's the strange thing.

It has a manual assigned IP, but it is not accepted from the router.

The communication is like I described some posts before

I had LAN and WLAN ports active simultanously with different IPs.
I had access to the NAS through both IPs. Acces through the WLAN IP was noticably slower most likely because of the differnt speed 54Mbit/s - 100MBit/s.
Then I disconnected the LAN cable expecting the WLAN remaining active, but at this point the WLAN connection also stops and I have no access anynore. Replugging the cable, renewing the connections in putty reestablishes both connections.

[matzi]

Kept on trying, I found something strange. Whenever I change IP Adress of wlan0, eth0 follows simultaneously (see quote). And it looks like it was too late last nite. The router listed wlan member witout IP was not the dongle, it was the eth0 interface. I am slightly mixed up at the moment...

root@fvdwsl-base:/ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:4B:91:71:FF
inet addr:192.168.178.2 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:4bff:fe91:71ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4801 errors:0 dropped:0 overruns:0 frame:0
TX packets:2776 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:487858 (476.4 KiB) TX bytes:314894 (307.5 KiB)
Interrupt:11

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:313 errors:0 dropped:0 overruns:0 frame:0
TX packets:313 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27545 (26.8 KiB) TX bytes:27545 (26.8 KiB)

wlan0 Link encap:Ethernet HWaddr 7C:DD:90:17:C3:09
inet addr:192.168.178.16 Bcast:192.168.178.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:401 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:86460 (84.4 KiB) TX bytes:1436 (1.4 KiB)

root@fvdwsl-base:/ # ifconfig wlan0 inet 192.168.178.2
root@fvdwsl-base:/ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:4B:91:71:FF
inet addr:192.168.178.2 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:4bff:fe91:71ff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4999 errors:0 dropped:0 overruns:0 frame:0
TX packets:2845 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:507234 (495.3 KiB) TX bytes:322784 (315.2 KiB)
Interrupt:11

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:317 errors:0 dropped:0 overruns:0 frame:0
TX packets:317 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:27617 (26.9 KiB) TX bytes:27617 (26.9 KiB)

wlan0 Link encap:Ethernet HWaddr 7C:DD:90:17:C3:09
inet addr:192.168.178.2 Bcast:192.168.178.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:401 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:86460 (84.4 KiB) TX bytes:1436 (1.4 KiB)

[matzi]

To avoid any casualties with encryption, I habe setup a Networl without it.
And this is what I get when trying to log on:


root@fvdwsl-base:/ # iwconfig wlan0 ap "FRITZ!Box Gastzugang"
Interface wlan0 doesn't support IP addresses
wlan0 Interface doesn't support IP addresses
Error for wireless request "Set AP Address" (8B14) :
invalid argument "FRITZ!Box Gastzugang".

The same when I use the network adress instead of its name.

[fvdw]

I have no experience with it but I think you should use

iwconfig wlan0 ap <mac address of the ap>

mac address of the ap must with the ":" separators so xx:xx:xx:xx:xx:xx

[matzi]

I did that also with the same result. For the moment I have no idea hw to proceed.
For now I would appreciate if you can find a suitable wpa_supplicant. And maybe the driver is not 100% ? Sometimes I read that ralink drivers show up with "ra0" instead of "wlan0" ??

[fvdw]

the drivers are as is in the linux kernel so I suppose that they are ok. Or you must have found a bug report on the internet

the rpoblem with compiling wpa-suppliant is that out ssl version (0.9.7m)in the firmware doesn't support sha256. We will need to upgrade that. But that could be risky as several application are compiled against this older version.

But I can make a package and you could try if it works

[matzi]

Yes please create that package.

I did some more trials and this is reproducable:

I can set up the wired and the wireless link simultanously. I have access to the web interface through both IPs. Using the wireless IP, the control LED on the WIFI dongle is flashing, I guess that is a sign that it is really used.

Then I unplug the LAN cable. After this, under both IPs I cannot reach the webinterface.

So far we had this before. But today I managed to set all the required values manually and unplugged/switched off all other network member other than computer, router, nas.

Strange thing is that the router now shows that the MAC adress of the wifi dongle is lost after unplugging the cable, it's IP is still visible. What can that mean ??

[fvdw]

:dontknow . Its very difficult to trouble shoot in this way. there is little more I can do then compile these drivers. It could be also that this dongle has a problem. Does it work ok on for instance your windows pc.

I made progress with wpa_suppliciant. I had to recompile openssl and ad an extra library. I will post soon a package. Unfortunate I am a little busy for work right now and there are other request on the forum as well, it may take therefor a few days.

[matzi]

Don't worry about waiting time! It's a hobby not a must. I see it as a leisure thing which is useful as well. Meanwhile I ordered another dongle like the thread's originator has. If you have pm'ned special files for that please send me copy, and will pick it up from were he left for work. Maybe on his return we can surprise him!

[fvdw]

A suggestion from Jocko, he thinks it could be a route table issue.
Maybe only routes is set with eth0 and routes for wlan0 is missing.
So when the two NIC are available, the NAS answers via the eth0 evenif the remote request uses the wlan0 NIC
if you then unplugs the cable of eth0 NIC then the NAS becomes silent without routes for wlan0

so check the route using this command

Code: Select all

busybox route -n