D-Link DWA-131 // Help Please

[millza.nz]

Hey there,

I have just been searching all over the web on how to make this dongle work. When i search what is connected via USB it shows up there. But will not show up in iwconfig, any ideas on how to get this to work.

Cheers

[Iedjee]

Hi.

The most important is to know which chipset it has... The page
http://www.wikidevi.com/wiki/D-Link_DWA-131_rev_A1
states that it is an RTL8191SU and that it uses Linus driver r8712u.
You'll find some other devices with that chipset on the wiki page:
http://elinux.org/RPi_VerifiedPeripherals.
So that's where you can start...

Good luck, EJ

[JeepGuy]

Hello, I too am new, but probably even newer than the original poster. I picked up the same dongle, the D-link DWA-131 because it is listed under verified Peripherals as:

DWA-131 USB ID 07d1:3303,Realtek RTL8192SU, 802.11n Wireless N Nano. Works out of the box on Raspbian “wheezy”

Ok, so I have a Pi, with an image of Wheezy on the SD card, what are all the steps to get the USB dongle working? I cannot find a link that explains it very well at all. This is my first step into linux, so please explain it maybe as you would to a child. What do I need to do? Should I be in the graphical session I get to from startx? Once I get it recognized, how do I set the ssid, password and such?

[DeFrivoleFramboos]

Hi there,
I'm in exactly the same situation as "JeepGuy".
I'm using the same dongle and Raspbian "Wheezy". The dongle's LED twinkles on and off.
lsusb shows the card and iwonfig shows the wlan0.
Then I followed the instructions found in this thread:
http://www.raspberrypi.org/phpBB3/viewt ... rk#p132277
look for Popiman's post. Replacing "wpa" by "wep" due to older hardware.
Restarting the network with (sudo /etc/init.d/networking restart) shows
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4 (or other numbers)
and then NO DHCPOFFERS receivers. Failed to bring up wlan0.
The dongle keeps on twinkling.
Any suggestions?

[dfreder1]

Same boat here. I managed to get the driver from realtek (8192cu.ko) from their website, unzip it, and put it in /lib/modules/3.1.9+/kernel/drivers/net/wireless/rtl819x/rtl8192. I made the last two directories because there was already a similar rtlxxxx directory and driver in that location.

Now trying to figure out the "insmod" command to tell it to use the 8182cu.ko driver. Will post again if successful.

[dfreder1]

okay, my card is working with the "r8712u" driver that I can see from an lsmod command. I'm not using the 8192cu at all.

The only thing I had to do was change /etc/network/resources as described in this thread:

http://www.raspberrypi.org/phpBB3/viewt ... es#p134160

See post by NickT Fri Jul 27, 2012 7:16 am.

mySSID and myPassword are inside quotes.

[hibol]

Hello,
Has anyone succeed with the DWA-131 dongle ?
If yes, it would be great ton post the solution you used with some details.
(Which driver has been downloaded, how it has been installed, and what modifications has been made to the configurations files.)
Thank you !

[JeepGuy]

I shocked myself and got it working. Basically, you only have to edit the file in the link above, but I had no idea how to go about doing that. Here is what worked for me.

What you ultimately need to do is to modify the file /etc/network/interfaces to be:

Code: Select all

auto lo wlan0

iface lo inet loopback
iface eth0 inet dhcp
iface wlan0 inet dhcp
wpa-ssid “JeepGuyWiFi”
wpa-psk “JeepsAreAwesome”

Substitute JeepGuyWiFi for your SSID
Substitute JeepsAreAwesome for your Password

To edit the file, at the command line (after you boot and type pi, then raspberry) type:
sudo vi /etc/network/interfaces
which will open the file in the vi editor as a super user so you can save the read only file (more info on the vi editor and how to use it here http://www.computerhope.com/unix/uvi.htm)

It will open the original file in the vi editor which should likely look like:

auto lo

iface lo inet loopback
iface eth0 inet dhcp
~
~

To use the vi editor, use the arrow keys and move your cursor to the end of the first line (auto lo) and press the i key (to insert text) and type wlan0. If it moves the o from lo, don’t worry, but you’ll have to fix that. To fix it, press the ESC key (to exit insert mode), use the arrows to move to where the extra “o” is and press the x key to delete the o at the end of the line, then use the arrows to go to where the “o” is supposed to be, press the i key again and replace the “o”. Then go to the end of the last line, press i and add the rest.
Press the ESC key once you have it all entered and then type :q to quit and save the file.
This should bring you back to a command prompt. Type sudo reboot to reboot.
While it is rebooting you should see some extra stuff regarding listening, sending, DHCPDISCOVER on wlan0, see some ip addresses and such.
Log in (Pi, Raspberry) Type startx and open midori and you should be able to browse the internet.

Maybe someone can chime in with a more elegant way to edit the file, but this finally worked for the DWA-131

[hibol]

Hi JeepGuy,
Thanks for the explanation. You can also modify the file with the editor Nano, which is a little easier to use than Vi I think.
The command line stays the same except that you replace vi by nano.
I have exactly the same configuration file as you, and it worked yesterday with a certain network.
Then I moved home and replaced the network informations to have the connection working for my wifi network, but it won't connect !

I don't know what to do, I am sure that the SSID and the wpa key are correct...
The command

Code: Select all

sudo iwlist wlan0 scan

shows up my network, but when I type

Code: Select all

sudo ifup wlan0

, it fails ! Even if I reboot my Pi.
I tried with a powered hub, and without, but the result is the same : no connection.
What is very strange is that I had it working in another place, with another network (while it was working, I made an rpi-update).

I hope someone can help me.

[ramesse]

Hi all,
I am having problems with Rasp pi and DWA-131 too...
Troubles with configuration were "solved" by using wicd tool. It configures wifi and I was finally able to connect to the wifi. But... I had to set up static IP, there was no succesful receiving IP from my DHCP (which is working!). That would not be a problem, but wicd disconnects, or lose connection after minute or two. What can I do with these disconnections?
Rasp pi is practically "out of the box", only wicd installed/changed.. Wifi dongle is connected directly to rasppi, no powered hub at all.
Thanks.

[JeepGuy]

Mine is on a powered hub along with my wireless mouse & keyboard dongle. I was getting erratic results with the mouse when it was plugged directly into the pi which cleared up when I switched to the hub, so I figured the wifi dongle would be happier with full power too. So, I have a powered 4 port hub with 1 port for the wifi, 1 for the keyboard/mouse dongle, and 1 to power the pi.

[DeFrivoleFramboos]

Hi,
I already made a post in here earlier. My dongle works now since the old computer is updated and now everything is WPA insteads of WEP. WEP will not work with this dongle. The only thing I changed is what Jeepguy already said.
sudo leafpad /etc/network/interfaces
and then
auto lo

iface lo inet loopback
iface eth0 inet dhcp
auto wlan0
iface wlan0 inet dhcp
wpa-ssid "YOURID"
wpa-psk "YourPassword"

The dongle only worked with (I think) the raspbian wheezy i downloaded onto an SD-card. It doesn' t work yet with the preloaded card I purchased from RS)components.

(sent from my Raspberry PI)

[lordcaine]

Jeepguy!

I want to thank you so much for your findings and for sharing them. I could not get my DWA-131 working until I read your simple explantion of the edits to the /etc/network/interfaces file. Once I put them in it came right up!

Thanks!!!!

Arthur

[vaab]

Hum, this doesn't always work. I bought the DL-131 as it was recommended in the wiki.

I tried this with my fonera as wifi provider, and I couldn't make it to work.
I tried with my Freebox v5 (a french ADSL provider's modem), and it worked.

To gather more info, here are the spec of the Fonera's wifi:

FONERA -- NOT WORKING

Code: Select all

                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.457 GHz (Channel 10)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 12 Mb/s
                              24 Mb/s; 48 Mb/s
                    Extra:rsn_ie=30140100000fac020100000fac020100000fac020000
                    IE: IEEE 802.11i/WPA2 Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK

to compare to Freebox's specs -- WORKING:

Code: Select all

                    Protocol:IEEE 802.11bg
                    Mode:Master
                    Frequency:2.412 GHz (Channel 1)
                    Encryption key:on
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
                              9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s
                              48 Mb/s; 54 Mb/s
                    Extra:wpa_ie=dd1a0050f20101000050f20202000050f2020050f20401000050f202
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (2) : TKIP CCMP
                        Authentication Suites (1) : PSK

Failure while attempting to connect to Fonera will appear as this:

Code: Select all

root@raspberrypi:~# ifup wlan0
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/wlan0/cc:b2:55:b1:67:8e
Sending on   LPF/wlan0/cc:b2:55:b1:67:8e
Sending on   Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 19
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
Unable to obtain a lease on first try.  Exiting.
Failed to bring up wlan0.

While on the freebox, it manages to get an IP at this stage.

any ideas ?

[serosenstein]

I just bought this wireless dongle today, I was having trouble staying connected to my wifi network. It would see the networks, attempt to connect and then when trying to get or set an IP it would disconnect and re-prompt for the password.

I am using the Fedora 17 Raspi (Test) remix: http://scotland.proximity.on.ca/raspber ... 7/latest/

I was able to resolve the issue, from what I can tell, by commenting out the IPv6 and some other stuff stuff in the /etc/sysconfig/network-scripts/ifcfg-<YOUR_SSID>

Code: Select all

ESSID="YOUR_SSID"
MODE=Managed
KEY_MGMT=WPA-PSK
TYPE=Wireless
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
#IPV6INIT=yes
#IPV6_AUTOCONF=yes
#IPV6_DEFROUTE=yes
#IPV6_FAILURE_FATAL=no
NAME=YOUR_SSID
UUID=a66ec13e-d912-4848-bd17-d8ce8XXXXXX
ONBOOT=yes
HWADDR=CC:B2:55:BD:XX:XX
#WPA_ALLOW_WPA=yes
WPA_ALLOW_WPA2=yes
#PEERDNS=yes
#PEERROUTES=yes
#IPV6_PEERDNS=yes
#IPV6_PEERROUTES=yes
#IPV6_PRIVACY=rfc3041

Not sure how useful this will be for the Debian guys...

[hermanhermitage]

WEP will not work with this dongle.

I just got a D-Link DWA-131, and managed to get WEP working with the following in /etc/network/interfaces:

Code: Select all

auto lo wlan0
iface lo inet loopback
iface eth0 inet dhcp
iface wlan0 inet dhcp
  wireless-key 0123456789
  wireless-essid NETWORK

where 0123456789 is my network key and NETWORK is the SSID of the network.

I'm working direct from the USB (no powered hub) and a very close wireless router. Seems stable but havent thrashed it yet
Cheers

[saranga2000]

I just got myself a D-Link DWA 131 and tried some of the suggestions given in this thread unsuccessfully.
The easiest way I was able to get it up and running, was by following the instructions in http://elinux.org/RPi_VerifiedPeriphera ... i_Adapters for this adapter which is to use wicd to configure it.
1. Plug in the adapter ( before you start), and start it connected to a monitor.
i. if you dont want to connect to a monitor, then use ssh & vnc with the rpi connected to wired ethernet, and with the wifi adapter plugged in.
2. once it starts, and you see the blue lights blinking, install wicd with - typing the command in a terminal -

Code: Select all

sudo aptitude install wicd

3. It is best if you are connected to a montior or through vnc. Browse for wicd ( click on start, you should find it under Internet ). It will show up as Wicd_Network_Manager.
4. Your Wifi hotspot name should show up there. Click on automatically connect to this network, click on properties, choose WPA 1/2 passphrase, and type it in.
5. Restart the pi.

Your Pi should now be connected via wifi. If you are connected without a montior, use a tool like advanced ip scanner ( windows, www.advanced-ip-scanner.com) or nmap ( linux) to get the ip address of the Pi, so you can ssh in and more.