I am experiencing exactly the same problem. I have a Pi 3 B that was successfully running piaware 8.2x for several years.
I have reimaged the SD card several times. I have tried BOTH wired and wireless as well as the default instructions that come with the 10.1 install (which has no mention of adding static/dynamic IP, selecting between wired and wireless).
For the wired, I added the following to the piaware-config.txt file:
I am no programmer, but I feel confident that there’s a bug in the software somewhere. The reason being is I was able to re-image to PiAware 8.2, added my wifi info into piaware-config.txt, booted up while connected to the monitor and saw a wifi connection after a minute or two.
My stats page shows info is now feeding to FlightAware, albeit with an anomaly notification that 10.1 is now current.
Do your wifi SSIDs or passphrases contain non-alphanumeric characters, or contain spaces? There’s a bug report in github issues about ' not being correctly handled, and it sounds like there might be more widespread problems with escaping quotes/spaces/etc
To get you Pi online (while you wait for a fix), can you setup a guest account on your wifi (with a restricted charactor set) and point your Pi to that.
It’s not ideal, but might get you going.
That is certainly an option. I, personally, would shy away from that approach because when flightaware gets the problem solved, it is going to require a new image file that will have to be installed, along with the attendant -config.txt updates. Not a big deal, just not something I would do.
I have the same problem - wlan0 down. Was working fine on the remote upgrade to 10.0.1 but when I re-imaged the card to 10.1 and put the same settings in my piaware-config with the feeder-id added, I see wlan0 down and eth0 down. My feeder is down until this gets fixed.
I can confirm the same issue others are reporting. Wireless only works when configured to use dhcp. Any/all attempts to configure with static address fails.
We’ll look into this asap. I’m going to assume this issue is also present on 10.0 and 10.0.1 SD card images but if anyone has a report of it working fine on those versions, let us know.
Doesn’t seem to be the case with 10.0.1. I re-imaged from 8.2 and then updated to 10.0.1 via the “Update and Restart Piaware” command from the stats page. That unit is successfully connected to FlightAware on Wifi and operating fine.
I just tried the Update and Restart and it did not work. I even tried to reimage from scratch and it was worse. I am using ethernet connection and I could not create an SSH file or copy over the config file as in Windows the image directory looked all *&%^%&%%^&%. It is back to 8.2
EDIT .. 8.2 works fine. My fan on my Raspberry Pi will not even work on 10.x but 8.2 looks to be fine.
The SD card image 10.1 is based on Bookworm, and has an App called “Network Manager”. You can configure STATIC IP using it’s utility “nmtui” (network manager text-based user interface)
NOTE If the first method given below fails, then try alternate method given in the next post below.
STEP-2:
Highlite “Edit a Connection” and press Enter Key. On the new screen, select “Wi-Fi Wireless”, then use arrow keys to select “Edit”. See screenshot below. Press Enter Key.
STEP-6:
On completion of Step-5 and pressing Enter Key, you will get following screen. Press “Add” and fill up the details (static IP address, DGateway address, DNS address), scroll down to OK button at bottom-right, and press Enter Key. On next screen, scroll down to “Quit” and press Enter Key. DONE.
STEP-2:
When you press Enter Key at the end of Step-1, following window will open. Scroll down till you see SSID of your WiFi. Select it and press Enter Key.
STEP-3:
When you press Enter Key at end of Step-2, A dialog will open “Connecting”. After a while a new dialog will open asking for your WiFi password. Enter the password and press Enter key.
