https://github.com/motdotla/ansible-pi
First thing is you need a file called ‘ssh’ on the raspbian to enable it:.
https://www.raspberrypi.org/forums/viewtopic.php?t=144839
ok so I found the IP address of the PI
root@chrx:~# nmap -sP 192.168.101.0/24
Starting Nmap 7.60 ( https://nmap.org ) at 2020-04-05 17:06 UTC
Nmap scan report for _gateway (192.168.101.1)
Host is up (0.0026s latency).
MAC Address: B8:69:F4:1B:D5:0F (Unknown)
Nmap scan report for 192.168.101.43
Host is up (0.042s latency).
MAC Address: 28:0D:FC:76:BB:3E (Sony Interactive Entertainment)
Nmap scan report for 192.168.101.100
Host is up (0.049s latency).
MAC Address: 18:F0:E4:E9:AF:E3 (Unknown)
Nmap scan report for 192.168.101.101
Host is up (0.015s latency).
MAC Address: DC:85:DE:22:AC:5D (AzureWave Technology)
Nmap scan report for 192.168.101.103
Host is up (-0.057s latency).
MAC Address: 74:C1:4F:31:47:61 (Unknown)
Nmap scan report for 192.168.101.105
Host is up (-0.097s latency).
MAC Address: B8:27:EB:03:24:B0 (Raspberry Pi Foundation)
Nmap scan report for 192.168.101.111
Host is up (-0.087s latency).
MAC Address: 00:24:D7:87:78:EC (Intel Corporate)
Nmap scan report for 192.168.101.121
Host is up (-0.068s latency).
MAC Address: AC:E0:10:C0:84:26 (Liteon Technology)
Nmap scan report for 192.168.101.130
Host is up (-0.097s latency).
MAC Address: 80:5E:C0:52:7A:27 (Yealink(xiamen) Network Technology)
Nmap scan report for 192.168.101.247
Host is up (0.15s latency).
MAC Address: DC:4F:22:FB:0B:27 (Unknown)
Nmap scan report for chrx (192.168.101.127)
Host is up.
Nmap done: 256 IP addresses (11 hosts up) scanned in 2.45 seconds
if nmap is not installed,
apt-get install nmap
Connect to whatever IP it is
ssh -vvvv pi@192.168.101.105
Are you sure you want to continue connecting (yes/no)? yes
Cool, and to set up wifi, let’s check out this ansible script https://github.com/motdotla/ansible-pi
$ sudo apt update $ sudo apt install software-properties-common $ sudo apt-add-repository --yes --update ppa:ansible/ansible $ sudo apt install ansible
ok 58MB install…
# ansible-playbook playbook.yml -i hosts –ask-pass –become -c paramiko
PLAY [Ansible Playbook for configuring brand new Raspberry Pi]
TASK [Gathering Facts]
TASK [pi : set_fact]
ok: [192.168.101.105]
TASK [pi : Configure WIFI] **
changed: [192.168.101.105]
TASK [pi : Update APT package cache]
[WARNING]: Updating cache and auto-installing missing dependency: python-apt
ok: [192.168.101.105]
TASK [pi : Upgrade APT to the lastest packages] *
changed: [192.168.101.105]
TASK [pi : Reboot] **
changed: [192.168.101.105]
TASK [pi : Wait for Raspberry PI to come back] **
ok: [192.168.101.105 -> localhost]
PLAY RECAP ****
192.168.101.105 : ok=7 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0
And I’ll unplug the ethernet and try connect by ssh again
Ah, but it’s moved up to 192.168.1.106 now
nmap -sP 192.168.101.0/24 (I checked again) and now it was ‘Unknown’, but ssh pi@192.168.101.106 worked
(If you can connect to your router, eg. 192.168.0.1 for most D-Link routers, you can go to something like Status -> Wireless, to see connected devices too, and skip the nmap stuff.)
I log in, then to configure some stuff:
sudo raspi-config
Under the interfaces peripheral section, Enable the camera and I2C
sudo apt-get install python-smbus
sudo apt-get install i2c-tools
ok tested with
raspistill -o out.jpg
Then copied across from my computer with
scp pi@192.168.101.106:/home/pi/out.jpg out.jpg
and then make it smaller (because trying to upload the 4MB version no)
convert out.jpg -resize 800×600 new.jpg
Cool and it looks like we also need to expand the partition
sudo raspi-config again, (Advanced Options, and first option)
Upon configuring the latest pi, I needed to first use the ethernet cable,
and then once logged in, use
sudo rfkill unblock 0
to turn on the wifi. The SSID and wifi password could be configured in raspi-config.
At Bitwäsherei, the ethernet cable to the router trick didn’t work.
Instead, as per the resident Gandalf’s advice, the instructions here
https://raspberrypi.stackexchange.com/questions/10251/prepare-sd-card-for-wifi-on-headless-pi
worked for setting up wireless access on the sd card.
“Since May 2016, Raspbian has been able to copy wifi details from /boot/wpa_supplicant.conf into /etc/wpa_supplicant/wpa_supplicant.conf to automatically configure wireless network access”
The file contains
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
country=«your_ISO-3166-1_two-letter_country_code»
network={
ssid="«your_SSID»"
psk="«your_PSK»"
key_mgmt=WPA-PSK
}Save, and put sd card in RPi. Wireless working and can ssh in again!
2022 News flash:
Incredibly, some more issues.
New issue, user guide not updated yet
https://stackoverflow.com/questions/71804429/raspberry-pi-ssh-access-denied
In essence, the default pi user no longer exists, so you have to create it and set its password using either the official Imager tool or by creating a userconf file in the boot partition of your microSD card, which should contain a single line of text: username:hashed-password
Default pi and raspberry:
pi:$6$/4.VdYgDm7RJ0qM1$FwXCeQgDKkqrOU3RIRuDSKpauAbBvP11msq9X58c8Que2l1Dwq3vdJMgiZlQSbEXGaY5esVHGBNbCxKLVNqZW1