I have a Raspberry Pi 3 Model B and was using the inbuilt Wifi interface with no problems. I was using it as a web server which I'd SSH into. However, after being unable to SSH into it, I've seen that it's now showing me the message "No wireless interfaces found" in the Raspbian UI taskbar.
What could cause this to stop working so suddenly without (to my knowledge) any messing around with config settings? How do I fix this? The Pi has just been sitting on my desk so I can't imagine it's physical damage.
The output of ifconfig
:
eth0 Link encap:Ethernet HWaddr b8:27:eb:4e:f2:ad
inet6 addr: fe80::b93d:28fd:d73e:d13f/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
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:1
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
wlan0 Link encap:Ethernet HWaddr b8:27:eb:1b:a7:f8
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:1 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:60 (60.0 B) TX bytes:0 (0.0 B)
Although wlan0
is displayed in this output, the Raspbian UI is not reflecting this.
I should also note, because this is often an issue, that my power supply should be sufficient as I'm using the official 2.5A PSU.
ifconfig
output contradicts this. It shows the wifi interface (wlan0
) asUP
. – goldilocks♦ May 3 '17 at 10:52ifconfig
. – goldilocks♦ May 3 '17 at 11:04