ok...it's back to connecting to the wrong wifi at boot agian

glenny1: I have no idea if this is your problem, but I once had a similar-sounding issue caused by the default wpa_supplicant.conf containing a rule to connect to unsecured networks

wpa_supplicant should be properly configured

I see. Best of luck, then

i don't know what's happening. it's like it's not even reading wpa_supplicant.conf

when you don't know what's happening you're in a bad place, and should turn to logs or tools that could help you understand what's going on under the hood

if i have a bastille jail running a postgresdb, is it "safe" to bastille clone the jail using zfs ?

now dhcp just loops and the system refuses to boot. i'm in single user mode hoping to edit rc.conf but it won't let me

i'm just going to reinstall and try again. i have no idea why things are so broken

reinstall fixed whatever happened

*something* is making the EFI-lua loader on a certain system set "boot_serial" to "YES" (according to the "show" command at the loader prompt when booting) and I can't figure out why. I've combed through the /boot config files and I don't see what could be setting it.