how do I set up the wifi

[muchotreeo258]

I tried going to the network manager and adding my connection, and it worked on my last install but because of over overscan issues I had to reinstall, and now it won't work.

[DougieLawson]

What's in your /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf?

Here's mine (set-up with a fixed IP address)
/e*/n*/interfaces

Code: Select all

auto lo
auto wlan0
iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
#wireless-power off
iface wlan0 inet manual
address 192.168.1.7
gateway 192.168.1.1
netmask 255.255.255.0
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet static
address 192.168.1.7
gateway 192.168.1.1
netmask 255.255.255.0

and /e*/wpa_*/wpa_supplicant.conf

Code: Select all

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

network={
 ssid="REDACTEDSSID"
 scan_ssid=1
 psk="redactedpassword"
}

[Lob0426]

Here is a simpler version that works for most people.
this is for WPA2

Code: Select all

cd /etc/network

Code: Select all

sudo nano interfaces

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp

wpa-ssid "your SSID"
wpa-psk "Your wifi password"

[DougieLawson]

Yours may be simpler but it's missing auto eth0 and auto wlan0 to get the interfaces started at boot up.

[MrEngman]

Yours may be simpler but it's missing auto eth0 and auto wlan0 to get the interfaces started at boot up.

And neither has mine but both eth0 and wlan0 connect when I boot/reboot. And both connect when booting if they are both connected.

Code: Select all

login as: pi
pi@192.168.16.27's password:
Linux raspberrypi 3.10.25+ #616 PREEMPT Mon Dec 23 18:13:02 GMT 2013 armv6l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Dec 27 06:35:37 2013
pi@raspberrypi ~ $ ifconfig
eth0      Link encap:Ethernet  HWaddr b8:27:eb:19:f0:e0
          inet addr:192.168.16.27  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:114 errors:0 dropped:0 overruns:0 frame:0
          TX packets:75 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12250 (11.9 KiB)  TX bytes:11407 (11.1 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr a0:f3:c1:25:7d:28
          inet addr:192.168.16.24  Bcast:192.168.16.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:57 errors:0 dropped:2 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7423 (7.2 KiB)  TX bytes:1028 (1.0 KiB)

And /etc/network/interfaces is currently

Code: Select all

pi@raspberrypi ~ $ cat /etc/network/interfaces
auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet dhcp
wpa-ssid "network-name"
wpa-psk "network-password"

allow-hotplug wlan1
iface wlan1 inet dhcp
wpa-ssid "network-name"
wpa-psk "network-password"

#iface wlan0 inet manual
#wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
#iface default inet dhcp
pi@raspberrypi ~ $

And no auto eth0 or auto wlan0/wlan1 and it's been pretty much similar to that since I started using the Pi in Apr 2012. auto eth0 was required before debian wheezy appeared but was remove in the default /etc/network/interfaces included since.

You really don't need auto wlan0 if you have allow-hotpug wlan0 included as they both behave similarly.


MrEngman

[muchotreeo258]

I dont have a network folder

[MrEngman]

I dont have a network folder

OK, what software image are you using? The above is typical for Raspbian. What are you using?


MrEngman

[muchotreeo258]

pidora

[MrEngman]

pidora

Ah. I've never tried Pidora so I have no idea how the wifi is set up on it. Will take a look and see how it is configured but it is way past my bed time now so I will have to do that in the morning.


MrEngman

[MrEngman]

Hi muchotreeo258,

Well I tried Pidora and I certainly won't be using it again. How complicated, almost as bad as Windows 8 to get working

Anyway I got the wifi working without any problem other than trying to figure out how to configure Pidora.

Ended up setting it to boot into a graphical window, logged in as root and then the window appeared with the menu bar across the top. Selected the network icon on the top right hand side and selected my wifi, input the password and it connected.

Logging in as a different user and the menu bar was not there and I couldn't get the network manager running or at least I could not see it running.


MrEngman

[klricks]

I tried going to the network manager and adding my connection, and it worked on my last install but because of over overscan issues I had to reinstall, and now it won't work.

Make sure you are using the network connect button on the top bar between the time and user name.
At first I was trying to use the network config under settings in the applications menu and could not get anything to work. Once I found that network button I had WIFI working in seconds.

I also bagged Pidora for now. It's just not ready for prime time. Simple things just don't work without a lot of fussing. I even run Fedora 19 on a desktop so I am somewhat familiar with it.