Raspberry Pi Forums

ng28 wrote:Hi MrEngMan

I did all download using my windows laptop, I use Huawei E586 Mifi with Vodafone data card form my primary internet use. Due to that issue with the file size and winzip error, today I tried downloading it using my Android Phone (Teathering) using 3 network sim.

Thanks for your help and glad to know that you found that details useful.

Others (I guess myengman you might be knowing this already)
Good News - wifi support for RTL8188CUS is now supported in new image and we can make our Pi run 50% faster, see this for details http://www.raspberrypi.org/archives/2008

Cheers

MrEngman wrote: And what a suprise MrEngman is mentioned on the Raspberry Pi home page. What an honour.

Made my day.

MrEngman wrote: MrEngman is mentioned on the Raspberry Pi home page. What an honour.
Made my day.

dom wrote:

MrEngman wrote: And what a suprise MrEngman is mentioned on the Raspberry Pi home page. What an honour.

Made my day.

We've been aware that using WiFi on the Pi has been pretty tough, especially with the out of tree RTL8188CUS driver.
This (huge) thread has allowed a lot of people to get up and running with Wifi, and also signalled to us there was a lot of demand.
(I actually used your script when getting my dad up and running with WiFi some weeks back).

Please try the new image, and see if WiFi does work "out of the box" as we hope. We'd be interested to hear any suggestions from you if you think any settings should be tweaked.
Thanks again.

thsBavR10 wrote:

MrEngman wrote: MrEngman is mentioned on the Raspberry Pi home page. What an honour.
Made my day.

Your contribution is not valued highly enough.
I think that a lot of Pi-users would have needed much more time, or were desperate without your scripts and the sustained support.
Therefore, again by me thank you!

Spectrose wrote:I'm beginning to think I have a bad dongle... I tried a fresh install of wheezy, with the new wifi setup, and was able to scan for networks, and join, but I had no internet access. If I ever disconnected from the network, the scan wouldn't work again. I would have to pull the dongle out and plug it in again. Still no network access, though, it appeared to be connected.

sudo ifdown wlan0
sudo ifup wlan0

sudo ifup --force wlan0

sudo /etc/network/interfaces restart

sudo ifup --force wlan0

iface wlan0 inet static             <<-- change from dhcp to static to use a static IP address
     address 192.168.1.10           <- static address settings to suit your network
     network 192.168.1.0
     netmask 255.255.255.0
     gateway 192.168.1.254

MrEngman wrote:Hi to everyone using the script.

A WARNING - DO NOT USE THE SCRIPT on the new 2012-09-18-wheezy-raspbian image. It will not work and messes up the /etc/network/interfaces file if you do use it - like I just found out.

Seems the configuration is expected to be done through the GUI.

Take a look here - http://www.raspberrypi.org/phpBB3/viewt ... 47#p176847

For those of you, like me, who keep well away from the GUI then too bad for the moment.

Dweeber wrote:

MrEngman wrote:Hi to everyone using the script.

A WARNING - DO NOT USE THE SCRIPT on the new 2012-09-18-wheezy-raspbian image. It will not work and messes up the /etc/network/interfaces file if you do use it - like I just found out.

Seems the configuration is expected to be done through the GUI.

Take a look here - http://www.raspberrypi.org/phpBB3/viewt ... 47#p176847

For those of you, like me, who keep well away from the GUI then too bad for the moment.

I'm actually doing the update now. Using the GUI is going to be interesting without a mouse. Hopefully, once I get one setup, I will see where the changes are made so that I can do them manually to the other system. That one doesn't even have a keyboard attached.

BTW... there appears to be a wpa_cli but I've never used it before... will try that after rebooting while on the keyboard.

More... can't use just keyboard on Startx... kinda figured that.
and wpa_cli is there, but I was not prepared for the list of commands I got when I did help
Need to look this command up and see if there are some simple scan, select, enter password etc.. commands

MrEngman wrote: Was just posting a reply to you in the Updating to the 2012-09-18-wheezy-raspbian image thread when I got an email about a message in this thread.

I've just set up the new image with the /etc/network/interfaces format used in the script. Like you I don't use the GUI much, in fact almost never.

I would suggest you copy your config to the new image and see what happens. I can't think of a reason why it shouldn't work.

I've a basic wpa_supplicant setup on one image just need to find it and then I'm going to try that.

It does look as though it's not necessary to use the GUI if you don't want to or cannot.

MrEngman

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
        ssid="brutus"
        psk="PASSWORD"
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        auth_alg=OPEN
}

Dweeber wrote: Now.. what did it change... Noticed that it added in /boot/wpa_supplicant.conf or physically in /etc/wpa_supplicant/wpa_supplicant.conf

The network section....

After

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

Code: Select all

network={
        ssid="brutus"
        psk="PASSWORD"
        proto=RSN
        key_mgmt=WPA-PSK
        pairwise=CCMP
        auth_alg=OPEN
}

So I think... you can add that and boot...

The part that kept messing me up was the CCMP... not sure I've seen that before. I was trying TK.. and was getting nowhere... then I used it which is the default and it worked (This was in the gui of course).

I seem to remember that you can put a priority and it will connect to the highest priority (or is it the lowest numbered one) first.

If this is true, it would not be hard to script something simple for command line.. scan for SSID's, enter which one and enter password and create the network section.

MrEngman wrote:For those of you, like me, who keep well away from the GUI then too bad for the moment.

MrEngman wrote: Seems the configuration is expected to be done through the GUI.

Take a look here - http://www.raspberrypi.org/phpBB3/viewt ... 47#p176847

For those of you, like me, who keep well away from the GUI then too bad for the moment.

asb wrote:

MrEngman wrote: Seems the configuration is expected to be done through the GUI.

Take a look here - http://www.raspberrypi.org/phpBB3/viewt ... 47#p176847

For those of you, like me, who keep well away from the GUI then too bad for the moment.

You should be able to just set up /etc/network/interfaces and a wpa_supplicant.conf just how you want, or use wpa_cli. The setup we went with seemed to be the one that would keep most people happy. Certainly worked out nicer than having wicd or network-manager take over all network config (and sucking up resources).

MrEngman wrote: For the moment I've set up /etc/network/interfaces to how I normally have it set, ignoring wpa_supplicant, and the wifi is running. Keep it simple etc.

MrEngman wrote: And I can swap dongles without problems which will be really handy for some as wlan persistent has been disabled. Set up an image with the wifi and save it and then duplicate SD cards for other Pi's using the same network and then it really will work "out of the box". Now lets see what happens when I connect two dongles.

MrEngman wrote:It doesn't appear to be broken.

You weren't sure about using a space in the network name (SSID). I tried with one of my access points and it appears to be OK using a space character in the name.

Can you define how you "disconnected from the network". Have you checked the output of command ifconfig wlan0 when connected and "disconnected"?

Unplugging and plugging back the dongle is one way to get it reconnected if its disconnected but there are other ways. This essentially causes the commands ifdown and ifup to be run automatically as the USB detects the wifi device is removed and then re-inserted.

The normal commands for taking a network down and back up are

Code: Select all

sudo ifdown wlan0
sudo ifup wlan0

for wifi wlan0. If the wifi gets disconnected from the wireless network say because the access point goes down it will not reconnect itself using the basic setup but needs to be told to reconnect. This can be done using commands ifdown and then ifup. However I tend to use the command

Code: Select all

sudo ifup --force wlan0

This can force a reconnect without having to use ifdown and saves having to take the network down and backup.

You could probably also reconnect if you ran the command

Code: Select all

sudo /etc/network/interfaces restart

If you "disconnect from the network" can you reconnect if you use the command

Code: Select all

sudo ifup --force wlan0

No need for sudo if logged in as root user.

Perhaps if you set up your wifi with a fixed IP it might help. What is your network access point? Does it use DHCP?

For a static IP the wlan0 settings in /etc/network/interfaces will need editing and changing to something like the following

Code: Select all

iface wlan0 inet static             <<-- change from dhcp to static to use a static IP address
     address 192.168.1.10           <- static address settings to suit your network
     network 192.168.1.0
     netmask 255.255.255.0
     gateway 192.168.1.254

dom wrote:
Please try the new image, and see if WiFi does work "out of the box" as we hope. We'd be interested to hear any suggestions from you if you think any settings should be tweaked.
Thanks again.

pmonro wrote: I tried to alter the interfaces file but it will not save and I do not know how to do it
Any suggestions appreciated
Regards

sudo nano /etc/network/interfaces

copper.hat wrote:Hi, thanks to MrEngman for a great script.

I am trying to get my Edimax EW-7811UN working with my hidden network.

I got the EW-7811UN working with my network ssid visible. I am using 2012-08-16-wheezy-raspbian, and the latest script from MrEngman. Works very nicely. I changed to using wpa_supplicant to see if that would allow me to hide my network ssid again. No luck.

Has anyone managed to connect to a hidden network with the EW-7811UN?

Thanks, Joe

relevant lines in /etc/network/interfaces
iface wlan0 inet dhcp
pre-up wpa_supplicant -d -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B

/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
ssid="my network"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="blah blah blah"
}

If the SSID is hidden, add the following option to the block: 
scan_ssid=1

MrEngman wrote:

copper.hat wrote:Hi, thanks to MrEngman for a great script.

I am trying to get my Edimax EW-7811UN working with my hidden network.

I got the EW-7811UN working with my network ssid visible. I am using 2012-08-16-wheezy-raspbian, and the latest script from MrEngman. Works very nicely. I changed to using wpa_supplicant to see if that would allow me to hide my network ssid again. No luck.

Has anyone managed to connect to a hidden network with the EW-7811UN?

Thanks, Joe

relevant lines in /etc/network/interfaces
iface wlan0 inet dhcp
pre-up wpa_supplicant -d -Dwext -iwlan0 -c/etc/wpa_supplicant.conf -B

/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
ssid="my network"
proto=RSN
key_mgmt=WPA-PSK
pairwise=CCMP TKIP
group=CCMP TKIP
psk="blah blah blah"
}

Well, there's plenty of people who've had the same problem and I'm not sure it can be done but I did find this.

Code: Select all

If the SSID is hidden, add the following option to the block: 
scan_ssid=1

Found that here https://wiki.archlinux.org/index.php/WPA_supplicant. Whether it works or not I've no idea. And there is a lot of stuff on the internet about hidden ssid's saying basically it's pointless and others saying it can actually be a bad thing to do.

MrEngman