Vu+ dongle RT2870STA BH 2.0.2 - problem

[yadranko]

Dear Angelofsky,
as I updated the BH image to 2.0.2, I open a new thread.
My last reports were here:
http://www.vuplus-community.net/boa...gle-300-mbps-problem-on-bh-2-0-1.11359/page-3

The Ralink Vu+ dongle still doesn't work with my Vu+ Duo.
The problems seems the same as before.
Without encryptation it works. With WPA2 on it doesn't.
As for the previous image, I attach 2 wifi.txt one with WPA2 on, the other without encryption.
Of course I can make some tests for you.

Thank you very much indeed!

 

[thawtes]

+1 I have this problem

 

[angelofsky1980]

+1 I have this problem

No debug file = no help.
Sorry my friend but without some infos about your network equipment it's almost impossible to try to identify the possible problem

 

[angelofsky1980]

Dear Angelofsky,
as I updated the BH image to 2.0.2, I open a new thread.
My last reports were here:
http://www.vuplus-community.net/boa...gle-300-mbps-problem-on-bh-2-0-1.11359/page-3

The Ralink Vu+ dongle still doesn't work with my Vu+ Duo.
The problems seems the same as before.
Without encryptation it works. With WPA2 on it doesn't.
As for the previous image, I attach 2 wifi.txt one with WPA2 on, the other without encryption.
Of course I can make some tests for you.

Thank you very much indeed!

Seems (in both debug files) you have obtained an IP address from your Access Point device.
What doesen't work ?

 

[thawtes]

No debug file = no help.
Sorry my friend but without some infos about your network equipment it's almost impossible to try to identify the possible problem

how to debug file ??

 

[yadranko]

Seems (in both debug files) you have obtained an IP address from your Access Point device.
What doesen't work ?

@Angelofsky
As before, the dongle doesn't connect when using the WPA2 encryption.
I noticed too that now in the Wireless Status it gives me a confirmed IP and Nameserver (something that with the previous driver never happened).
Unfortunately isn't enough to get it connect properly. There must be something else...

Tonight I installed on my Mac Book Pro the driver Ralink driver USB(RT2870/RT2770/RT3X7X/RT537X) 10/01/2012 V 4.2.6.0 and guess what ... it works perfectly with WPA2 - I'm using it right now, writing this post.
I think that it is the definitive confirmation that the router and the WPA2 is set up properly and that the dongle works.

So it must be something in the Duo.
Are there any other settings/files related to networking on the Duo that could I check for you?
Is it possible a driver conflict or something like that?
Thanks!

 

[thawtes]

dsl modem : unencrypted + WEP = WORKING

dsl modem : WPA or WPA2 or WPA/WPA2 = does not work


Thank you in advance for your help...

 

[shad0w]

Drivers from ralink site should be configured to use WPA_supplicant before compilation.(WPA is off by default) I think BH maintainers forgot about that. And there is no RT2870/RT2770/RT3X7X/RT537X driver in 2.0.2 build

 

[thawtes]

Drivers from ralink site should be configured to use WPA_supplicant before compilation.(WPA is off by default) I think BH maintainers forgot about that. And there is no RT2870/RT2770/RT3X7X/RT537X driver in 2.0.2 build

thanks

 

[angelofsky1980]

Drivers from ralink site should be configured to use WPA_supplicant before compilation.(WPA is off by default) I think BH maintainers forgot about that. And there is no RT2870/RT2770/RT3X7X/RT537X driver in 2.0.2 build

WPA supplicant support (and their native support too) are enabled on Ralink drivers.
I've use them with my WPA2 network and DWA-140 B3 FW 2.00 devices and all works properly.

 

[yadranko]

Dear Angelofsky,
I just updated to 2.0.2 rev. A and now I can't connect also without encryption... and not only with WPA2.
I tried also with a clean BH 2.0.2 rev. A image in flash (from usb) and as you told us to get first DHCP and reboot.
If I select DHCP, there is the option "use manual dns-nameserver"; without DHCP there isn't.
If I manually insert a DNS ... it doesn't work anyway.
Am I doing something wrong?

P.s. I read you will buy our dongles ... thank you. Hope that you could solve our problems.

 

[yadranko]

Dear Angelofsky, dear all,
are there any news about these issues?

Today I continue with my tests and I tried the latest VTI image 5.1.x and I confirm you that the dongle works perfectly also with WPA2.
Of course (as it was with the successful previous test with my Mac Book Pro) also in this case, I didn't change anything in my router settings.
I also updated online the VTI image - I had to use the described "DHCP procedure" to reset the settings -, but then it works again perfectly.

I noticed some differences:
First of all, in BH there are no differences in settings beetween "Network" and "Wireless Lan Setup", instead in VTI it happened that I have to set it in both places ... That seems very strange, but in VTI I managed to overcome the DNS problem by setting it in the Name Server Configuration (which is under the Wireless Lan Setup - a menu that in BH is no more available) and leaving 0.0.0.0 in "Network".
After I discovered that in VTI, I tried again in BH, but I couldn't fix it. No way to make the dongle works even with no encryptation (this is a problem since 2.0.2 rev. a).

Moreover, there are different names in "Network". VTI recognized the dongle as "rt5370sta", BH as "rt5572sta". But both images in "Wireless Lan Setup" nicknamed it as "rt2870sta"...

In a VTI menu there is a script similar to some parts of the wifi.txt script. VTI recognized it as "ra0", in BH is "wlan0". The name is confirmed entering in the "Wireless Lan Setup", BH named it "usb WLAN adapter (wlan0)" , VTI as "...(ra0)".

I hope that my report could help you to solve the problem in BH.

 

[angelofsky1980]

Dear Angelofsky, dear all,
are there any news about these issues?

Today I continue with my tests and I tried the latest VTI image 5.1.x and I confirm you that the dongle works perfectly also with WPA2.
Of course (as it was with the successful previous test with my Mac Book Pro) also in this case, I didn't change anything in my router settings.
I also updated online the VTI image - I had to use the described "DHCP procedure" to reset the settings -, but then it works again perfectly.

I noticed some differences:
First of all, in BH there are no differences in settings beetween "Network" and "Wireless Lan Setup", instead in VTI it happened that I have to set it in both places ... That seems very strange, but in VTI I managed to overcome the DNS problem by setting it in the Name Server Configuration (which is under the Wireless Lan Setup - a menu that in BH is no more available) and leaving 0.0.0.0 in "Network".
After I discovered that in VTI, I tried again in BH, but I couldn't fix it. No way to make the dongle works even with no encryptation (this is a problem since 2.0.2 rev. a).

Moreover, there are different names in "Network". VTI recognized the dongle as "rt5370sta", BH as "rt5572sta". But both images in "Wireless Lan Setup" nicknamed it as "rt2870sta"...

In a VTI menu there is a script similar to some parts of the wifi.txt script. VTI recognized it as "ra0", in BH is "wlan0". The name is confirmed entering in the "Wireless Lan Setup", BH named it "usb WLAN adapter (wlan0)" , VTI as "...(ra0)".

I hope that my report could help you to solve the problem in BH.

Thanks for reports but it's not very useful.
VTI should use the stocking driver delivered via VU+ OE SDK without any kind of patches applied (driver name is the old one and the device is ra0 instead of wlan0).
I've ordered the two Ralink official Vu+ devices to make direct tests.
All other Ralink devices supported by this driver in my home works correctly with WPA/WPA2 (300 or 150 mbit/s) without problems.

 

[yadranko]

Thanks for reports but it's not very useful.
VTI should use the stocking driver delivered via VU+ OE SDK without any kind of patches applied (driver name is the old one and the device is ra0 instead of wlan0).
I've ordered the two Ralink official Vu+ devices to make direct tests.
All other Ralink devices supported by this driver in my home works correctly with WPA/WPA2 (300 or 150 mbit/s) without problems.

Dear Angelofsky,
are there any news? Have you recieved the Vu+ devices to make direct tests?
As reported before after the 2.0.2 rev. A I am unable to connect also without encryptation and since 2.0.0, as you probably remember, with WPA2.
By the way, are you in touch also with coders from other teams? As we have many reports that with other images there aren't problems with these Ralink devices, maybe they have discovered some bugs in the delivered driver.

Of course I'm following also the other posts and I insert here the commands you requested to tango110 - if could help you:

bm750 login: root
root@bm750:~# ls -l /etc/resolv*
-rw-r--r-- 1 root root 0 Mar 26 18:34 /etc/resolv.conf
root@bm750:~# cat /etc/resolv.conf
root@bm750:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 * 255.255.0.0 U 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
root@bm750:~#

Note that the file resolv.conf is empty. I check it also via FTP. Of course all was done via LAN.
The used DNS were Google once.
I tried twice, after the first try I did again the "DHCP procedure", but nothing changed.

Thank you!

 

[angelofsky1980]

Dear Angelofsky,
are there any news? Have you recieved the Vu+ devices to make direct tests?
As reported before after the 2.0.2 rev. A I am unable to connect also without encryptation and since 2.0.0, as you probably remember, with WPA2.
By the way, are you in touch also with coders from other teams? As we have many reports that with other images there aren't problems with these Ralink devices, maybe they have discovered some bugs in the delivered driver.

Of course I'm following also the other posts and I insert here the commands you requested to tango110 - if could help you:

bm750 login: root
root@bm750:~# ls -l /etc/resolv*
-rw-r--r-- 1 root root 0 Mar 26 18:34 /etc/resolv.conf
root@bm750:~# cat /etc/resolv.conf
root@bm750:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 * 255.255.0.0 U 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
root@bm750:~#

Note that the file resolv.conf is empty. I check it also via FTP. Of course all was done via LAN.
The used DNS were Google once.
I tried twice, after the first try I did again the "DHCP procedure", but nothing changed.

Thank you!

I haven't received my dongles I hope they come to my home soon.
About the resolv.conf file, if you have a valid IP address for your network and none into your resolv.conf file you CANNOT resolve hostnames into IP (for example www.google.com into their IP address - this operation is FOUNDAMENTAL for TCP/IP networks).
My resolv.conf contains these lines:

nameserver 8.8.8.8
nameserver 8.8.4.4

Try to put them into your resolv.conf file and retry to use your network.

I've no contact with other Teams directly but, as I wrote before, into BH there is the LATEST driver for Ralink chipsets. Other teams uses the stocking driver delivered via Vu+ OE SDK.

 

[yadranko]

I haven't received my dongles I hope they come to my home soon.
About the resolv.conf file, if you have a valid IP address for your network and none into your resolv.conf file you CANNOT resolve hostnames into IP (for example www.google.com into their IP address - this operation is FOUNDAMENTAL for TCP/IP networks).
My resolv.conf contains these lines:

nameserver 8.8.8.8
nameserver 8.8.4.4

Try to put them into your resolv.conf file and retry to use your network.

I've no contact with other Teams directly but, as I wrote before, into BH there is the LATEST driver for Ralink chipsets. Other teams uses the stocking driver delivered via Vu+ OE SDK.

Thank you Angelofsky!
I added the nameservers in the resolv.conf, FTP it to the box and finally I was able to connect to the network (static IP, no encryptation of course).
Now I am updated to rev. C
Here are the telnet commands:
bm750 login: root
root@bm750:~# ls -l /etc/resolv*
-rw-r--r-- 1 root root 38 Apr 21 19:05 /etc/resolv.conf
root@bm750:~# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4root@bm750:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 * 255.255.0.0 U 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
root@bm750:~#

Very strange that flashing (or updating) 2.0.2 rev. A, the resolv.conf file was empty... it would be interesting to understand why.
Now remains to fix the WPA problem. If you'd like, I can make some test with telnet commands (maybe is something similar happening with these Ralink dongles also regarding WPA), until you receive the dongles...

 

[angelofsky1980]

Thank you Angelofsky!
I added the nameservers in the resolv.conf, FTP it to the box and finally I was able to connect to the network (static IP, no encryptation of course).
Now I am updated to rev. C
Here are the telnet commands:
bm750 login: root
root@bm750:~# ls -l /etc/resolv*
-rw-r--r-- 1 root root 38 Apr 21 19:05 /etc/resolv.conf
root@bm750:~# cat /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4root@bm750:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.0.1 0.0.0.0 UG 0 0 0 wlan0
169.254.0.0 * 255.255.0.0 U 0 0 0 wlan0
192.168.0.0 * 255.255.255.0 U 0 0 0 wlan0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
root@bm750:~#

Very strange that flashing (or updating) 2.0.2 rev. A, the resolv.conf file was empty... it would be interesting to understand why.
Now remains to fix the WPA problem. If you'd like, I can make some test with telnet commands (maybe is something similar happening with these Ralink dongles also regarding WPA), until you receive the dongles...

I'm happy you can connect to Internet from your box
About dongles, I hope to receive them during this week.