Difference between revisions of "Bering-uClibc 6.x - User Guide - Advanced Topics - Special case for the Raspberry PI Zero W"

From bering-uClibc
Jump to: navigation, search
(Special case for the Raspberry PI Zero W)
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
===Special case for the Raspberry PI Zero W===
+
===Raspberry PI Zero W direct WIFI logon===
  
  
  
If you own a '''Raspberry PI Zero W''' you can connect to it using the WIFI interface only, no need for the console access using GPIOs serial pins 14 and 15 with a TTL-serial-USB adapter.  
+
If you own a '''Raspberry PI Zero W''' you can connect to it using the WIFI interface only, no need for the console access using GPIOs serial pins 14 and 15 with a TTL-serial-USB adapter. This is an interesting feature if you want to use the lowest priced Zero which does not have a soldered GPIO pins header and want to keep it that way.  
  
 
You can obtain a bootable image file https://sourceforge.net/p/leaf/packages/ci/802bb63a523a058489004204ea8b7cab7370aa04/tree/PiZ.img from the LEAF distribution and transfer it to an SD card using '''dd''' or the Raspberry PI Imager program on Windows or Mac.  
 
You can obtain a bootable image file https://sourceforge.net/p/leaf/packages/ci/802bb63a523a058489004204ea8b7cab7370aa04/tree/PiZ.img from the LEAF distribution and transfer it to an SD card using '''dd''' or the Raspberry PI Imager program on Windows or Mac.  
  
Once the SD card is generated and is still in your PC, open it up and create a file '''wpa_supplicant.conf''' in the '''mmcblk0p1''' partition...
+
Once the SD card is generated and is still inserted in your PC, open it up and add a file '''wpa_supplicant.conf''' to it's existing content.
  
 
The content of the file should be:
 
The content of the file should be:
Line 21: Line 21:
 
  fast_reauth=1
 
  fast_reauth=1
 
   
 
   
  ### Example of basic WPA-PSK secured AP, uncomment the next 5 lines, add your own ssid and psk...
+
  ### Example of basic WPA-PSK secured AP, uncomment the next 4 lines, add in your own ssid and psk...
 
  #network={
 
  #network={
  #    ssid="ournet"
+
  #    ssid="yournet"
  #    psk="ourpassword"
+
  #    psk="yourpassword"
#    #psk="w243sd5f324asdf5123sadf54324"
+
 
  #}
 
  #}
 
   
 
   
Line 37: Line 36:
 
On bootup the /init.d/wpasupplicant startup script will look for this file presence on the boot media, and will copy it's content to /etc/wpasupplicant.conf . The script will then delete the file on the boot media.  
 
On bootup the /init.d/wpasupplicant startup script will look for this file presence on the boot media, and will copy it's content to /etc/wpasupplicant.conf . The script will then delete the file on the boot media.  
  
Wait a few minutes for the PI to load and run, find the PI Zero IP address ( using fing on your phone...) and from a browser type in the suitable URL http://123.456.789 . If faced with password login request, admin:admin should get you there.
+
Wait a few minutes for the PI to load and run, find the PI Zero IP address ( using fing on your phone...) and from a browser type in the URL http://pi.zero.ip.addr . If faced with a password login request, admin:admin should get you there.
 +
 
 +
You should make these changes permanent by running '''lrcfg''' with the '''s)''' option... remember the file on the media will be erased after the first boot. Before doing that though, if you don't want to leave "yourpassword" in plain sight you could use the result of the command "'''wpa_passphrase yournet yourpassword'''" which will give you a hash of "yourpassword" that you can copy to '''/etc/wpa_supplicant.conf''' .

Latest revision as of 20:15, 28 December 2020

Raspberry PI Zero W direct WIFI logon

If you own a Raspberry PI Zero W you can connect to it using the WIFI interface only, no need for the console access using GPIOs serial pins 14 and 15 with a TTL-serial-USB adapter. This is an interesting feature if you want to use the lowest priced Zero which does not have a soldered GPIO pins header and want to keep it that way.

You can obtain a bootable image file https://sourceforge.net/p/leaf/packages/ci/802bb63a523a058489004204ea8b7cab7370aa04/tree/PiZ.img from the LEAF distribution and transfer it to an SD card using dd or the Raspberry PI Imager program on Windows or Mac.

Once the SD card is generated and is still inserted in your PC, open it up and add a file wpa_supplicant.conf to it's existing content.

The content of the file should be:

# Minimal /etc/wpa_supplicant.conf to associate with open
#  access points. 

# path to UNIX socket control interface
ctrl_interface=/var/run/wpa_supplicant

eapol_version=1
ap_scan=1
fast_reauth=1

### Example of basic WPA-PSK secured AP, uncomment the next 4 lines, add in your own ssid and psk...
#network={
#    ssid="yournet"
#    psk="yourpassword"
#}

### Associate with any open access point
###  Scans/ESSID changes can be done with wpa_cli
network={
        key_mgmt=NONE
}


On bootup the /init.d/wpasupplicant startup script will look for this file presence on the boot media, and will copy it's content to /etc/wpasupplicant.conf . The script will then delete the file on the boot media.

Wait a few minutes for the PI to load and run, find the PI Zero IP address ( using fing on your phone...) and from a browser type in the URL http://pi.zero.ip.addr . If faced with a password login request, admin:admin should get you there.

You should make these changes permanent by running lrcfg with the s) option... remember the file on the media will be erased after the first boot. Before doing that though, if you don't want to leave "yourpassword" in plain sight you could use the result of the command "wpa_passphrase yournet yourpassword" which will give you a hash of "yourpassword" that you can copy to /etc/wpa_supplicant.conf .