[BUG] Configure Wi-Fi - No networks found

[custard2022]

Environment

• Camera: ZWO ASI678MC
• OS: Debian GNU/Linux 11 (bullseye) aarch64
• Allsky version: Version: v2023.05.01_04
• Pi model and amount of memory (512 MB, 1, 2, 4, or 8 GB): Raspberry Pi 4, 4GB

Bug Description

• Include a clear and concise description of what the bug is. Configure Wi-Fi has "No networks found" message, have been noticing it happening every time I go to the page. It works initially, but after some time it stops showing networks, even though I'm connected through a WiFi network. I'm still connected to WiFI, just not allowing me to change the netowrk.
• Can it be reproduced? If so, how? Happens every time for some reason, I think it works when not in capture mode.
• Did anything change? Any settings? Most issues occur after a change was made. No
• Please include the exact messages or a screenshot.
• If this is a configuration-related issue (or you are not sure), attach these files, appending ".txt" to their names first: Don't think so.

If you have program output or multi-line messages to include, add it like this so it formats correctly (note the lines with tildas): N/A

Log / configuration files

allsky.log

[EricClaeys]

@custard2022, does WiFi work and it's just that the WebUI page can't find any networks, or does WiFi itself stop working. If the former, then the "Configure WiFi" page is fixed in the next release. There was a bug that caused that page to report no networks when there were some.

[custard2022]

@EricClaeys ok thank you, sounds like you already have it figured out, yes, networks available but not showing in the Configure WiFi. Appreciate the quick response!

[briankkeyser]

I have a similar problem. Brand new raspi OS 64 is using end0 NOT eth0 as ethernet port. The lan dashboard reports "interface eth0 is down (because is is now called end0). I can access the website using the ethernet port address, but the uploads and refresh seem slow - like they are using wlan0 because AllSky does not know about eth0 renaming to end0.

[EricClaeys]

@briankkeyser, slow uploads are not an Allsky issue - it's something with your network or Pi. Allsky has no control over the network and simply uses it like any other process does. It has no idea if the underlying network is wired or wireless, nor does it care.

I have never heard of end0 before. Do you have a different network adapter? What model Pi do you have? If end0 is a valid RPi ethernet adapter we can change the Dashboard page to look for it.

[briankkeyser]

systemd.net-naming-scheme (www.freedesktop.org)https://www.freedesktop.org/software/systemd/man/latest/systemd.net-naming-scheme.html

The systemd docs (above) state that all Ethernet interfaces begin with "en" and the rest of the name is assigned by system - hence my end0.

I enabled to use "predictable" interface names in raspi-config network config, but changing that selection back (to don't use predictable names) does not change the interface name back to eth0. So I am stuck with end0 unless I can figure our some way fix it in my linux startup configuration.

Anyone who selects to use predictable interface names in raspi-config is going to have the same issue.

[EricClaeys]

@briankkeyser, see the end of this Discussion for what I hope is a fix.

[EricClaeys]

Closing. Using Issue 3546 instead.