headless server internet connection error

[CleetWiggz]

-Tried script on Ryzen 5000 series mini PC and OrangePi 5 Plus, multiple OSes, multiple known good wifi adapters and ethernet, multiple APs

-Script hangs when looking for an internet connection with a warning about pip and that the installer might fail if you continue while the computer has a confirmed solid connection.

-Everything will install fine when ignoring the error.

-ragnar service runs after reboot

-web app never goes live/port 8000 stays closed

-ssh works fine

-ragnar maybe looking in the wrong place because not raspberry device

-likely i'm probably just being dumb

[PierreGode]

Yeah, Ragnar development han being focused to tun on Raspberry pi, but i know it runs on laptops.
It is focused to use wlan0 wlan1 and eth0.

This is good i will take a look to make Ragnar more flexible outside its sphere

I have other issues that are more urgent to be resolved so it might take a week or 2 before I can pick this up.

[CleetWiggz]

No worries!

I just wish I could be more helpful, but I know very little about code.

If I end up playing around with it again before then, I'll at least post anything else that seems helpful or important up here.

Thanks!

[CleetWiggz]

Okie

I got it working on a ryzen mini pc.

-created a file named 10-wlan.link (keep the 10- part) in /etc/systemd/network/

-in the file:

[Match]
MACAddress=AA:BB:CC:DD:EE:FF
[Link]
Name=wlan0

Haven't tried with anything else, but I imagine this should work as a workaround with most things. It still hangs with the same error, but worked on the first try after ignoring it.

[PierreGode]

Thank you, this is gold. I Will investigate if i can make Ragnar to automate this.

[CleetWiggz]

this is going to change the interface name entirely, which i guess is fine if the user knows. i'll see if can find anything about a symbolic link to act more as an alias than a replacement

[CleetWiggz]

I guess, if I understand correctly, the naming convention changed to avoid wlan0 and wlan1 from switching because they'd be arbitrarily assigned at boot. Instead of just assigning wlan0, wlan1, etc to a specific adapter for each, they get assigned unique names.

This won't flip flop because we assign it to a specific mac. I also didn't notice any issues with light use on that machine as far as things losing their connection so it might actually be fine.

I actually had to do this on a pi for something else the other day and it also seems fine.

Might be worth exploring.

[PierreGode]

@CleetWiggz will pick this up soon. had other focuses.

[CleetWiggz]

yeah, no worries! i've got plenty of other things going on too as i'm sure all of us have. take your time