On May 28, 2021, at 6:41 AM, Justin Mann via <w9fyi@...> wrote:

I understand that part of it, but when I choose a menu option, do I then have to press the enter key to then enter the coresponding values? ?So when I’m in the IRCDDB menu option, I, and I need to enter my call sign which is option L, do I press L, and then the dialogue comes up for my callsign. ?I’m totally blind, and I use voiceover, so it’s not reading me that prompt. ?I can make this all work, I just have to set things up to read as expected.

On May 28, 2021, at 5:31 AM, John F Davis <wa8yxm@...> wrote:

First teh choice of module is up to you you will configure only one module on most MMDVM hats A, B or C traditionally B is 70cm I think C is 2 meters and A is for a 220 hat if such exists but you need not stick to that since only you will use it.

Once you finish configurine each seciton you "q" (Quit) out of that portion and return to the sub menu.
Before you exit qnconfigure you "w"rite the configuration to the card.

if you get it working let me know what you did because I was not able to get it to work with a hat. I think I know why but the key word is "Think" I've not yet tested the theory.


"Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis

On Thursday, May 27, 2021, 11:35:14 PM EDT, Justin Mann via <w9fyi@...> wrote:

FOlks,

I’ve had a heck of a time trying to get a version of Raspberry PI OS to successfully image to an SD card, or should I say boot and connect to my wifi.? I’ve created a wpa_supplicant.conf file, used touch to make a ssh file that I moved over to the boot partission of the SD card, and have done the necessary edits to enable the serial port, and disable bluetooth.? For whatever reason, there is something just acting weird with my attempt to install Raspberry Pi OS on this Pi 0W that I can’t quite work out, so…

I’ve done a little experimenting, and have been able to successfully ssh in to my Pi when I have my card that I use for Pi-star installed, and I was successfully able to get qnet installed, and have started to try and run the ./qnetconfig script.? When you are in the menus, and you are presented with the various modules, in my case I chose b, as I’m running an mmdvm hotspot, how do you move one choice to the next, so I know that I do need to go in to the IRCDDB menu, i, and login, l,once I’ve pressed the letter l to enter my callsign, do I then press enter, and then enter the desired values, followed by enter again when I’m finished?

Finally, is there a way that I can tel Pi-star not to load, but allow the Raspian OS to load so that I can use Qnet?? I’m assuming that having both running on a hotspot probably causes problems.

Thanks for the help folks,

Justin

On May 28, 2021, at 5:31 AM, John F Davis <wa8yxm@...> wrote:

First teh choice of module is up to you you will configure only one module on most MMDVM hats A, B or C traditionally B is 70cm I think C is 2 meters and A is for a 220 hat if such exists but you need not stick to that since only you will use it.

Once you finish configurine each seciton you "q" (Quit) out of that portion and return to the sub menu.
Before you exit qnconfigure you "w"rite the configuration to the card.

if you get it working let me know what you did because I was not able to get it to work with a hat. I think I know why but the key word is "Think" I've not yet tested the theory.


"Nothing adds excitement like something that is none of your business" Note I am not a doctor, I don't even play one on television John F Davis

On Thursday, May 27, 2021, 11:35:14 PM EDT, Justin Mann via <w9fyi@...> wrote:

FOlks,

I’ve had a heck of a time trying to get a version of Raspberry PI OS to successfully image to an SD card, or should I say boot and connect to my wifi.? I’ve created a wpa_supplicant.conf file, used touch to make a ssh file that I moved over to the boot partission of the SD card, and have done the necessary edits to enable the serial port, and disable bluetooth.? For whatever reason, there is something just acting weird with my attempt to install Raspberry Pi OS on this Pi 0W that I can’t quite work out, so…

I’ve done a little experimenting, and have been able to successfully ssh in to my Pi when I have my card that I use for Pi-star installed, and I was successfully able to get qnet installed, and have started to try and run the ./qnetconfig script.? When you are in the menus, and you are presented with the various modules, in my case I chose b, as I’m running an mmdvm hotspot, how do you move one choice to the next, so I know that I do need to go in to the IRCDDB menu, i, and login, l,once I’ve pressed the letter l to enter my callsign, do I then press enter, and then enter the desired values, followed by enter again when I’m finished?

Finally, is there a way that I can tel Pi-star not to load, but allow the Raspian OS to load so that I can use Qnet?? I’m assuming that having both running on a hotspot probably causes problems.

Thanks for the help folks,

Justin

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]"

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...

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...

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...

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...

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...

After quite a bit of playing around with this, there is a new version for DVAP users that will allow you to either configure your DVAP using its serial number, or its assigned device path (i.e., /dev/ttyUSB<X>). You only need to specify one, either a serial number or a device path. If you specify a serial number in qnconfig, the device path will be truncated to zero length. If you specify a device path in qnconfig, the DVAP serial number will be truncated to zero length.

Recently, github.com has enabled a new feature called "Discussions" under its own tab. I am thinking of shutting down all my groups.io groups in favor of using this new Discussions feature on github.com. I think it would make my live a little easier and less cluttered and perhaps it would have the same effect on on you too. In order to use the "Discussions" feature, I believe you have to have a github.com account, and it is very easy to sign up for an account. I believe that github.com (owned now by Microsoft) is very good about not sharing your account information with third parties.

I would like to know of your opinion of such a move, especially if you though it would be a bad idea and would not like to see my groups.io groups disappear.