Enable ssh on first boot about nextcloudpi

[nachoparker]

This image is based in Raspbian, so there is no difference

If you place a file called ssh it indeed enables SSH

If you look at

https://github.com/nachoparker/qemu-raspbian-network/blob/master/qemu-pi.sh

The relevant code is

# prepare the image
SECTOR1=$( fdisk -l $IMG | grep FAT32 | awk '{ print $2 }' )
SECTOR2=$( fdisk -l $IMG | grep Linux | awk '{ print $2 }' )
OFFSET1=$(( SECTOR1 * 512 ))
OFFSET2=$(( SECTOR2 * 512 ))

mkdir -p tmpmnt
mount $IMG -o offset=$OFFSET1 tmpmnt
touch tmpmnt/ssh   # this enables ssh
umount tmpmnt

I use that everyday (automatically) to build NextCloudPi images, so I know it works.

You must have done something wrong... maybe you forgot to sync and umount?

[Plorenzo]

maybe I'm missing something but I unmount the SD (on my Mac) after I run:
sudo dd bs=1m if=NextCloudPi_03-31-17_FULL.img of=/dev/rdisk3
and I add the ssh file

After I insert the SD to the pi, attach the ethernet to the router, I find the IP the Pi has been assigned and I try
ssh [email protected]
the result is:
ssh: connect to host 192.168.1.73 port 22: Operation timed out

[nachoparker]

how are you adding the ssh file to the boot partition?

did you run sync before dd'ing the image to the SD?

Just to be sure:

1. mount image
2. touch bootmnt/ssh
3. sync
4. dd to SD card

[Plorenzo]

I'm not sure what you mean by sync, I add the file with touch from the boot directory.

This are the steps I'm doing:

1. Download image from https://ownyourbits.com/2017/02/13/nextcloud-ready-raspberry-pi-image/
2. Insert SD into mac
3. diskutil unmountDisk /dev/disk3
4. cd ~/Downloads
5. sudo dd bs=1m if=NextCloudPi_03-31-17_FULL.img of=/dev/rdisk3
6. cd /Volumes/boot
7. touch ssh
8. Eject SD
9. Insert SD into RPi
10. ssh [email protected]

And then I get one of the following error:

ssh: connect to host 192.168.1.73 port 22: Operation timed out
ssh: connect to host 192.168.1.73 port 22: Host is down

[nachoparker]

The steps look ok to me, but I do not own an apple computer, so I am not sure.

Try to type sync after step 7

In any case, it must be just the same as with any other Raspbian. The exact same

How do you know what IP you have to use? can you ping the IP you are trying to connect to?

Connect a TV and keyboard if you are stuck

[Plorenzo]

After some time trying to figure it out I think it has to do with DHCP no assigning a local IP to the Pi .
Any idea why it could be?
If I do the exact same steps with the raspbian image, works fine

[nachoparker]

I tested the issue and you are right:

as long as wicd is active, DHCP no longer appears to work.

I will disable it by default then

thanks for the feedback, I'll open a new issue with this

[nachoparker]

opened as a new issue #5

[Plorenzo]

Thank you for the contribution and the quick answers! I'm looking forward to try NextCloudPi :)