Use sudo asl-show-version to obtain this information from the console or SSH
Asterisk Version: 22.2.0asl3-3.4.5-1deb12
ASL [app_rpt] : No Ethernet interface found for seeding global EID. You will have to set it manually.
I get this message WiFi info was entered when the SD card was imaged with Raspberry Pi Imager.
I don’t know where to go from here.
What platform (RPi, PC, VM, ...) and OS version/variant ?
Also, searching for the "No Ethernet interface found for seeding global EID" string in your favorite browser will likely provide some good insights.
Sorry, platform is RPi
OS: Debian GNU/Linux 12 (bookworm)
OS Kernel: 6.12.25+rpt-rpi-v8
As I am writing this reply, for the fifth time, I re-imaged the SD card and used balenaEtcher to write the image. Now, my wifi works. Now, I can't login per instructions with the user repeater and password allstarlink so I can finish the setup. Just won't let me.
You do NOT want to use balenaEtcher to write the ASL3 image to the SD card.
PLEASE follow our installation instructions @ ASL3 Appliance Installation - AllStarLink Manual and use the Raspberry Pi Imager application.
I followed these instructions four times to write the card with Raspberry Pi Imager. Does not give me internet access. Gonna try a couple more and see what happens.
Honestly, I have never had an issue using the Raspberry Pi Imager to write an ASL3 image to a SD card. Just remember to setup and apply the "OS customisation settings" (hostname, username and password, Wi-Fi SSID and password, etc).
Note: most of my RPi nodes are setup for Wi-Fi but I do have one Pi I've used with Ethernet. I had no issues with either interface.
The ASL3 Pi Appliance image will not work with balenaEtcher by default. balenaEtcher will not set the account information or other configuration properly. You could use the various boot .txt files like userconf.txt and a wpa_supplicant file. But that's a lot of unnecessary work.
References to a "repeater" account is from the old ASL image. It has no bearing on ASL3. You need to follow the directions WA3WCO posted.
I am having the same problem described here. I used the pi imager to image the asl3 image onto my SD card no problem. I placed the imaged card in the pi zero 2W and turned the pi on. It seems to boot up properly, but the wifi does not connect to my computer, so I cannot continue the installation. I read about port forwarding, but that was never mentioned in the installation instructions, and I cannot port forward on my router because it requires an IP address, which I can't get because it's not connected to the pi. Help!
One thing you need to know about the Raspberry Pi Zero 2 W is that it only supports 2.4GHz wireless networks. Make sure that you are providing the "2.4" network SSID info.
This may or may not help; on several occasions, I've had a problem with the Raspberry Pi Imager where it seems to cache the previous custom info that was loaded, so in effect the wrong wifi/login info is written to the sd card. I had to blank it out, start a write, abort, then fill everything in anew. No idea if this is some dumbass thing only I'm doing or not...
That’s what fixed mine also. I closed out the program, restarted it and put in the parameters. Wrote the image and it worked. Thanks to all for the help.
That's not the problem, but your response is appreciated.
So, when using the Raspberry Pi Imager application you set the "SSID" and "Password" of your 2.4GHz enabled Wi-Fi network into the "customisation" settings?
and you chose to apply those settings to the image that you flashed?
and was the desktop/laptop you are using to access the Pi Zero on the same Wi-Fi network?
Also, most Wi-Fi routers have a web page where you can review the connected devices. Have you confirmed that the Pi does not show up after booting (and waiting a few minutes after first applying power) ?
So what IS the problem? I wrote the image 4 times. It did not set an up address except for 127.0.0.1. When I wrote the image the fifth time after restarting the image program, typing in the exact same information, it functioned correctly. I would like to know the solution so I can do it correctly the next time I do an image. I plan on setting up a second pi and node for a different band and would hope to do it correctly the first try.
Yes to all. I also confirmed that the pi zero 2 W wifi works by installing a working SD card into it. It immediately connected to my computer. I've since read online that some of the pi imagers have some glitches, and one of them is the ability to connect to wifi.
Your earlier post got me thinking. I've done some online reading and I've found that some pi imagers seem to have some glitches. One of the glitches is the ability to connect to wifi consistently.
Huh? Where in the Raspberry Pi Imager application's "customisation" settings would you set an IP address?
In the "General" tab you want to "Set hostname" with the local hostname (e.g. node12345), "Set username and password" with your login information for the Pi, and "Configure wireless LAN" with the WiFi info. I also use the "Set locale settings" to set the time zone, and keyboard. In the "Services" tab you want to "Enable SSH".
That should be all you need.
When I want to flash an image for a different Pi I just start up the Raspberry Pi Imager, choose "EDIT SETTINGS", change the local hostname, "SAVE", click "YES" (to use the settings), and burn the image.
I have tried several things. A sd card burned a week ago works but no card that I have imaged in the last 5 days have had the wifi started when run in the boards it has to be in the image writer of the down loaded ASL3 code must be broken when will it be fixed? I suspect that it was broken with the latest either in the pi imager or in the allstar code bei g burned. This issue started when I updated the image. It has not worked once. Whats up with the wifi not working? I even down loaded what was supposed to be the previous release and now it doesnt work either. Is this issue being worked on?
If you are using the Pi zero 2 W it only does 2.4 GHz. But something is crapped up I dont know what it is. I burned 5 or 6 times last night and no, none, nada, on the wifi i verify that by using a monitor connected to the board.
And No it never starts even over night.
You perhaps should try a second SD card if you haven't already, just to rule that out.
Seen it here many times for unknown reasons. Save some hair ?