On Jul 6, 2021, at 11:58 AM, Justin Mann via <w9fyi@...> wrote:

****Update****
I recompiled the Qnet gateway app, choosing the board as a d-star modem, and that appears to work where as using an MMDVM host does not. ?DO full duplex mmdvm boards behave differently?

On Jul 6, 2021, at 9:50 AM, Justin Mann via <w9fyi@...> wrote:

FOlks,
I’ve just compiled my Qnet gateway build on one of the boards put out by n5boc:
aka, Lonestar Semi conductor, and the board is a full duplex board. ?I uninstalled the configuration, created a new configuration indicating that my gateway was using an mmdvm host, and then recompiled the gateway. ?The gateway seems to work fine, but when I key, and unkey my radio, I get a sound that is kind of like some weird monster, and then I hear the confirmation of transmission. ?Is there any setting that I can change to aleviate this?
Thanks,
Justin

On Jul 6, 2021, at 9:50 AM, Justin Mann via groups.io <w9fyi@...> wrote:

FOlks,
I’ve just compiled my Qnet gateway build on one of the boards put out by n5boc:
aka, Lonestar Semi conductor, and the board is a full duplex board. I uninstalled the configuration, created a new configuration indicating that my gateway was using an mmdvm host, and then recompiled the gateway. The gateway seems to work fine, but when I key, and unkey my radio, I get a sound that is kind of like some weird monster, and then I hear the confirmation of transmission. Is there any setting that I can change to aleviate this?
Thanks,
Justin

On Jun 20, 2021, at 4:23 PM, Ryan Matthew Headley <headley.ryan@...> wrote:

Hello Justin,

If you are still wondering, I may be able to help.

In several places in YSFGateway.qn, there are configurations for the paths to files necessary for YSFGateway to start and function correctly.?

Line 29 in your file is the path to the log.? YSFGateway will not run unless it can find and write to that path.? The standard log directory is "/var/log".? It is advisable to create another directory with /var/log so that it doesn't get too chaotic in the general log directory.? Fixing this line is a two-step process:? 1) create the directory "/var/log/ysfgateway", then list that as the location on line 29.

Lines 52 and 65 have a similar problem. QnetGateway installs YSFGateway as a service running at the root level, so paths like "./YSFhosts.txt" won't cut it.? If the YSFClients directory is in you home directory, the path would be:? /home/[username]/YSFClients/YSFGateway/YSFHosts.txt"? in line 52.? Line 65 should be same, but point to FCS file.

On Jun 7, 2021, at 11:11 AM, John F Davis <wa8yxm@...> wrote:

No just D-star and that in terminal mode... But I was not even getting to that point For some reason on the "Coolspot" (What I call it) Pi I could not get SSH to work for initial set up.. Pulled the card from one of my hotspots and put the card in that. Got it all configured and working.. It is now all re-configured, working, in fact I'm listening to it. I was able to log in via ssh and play my recorded voice-mail file (Though I did have to re-make that file as well) And hopefully I have a fully configured back up card too.

One more task to go but it's minor and won't mess up anything (edit wifi Supplicant file to dual search)

"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 Monday, June 7, 2021, 11:49:28 AM EDT, Justin Mann via <w9fyi@...> wrote:

John,

Is your build a multi-protocol build, in other words, can you support d-star, DMr, and whatever else, or do you just use d-star?

Just curious.

On Jun 7, 2021, at 10:32 AM, John F Davis <wa8yxm@...> wrote:

Problem solved. IT WAS hardware. I reburned the cards (yet again) copied wi-fi Supplicant and ssh to card exactly as before. popped it in a DIFFERENT Raspberry pi-zero.. one card is configured and working (And I can SSH into it normally now that it loaded SSH) and the other one is ... Getting there (Doing the Make Dash as I type) Configuration of back up card will follow shortly (Iin the alternate PI) then I need to restore pi#2 to it's originally scheduled duties (sudo shutdown, de-power pull card replace with original card for that pi reboot and re-configure)


"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 Sunday, June 6, 2021, 05:55:39 AM EDT, John F Davis <wa8yxm@...> wrote:

I tripped over the box with one or two spare Pi-zero's last night today or tomorrow depending on .. this is a busy weekend... I'll give a try to a brand new pi

"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 Sunday, June 6, 2021, 12:02:42 AM EDT, Justin Mann via <w9fyi@...> wrote:

Yep that is the same issue that I’ve had, working with the wifi builder that is on the ?website. ?I was able to find another pi with an ethernet connection. ?However, I think were I in this situation again, I would find a usb-c ethernet adapter, and connect it to the pi-0 at least until you can get the wi-fi enabled. ?Then you can stick it back into the junk drawer until you need it the next time.

I hope this helps,

Justin

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 7, 2021, at 11:11 AM, John F Davis <wa8yxm@...> wrote:

No just D-star and that in terminal mode... But I was not even getting to that point For some reason on the "Coolspot" (What I call it) Pi I could not get SSH to work for initial set up.. Pulled the card from one of my hotspots and put the card in that. Got it all configured and working.. It is now all re-configured, working, in fact I'm listening to it. I was able to log in via ssh and play my recorded voice-mail file (Though I did have to re-make that file as well) And hopefully I have a fully configured back up card too.

One more task to go but it's minor and won't mess up anything (edit wifi Supplicant file to dual search)

"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 Monday, June 7, 2021, 11:49:28 AM EDT, Justin Mann via <w9fyi@...> wrote:

John,

Is your build a multi-protocol build, in other words, can you support d-star, DMr, and whatever else, or do you just use d-star?

Just curious.

On Jun 7, 2021, at 10:32 AM, John F Davis <wa8yxm@...> wrote:

Problem solved. IT WAS hardware. I reburned the cards (yet again) copied wi-fi Supplicant and ssh to card exactly as before. popped it in a DIFFERENT Raspberry pi-zero.. one card is configured and working (And I can SSH into it normally now that it loaded SSH) and the other one is ... Getting there (Doing the Make Dash as I type) Configuration of back up card will follow shortly (Iin the alternate PI) then I need to restore pi#2 to it's originally scheduled duties (sudo shutdown, de-power pull card replace with original card for that pi reboot and re-configure)


"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 Sunday, June 6, 2021, 05:55:39 AM EDT, John F Davis <wa8yxm@...> wrote:

I tripped over the box with one or two spare Pi-zero's last night today or tomorrow depending on .. this is a busy weekend... I'll give a try to a brand new pi

"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 Sunday, June 6, 2021, 12:02:42 AM EDT, Justin Mann via <w9fyi@...> wrote:

Yep that is the same issue that I’ve had, working with the wifi builder that is on the ?website. ?I was able to find another pi with an ethernet connection. ?However, I think were I in this situation again, I would find a usb-c ethernet adapter, and connect it to the pi-0 at least until you can get the wi-fi enabled. ?Then you can stick it back into the junk drawer until you need it the next time.

I hope this helps,

Justin

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 7, 2021, at 10:32 AM, John F Davis <wa8yxm@...> wrote:

Problem solved. IT WAS hardware. I reburned the cards (yet again) copied wi-fi Supplicant and ssh to card exactly as before. popped it in a DIFFERENT Raspberry pi-zero.. one card is configured and working (And I can SSH into it normally now that it loaded SSH) and the other one is ... Getting there (Doing the Make Dash as I type) Configuration of back up card will follow shortly (Iin the alternate PI) then I need to restore pi#2 to it's originally scheduled duties (sudo shutdown, de-power pull card replace with original card for that pi reboot and re-configure)


"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 Sunday, June 6, 2021, 05:55:39 AM EDT, John F Davis <wa8yxm@...> wrote:

I tripped over the box with one or two spare Pi-zero's last night today or tomorrow depending on .. this is a busy weekend... I'll give a try to a brand new pi

"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 Sunday, June 6, 2021, 12:02:42 AM EDT, Justin Mann via <w9fyi@...> wrote:

Yep that is the same issue that I’ve had, working with the wifi builder that is on the ?website. ?I was able to find another pi with an ethernet connection. ?However, I think were I in this situation again, I would find a usb-c ethernet adapter, and connect it to the pi-0 at least until you can get the wi-fi enabled. ?Then you can stick it back into the junk drawer until you need it the next time.

I hope this helps,

Justin

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 7, 2021, at 10:32 AM, John F Davis <wa8yxm@...> wrote:

Problem solved. IT WAS hardware. I reburned the cards (yet again) copied wi-fi Supplicant and ssh to card exactly as before. popped it in a DIFFERENT Raspberry pi-zero.. one card is configured and working (And I can SSH into it normally now that it loaded SSH) and the other one is ... Getting there (Doing the Make Dash as I type) Configuration of back up card will follow shortly (Iin the alternate PI) then I need to restore pi#2 to it's originally scheduled duties (sudo shutdown, de-power pull card replace with original card for that pi reboot and re-configure)


"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 Sunday, June 6, 2021, 05:55:39 AM EDT, John F Davis <wa8yxm@...> wrote:

I tripped over the box with one or two spare Pi-zero's last night today or tomorrow depending on .. this is a busy weekend... I'll give a try to a brand new pi

"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 Sunday, June 6, 2021, 12:02:42 AM EDT, Justin Mann via <w9fyi@...> wrote:

Yep that is the same issue that I’ve had, working with the wifi builder that is on the ?website. ?I was able to find another pi with an ethernet connection. ?However, I think were I in this situation again, I would find a usb-c ethernet adapter, and connect it to the pi-0 at least until you can get the wi-fi enabled. ?Then you can stick it back into the junk drawer until you need it the next time.

I hope this helps,

Justin

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 5, 2021, at 6:23 PM, John F Davis <wa8yxm@...> wrote:

The router seeds it. both routers see it depending on which wifi_Supplicant I use. But that's as far as it goes.

"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 Saturday, June 5, 2021, 06:14:16 PM EDT, Justin Mann via <w9fyi@...> wrote:

Trust me, I can totally relate, becuase I knew I had imaged the thing correctly, and yet it refused to connect to my wifi.

??

I fought for days trying to get this pi working for me… It wasn’t fun

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.

On Jun 5, 2021, at 3:45 PM, Tom Early <n7tae@...> wrote:

I agree, if you have a new OS on a Pi Zero W and can see it on your home router, then that pretty much has to mean it installed your wpa_supplicant.conf file okay, so there must be a problem with ssh. I don't think it particularly matters, but when I create the /boot/ssh file, it's just an empty file. Be careful not to add some trailing white-space on the filename, and, of course, no filename extensions that sometimes windows can help but adding.

Unfortunately, you only get one shot at this, once your system does it's initial boot, you can't do the /boot/ssh trick again to enable ssh on a card that has already booted. As a postmortem, you can pop the card and see if the /boot/ssh file is still there, because if it is, then maybe you can look it over carefully to try to figure out what went wrong.

Since you can't get in from either your Windows putty app or your chromebook, I think you have to start over again.

One more thing, according to your original message, it seems like you making the card a desktop OS. You should use the "lite" (no-gui) OS. Then after you've done all you need to do with raspi-config, you'll need to "sudo apt install build-essential git" to install git, g++ and make because not all of these are on the "lite" OS.