<p>Just to add to Jim's email, if you're using WPA based authentication, have you got the supplicant installed?<br>
</p>
<div class="gmail_quote">On Jul 21, 2012 11:06 PM, "Dimitrios Siganos" <<a href="mailto:dimitris@siganos.org">dimitris@siganos.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jim,<br>
<br>
And welcome to the group. I am relatively new here too.<br>
<br>
The ifconfig "up" status could mean various things. I don't think it is<br>
a reliable indication of Wifi link status.<br>
<br>
Try instead the commands:<br>
* ip link<br>
* ip addr<br>
to get better reporting of network status.<br>
<br>
I don't think the problem is with the router. If you notice the counters<br>
for the Wifi interface, they are all zeros, which makes me thing that<br>
DHCP hasn't even tried to send a single packet.<br>
<br>
What could be wrong?<br>
<br>
1) You might not be getting a Wifi link. What kind of Wifi network are<br>
you connecting to? Have you tried to "open/unsecured" network?<br>
<br>
2) Maybe the Wifi link is up but DHCP is not triggered.<br>
<br>
Other useful commands:<br>
* ip monitor<br>
* iw event<br>
* iw dev wlan0 link<br>
* iwconfig<br>
<br>
Regards,<br>
Dimitris<br>
<br>
On 21/07/12 22:31, Jim Ford wrote:<br>
> I'm trying to get wifi set up on my raspberry pi.<br>
><br>
> I'm running the raspberry 'headless' with a network cable, and a ssh<br>
> using 'putty'.<br>
><br>
> The USB dongle driver works ok as indicated by lsusb and lsmod, and also<br>
> the wlan0 interface comes up, as shown below. Also iwlist wlan0 scan<br>
> shows my router (and others):<br>
><br>
> eth0 Link encap:Ethernet HWaddr b8:27:eb:d9:33:aa<br>
> inet addr:192.168.1.128 Bcast:192.168.1.255 Mask:255.255.255.0<br>
> inet6 addr: fe80::ba27:ebff:fed9:33aa/64 Scope:Link<br>
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
> RX packets:1039 errors:0 dropped:0 overruns:0 frame:0<br>
> TX packets:1452 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:63698 (62.2 KiB) TX bytes:190755 (186.2 KiB)<br>
><br>
> lo Link encap:Local Loopback<br>
> inet addr:127.0.0.1 Mask:255.0.0.0<br>
> inet6 addr: ::1/128 Scope:Host<br>
> UP LOOPBACK RUNNING MTU:16436 Metric:1<br>
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:0<br>
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)<br>
><br>
> wlan0 Link encap:Ethernet HWaddr 48:02:2a:eb:ae:b2<br>
> UP BROADCAST MULTICAST MTU:1500 Metric:1<br>
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0<br>
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0<br>
> collisions:0 txqueuelen:1000<br>
> RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)<br>
><br>
> The problem appears to be that although I'm getting an IP address from<br>
> my router for eth0, I'm not getting one for the wlan0 interface.<br>
><br>
> I'm wondering whether the eth0 interface somehow inhibits the wlan0 from<br>
> getting an IP<br>
><br>
> I'd be grateful for any pointers to where the problem might lie, please.<br>
><br>
><br>
> BTW. I only discovered the Watford Linux Group this evening. I'm a<br>
> Watford resident and have tinkered with Linux for some years, though I'm<br>
> no expert. I hope to get to the 'Sportsman' this Thursday.<br>
><br>
> Jim<br>
><br>
> _______________________________________________<br>
> Watford mailing list<br>
> <a href="mailto:Watford@mailman.lug.org.uk">Watford@mailman.lug.org.uk</a><br>
> <a href="https://mailman.lug.org.uk/mailman/listinfo/watford" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/watford</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Watford mailing list<br>
<a href="mailto:Watford@mailman.lug.org.uk">Watford@mailman.lug.org.uk</a><br>
<a href="https://mailman.lug.org.uk/mailman/listinfo/watford" target="_blank">https://mailman.lug.org.uk/mailman/listinfo/watford</a><br>
</blockquote></div>