|
Folks,
i’ve just purchased an S card of 32 GB, and I’m going to try and install qnet gateway. Being totally blind, using any kind of external keyboard, and monitor connected to a Pi is going to not work at all. is there a way that I can get a version of Raspbian downloaded that might be preconfigured with my wifi information so that I could ssh in and perform the necessary steps?
Thanks,
Justin
|
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh pi@<internet address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
Hi Tom, I’m assuming that the pi is using port 22? ?Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ?
toggle quoted message
Show quoted text
On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh pi@<internet address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
Justin, if it’s a new image… possibly SSH is not enabled by default.
toggle quoted message
Show quoted text
On May 23, 2021, at 2:31 PM, Justin Mann via < w9fyi@...> wrote:
Hi Tom,I’m assuming that the pi is using port 22? ?Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ? On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at ??In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh ?pi@<internet?address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
Justin did you follow the instruction about enabling ssh by putting the file in the boot partition before booting?
On Sun, May 23, 2021, 15:14 Elden AI7HL < AI7HL@...> wrote: Justin, if it’s a new image… possibly SSH is not enabled by default. On May 23, 2021, at 2:31 PM, Justin Mann via < w9fyi@...> wrote:
Hi Tom,I’m assuming that the pi is using port 22?? Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ? On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at ??In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh ?pi@<internet?address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
that is what it appears. ?i’ve managed to get the Pi to see my wifi network, and it definitely does have a good ip address. ?I saw where if I put a blank filed named ssh in the boot partision of the SD card that that would enable ssh by default, but I’ve either donesomething incorrectly, or I was wrong in what I’ve read. ?I wonder if there is any kind of work around I might be able to use without having to reimage the Sd card. ?i wonder if ther is such a working image with ssh enabled somewhere?
toggle quoted message
Show quoted text
On May 23, 2021, at 5:14 PM, Elden AI7HL < AI7HL@...> wrote:
Justin, if it’s a new image… possibly SSH is not enabled by default. On May 23, 2021, at 2:31 PM, Justin Mann via < w9fyi@...> wrote:
Hi Tom,I’m assuming that the pi is using port 22? ?Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ? On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at ??In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh ?pi@<internet?address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
Yes. ?I did use stickys on my mac to create a file. ?It did add a .txt extension, but the dockumentation indicated that so long as the file was named ssh, that should work. If the txt extension is getting in the way is here a specific terminal command I could use to create a blank file called ssh, and try this again?
toggle quoted message
Show quoted text
On May 23, 2021, at 5:53 PM, John D Hays - K7VE < john@...> wrote:
Justin did you follow the instruction about enabling ssh by putting the file in the boot partition before booting? On Sun, May 23, 2021, 15:14 Elden AI7HL < AI7HL@...> wrote: Justin, if it’s a new image… possibly SSH is not enabled by default. On May 23, 2021, at 2:31 PM, Justin Mann via ??< w9fyi@...> wrote:
Hi Tom,I’m assuming that the pi is using port 22?? Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ? On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at ??In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh ?pi@<internet?address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
The terminal command to create an empty file would be “touch ssh” (If I recall correctly). I definitely think the .txt extension would be a problem.?
toggle quoted message
Show quoted text
On May 23, 2021, at 3:57 PM, Justin Mann via < w9fyi@...> wrote:
Yes. ?I did use stickys on my mac to create a file. ?It did add a .txt extension, but the dockumentation indicated that so long as the file was named ssh, that should work.If the txt extension is getting in the way is here a specific terminal command I could use to create a blank file called ssh, and try this again? On May 23, 2021, at 5:53 PM, John D Hays - K7VE < john@...> wrote:
Justin did you follow the instruction about enabling ssh by putting the file in the boot partition before booting? On Sun, May 23, 2021, 15:14 Elden AI7HL < AI7HL@...> wrote: Justin, if it’s a new image… possibly SSH is not enabled by default. On May 23, 2021, at 2:31 PM, Justin Mann via ??< w9fyi@...> wrote:
Hi Tom,I’m assuming that the pi is using port 22?? Anyway, I did manage to get the device to connect to my wifi network, and it does have the ip address of 192.168.1.32 but it is refusing the connection: ssh 192.168.1.32 should be the correct syntax? Thanks. . ? On May 23, 2021, at 12:17 PM, Tom Early < n7tae@...> wrote:
It is reasonably straightforward to do this, but first let me say, it is preferable to run hot-spots through a wired internet connection, if at all possible, You will have better digital voice performance with lower latency than if you run your hot-spot using WiFi. After you burn the image onto a micro SD card, you'll end up with two partitions, /root, where most of the Raspbian OS is installed and /boot, a smaller partition used during initial boot up. Before you try to boot from this new SD card, you'll want to create two files in the boot partition to enable both WiFi and remote access. To enable SSH, simply create an empty file, ssh, in the boot partition. This will cause the system to enable ssh on its first boot up. To enable WiFi, you simply need to provide a working wpa_supplicant.conf file and you do this by creating this file in the the boot partition. On the first boot, the OS will copy this file to the proper location and enable WiFi. This is explained, with an example, on the Raspbian website at ??In the wpa_supplicant.conf file, you just need to specify the WiFi network name (ssid) and the password (psk) and also set your country (country). If you want your Pi to optionally connect to a different WiFi network, it gets slightly more complicated because you also need to define a priority for each defined network. The first time you boot up on this card, give it some extra time. It will boot twice as it automatically expands the file system to incorporate all available space on the SD card. It will also take some extra time to make its first connection to your WiFi network. After the system is booted up, you should be able to ssh into it: ssh ?pi@<internet?address> Then do a "sudo apt update" followed by an "sudo apt upgrade". After that you can reset the pi user password and change your locale in the menu-driven command: raspi-config. After all that you're ready to download and build QnetGateway...
|
Good, it sounds like your wpa_suplicant file is okay. I'm pretty sure ssh.txt won't work. You need an "ssh" file in the boot directory without an extension. Start over and reimage the SD card. You can easily create the empty file with you make by doing a "touch ssh" when you are in the boot directory. It is a good skill to be able to quickly generate a fresh SD card and if you are going to run a single board computer headless, it's important to make sure ssh is running on first boot, and also WiFi if you need that to be able to log in. When you ssh into your pi, you need to specify both an IP address and an account, like "ssh [email protected]"
|
Hi there,
Is there a good terminal command that I could use the remove the current image on the SD card, and reimage it? ?Looks like my SD card is in /dev/disk4? ?I tried to use Etcher, and write over the top of the eisting image, but I’m not sure that is necesssarily best practice. ?Sorry for asking such questions. Thanks, Justin
toggle quoted message
Show quoted text
On May 23, 2021, at 10:55 PM, Tom Early < n7tae@...> wrote:
Good, it sounds like your wpa_suplicant file is okay. I'm pretty sure ssh.txt won't work. You need an "ssh" file in the boot directory without an extension. Start over and reimage the SD card. You can easily create the empty file with you make by doing a "touch ssh" when you are in the boot directory. It is a good skill to be able to quickly generate a fresh SD card and if you are going to run a single board computer headless, it's important to make sure ssh is running on first boot, and also WiFi if you need that to be able to log in. When you ssh into your pi, you need to specify both an IP address and an account, like "ssh [email protected]"
|
MacOS has "dd" and it works. I just tried it on my iMac. In terminal, cd to where your .img file is. Then type: sudo dd bs=4m if=2021-03-04-raspios-buster-armhf-lite.img of=/dev/rdiskX I hope you are using the latest lite image. The X is the disk number of your SD card. Note the "r" in /dev/rdisk. This device path is faster than /dev/disk. Even using the faster device, this will take a few minutes to write you image. FYI: "bs" is the block size of the transfer, 4 megabyte, "if" is the input file and "of" is the output file. Be very careful not to accidentally specify you mac drive for the "of" parameter. That would be very bad for your mac. Before you eject your sd card, there are __FOUR__ things you need to do to the boot partition:
- cd to the boot partition and do: touch ssh
- Copy your wpa_suplicant.conf file to the boot partition.
- Edit the cmdline.txt file and remove the reference to "
console=serial0,115200". This will disable the console on the serial-port on the RPi header and make that port available to your modem.
- Edit the config.txt file to disable bluetooth by adding "dtoverlay=pi3-disable-bt" to the file. If you need bluetooth, you can instead move it to a slighty slower device by using "dtoverlay=miniuart-bt" to the file. This dtoverlay line can go anywhere in the file.
If you don't do 3 and 4, QnetGateway won't be able to access the ZUM modem. But if you forget to do these two steps, you can do it later. You don't have to do it before your first boot. Steps 1 and 2 have to be done before your first boot. After you have made the four modifications to the boot partition, you can unmount the SD card with "diskutil unmountdisk /dev/diskX", where X is where you new SD card is. This will force all cached changes to the boot partition to be written to the SD card. You can then safely remove the SD card and give it a try. The first time you log into your new image, SSH may complain and refuse to do it, but it will tell you how to fix it so you can successfully connect. What's going on here is that SSH has detected that the hardware address no longer has the same software configuration and that could mean someone is trying to spoof you into connecting to a hacked system.
|
OK so I've finally gotten this all to work on my Pi-0. ?For some reason when I would edit the wpa_supplicant.conf file, and move it over to my SD card, the Pi-0 would not detect my wifi network. ?So after looking through numverous junk boxes, i found a Pi 3b+, connected it to ethernet, went through the raspiconfig, got the Pi localized, and wifi setup, put it back in to my Zumspot that I intend to use, and voila.
I've Now gone ahead, and completed steps one, and two of the MMDVM.readme file. ?However in step 3 I can't find the MMDVMhost directory. ?I can find the .ini files for steps 4, and 5. ?My plan is to enable this for all three modes, d-star, YSF, and DMR. ?Any help, and suggested values I would appreciate.
Thanks,
Justin
|
Tom Early
Elden AI7HL
John Hays - K7VE / WRJT-215