dlink dwa-140 not working properly with solo 2

[angelofsky1980]

that okay you delete the link no probs at all i can tell you that i ordered a Ferguson wifi dongle and it Works on all vu+ models plus gigablue and many others so i hope this will be my solution to my problem and it it smaller than the dongle that you have but i will let you know when i get the dongle ordered from uk and i live in denmark so i takes some days before i get it also a dvb-t usb i have ordered for fun it has chipset RTL2832U / R820T is there any support for that for vu+ i know that this is a Little off topic

About Ralink wifi dongles, I'm very happy the dongle works with your network (the box acquire / accept the IP address) and it's reacheable into your network from other PCs.
About your problem, report the output of following commands:

ls -l /etc/resolv*
cat /etc/resolv.conf

After see your output, I can suggest you a good strategy to solve your problem.

About RTL2832U + R820T there are some patches from LinuxTV.org team who are in evaluation from BH Team to support this combination of chipsets.

 

[tango110]

About Ralink wifi dongles, I'm very happy the dongle works with your network (the box acquire / accept the IP address) and it's reacheable into your network from other PCs.
About your problem, report the output of following commands:

ls -l /etc/resolv*
cat /etc/resolv.conf

After see your output, I can suggest you a good strategy to solve your problem.

About RTL2832U + R820T there are some patches from LinuxTV.org team who are in evaluation from BH Team to support this combination of chipsets.

heres my output

vusolo2 login: root

root@vusolo2:~# ls -l /etc/resolv*

-rw-r--r-- 1 root root 23 Jan 1 1970 /etc/resolv.conf

root@vusolo2:~# cat /etc/resolv.conf

nameserver 192.168.1.1

root@vusolo2:~#

if this is this you need from the commands you where writing i can tell you that i just have installed latest blackhole into my vu+ duo and using same dongle and same problem

 

[angelofsky1980]

heres my output

vusolo2 login: root

root@vusolo2:~# ls -l /etc/resolv*

-rw-r--r-- 1 root root 23 Jan 1 1970 /etc/resolv.conf

root@vusolo2:~# cat /etc/resolv.conf

nameserver 192.168.1.1

root@vusolo2:~#

if this is this you need from the commands you where writing i can tell you that i just have installed latest blackhole into my vu+ duo and using same dongle and same problem

You should try to setup your Vu+ box with the Google DNS instead of your router IP.
Google DNS are 8.8.8.8 and 8.8.4.4

Also post the output of the command

route

 

[tango110]

You should try to setup your Vu+ box with the Google DNS instead of your router IP.
Google DNS are 8.8.8.8 and 8.8.4.4

Also post the output of the command

route

wont help beside it sometimes disconnect the Wireless Network, but the only way to get it to Work is using openpli or openvix image so this is really sad because i do like the blackhole image and has always being using it and the dongle also did Work with the bh image, but after version 2.02 only problems so sad so sad.

 

[tango110]

wont help beside it sometimes disconnect the Wireless Network, but the only way to get it to Work is using openpli or openvix image so this is really sad because i do like the blackhole image and has always being using it and the dongle also did Work with the bh image, but after version 2.02 only problems so sad so sad.

BlackHole 2.0.2 vusolo2
vusolo2 login: root
root@vusolo2:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.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.1.0 * 255.255.255.0 U 0 0 0 wlan0
root@vusolo2:~#

 

[angelofsky1980]

BlackHole 2.0.2 vusolo2
vusolo2 login: root
root@vusolo2:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 192.168.1.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.1.0 * 255.255.255.0 U 0 0 0 wlan0
root@vusolo2:~#[/quote]

Ok Seems that your default gateway is correctly setted up.

Try to issue this command from your box (into a telnet session):

ping www.google.com

 

[tango110]

Ok Seems that your default gateway is correctly setted up.

Try to issue this command from your box (into a telnet session):

ping www.google.com

it says bad adresss so not possible to ping www.google.com

 

[tango110]

it says bad adresss so not possible to ping www.google.com[/quote]

hey angelofsky so have you given up ?

 

[angelofsky1980]

hey angelofsky so have you given up ?

No, but I'm very busy at work.

 

[tango110]

No, but I'm very busy at work.

thats ok we can all be busy, but i can tell you that it is the same problem with vu+ duo with same dongle

 

[tango110]

thats ok we can all be busy, but i can tell you that it is the same problem with vu+ duo with same dongle

as i have being reading on this forum is if you turn of wpa/wpa2 psk protection then the dongle Works fine also same problem even with original vu+ dongle
this is not good news hope you can make a fix for it very soon have a nice weekend

ps my dlink dongles dwa-140 are rev b1 and rev b2

 

[roozbehk]

hi angelofsky, did you solve the problem??

 

[tango110]

hi angelofsky, did you solve the problem??

not solved,, buy new wifi dongles with chipset realtek 8192cu it you want wifi that works with wpa/wpa2 encryption . i did it and it works perfectly now i can throw both my dwa-140 out not usefull with new v2 blackhole software, sad but truely :-(

 

[roozbehk]

not solved,, buy new wifi dongles with chipset realtek 8192cu it you want wifi that works with wpa/wpa2 encryption . i did it and it works perfectly now i can throw both my dwa-140 out not usefull with new v2 blackhole software, sad but truely :-(

i think i must do it to. but i can wait until someone confirm my dongle have problem with new image and problem cant be solved. i fount one dongle with 8192cu chipset. but it is to expensive for me right now. )

 

[roozbehk]

tanx to angle for his work. problem is solved in version 2.0.3.

 

[angelofsky1980]

Thanks to all for your patience.
At the end I've downgraded the driver to the stable and fully working version.

Sorry for long days without wifi networks on your boxes.

 

[javier007]

Thanks to all for your patience.
At the end I've downgraded the driver to the stable and fully working version.

Sorry for long days without wifi networks on your boxes.

sorry angelofsky but i have seen a new problem with this drivers downgraded...in this last image.

my wifi dongle is dlink dwa-140 b-2 and with this last drivers it works slow...in wlan status it shows 54mb-100 mbs...when it works always 270-300mbs...with the 2.0.2 works fine at this point and in 1.7.9 too...

thanks in advance.

 

[angelofsky1980]

sorry angelofsky but i have seen a new problem with this drivers downgraded...in this last image.

my wifi dongle is dlink dwa-140 b-2 and with this last drivers it works slow...in wlan status it shows 54mb-100 mbs...when it works always 270-300mbs...with the 2.0.2 works fine at this point and in 1.7.9 too...

thanks in advance.

I will test this evening with solo2 and rev b2 of dwa140.
With b3 all works correctly


iPhone 5 & Tapatalk forever

 

[javier007]

I will test this evening with solo2 and rev b2 of dwa140.
With b3 all works correctly


iPhone 5 & Tapatalk forever

thanks angelofsky...my dongle is dwa-140 B2 firmware version 1.71 with vu duo..

i don´t know why this drivers worked well in BH 1.7.x and not in this one...it is a mistery ejejejej...

regards and thanks other time.

 

[angelofsky1980]

thanks angelofsky...my dongle is dwa-140 B2 firmware version 1.71 with vu duo..

i don´t know why this drivers worked well in BH 1.7.x and not in this one...it is a mistery ejejejej...

regards and thanks other time.

During last weekend I've spent some times around wireless support and I've discovered a bug.
I've already fixed it and I can post here that the DWA-140 problem you mention is part of the bug.
To solve it prior to the next image you should connect via telnet or SSH to your box and issue a simple command:

opkg remove kernel-module-rt2800usb --force-depends

In the next Image (or Revision) the rt2800usb driver will be drammatically reduced and reconfigured to be invoked only with specified devices and not for other wifi sticks governed by chipset vendor driver that are included into BH images.

I've tested the above command with my Vu+Uno and a DWA-140 B2 FW 1.31.
Initially the device will be detected as rt2800usb device and doesen't work properly (variable speed and other problems with my wireless router)
After launch the command, I've reconfigured my box and now my DWA device works as expected (270Mbit/s) and uses the properly driver.

I would like to remember that this modification will be included in the next Image / Revision.