Hello ! The issue is finding the right app on the archiso. What I do, and is totally scriptable is to use wpa_supplicant plus dhcpd. Both available through the archiso according to head of master [1].
If you know how the configurations information required for your AP, you can follow instruction on the archwiki [2], and I usually go for the manual configuration rather than the interactive process, and usually such configuration ends up being actually pretty basic, like for pure WPA3 [3]. Once the connection has been established, which turns the corresponding interface up for it, you can start the dhcpcd [4] service without initial configuration if having a dhcp server somewhere in your network, otherwise you have to configure the static routes. For later automation, you can enable the wpa_supplicant hook for dhcpcd [5]. Is sounds more complicated than it actually is... And it's been working through ages... That might be an options to consider. A non standard way would be, given you already have an Arch (or your derivative of choice) working on your network you could "cp -a" the ful disk of the working system into the disk of the new box, and modify the usernames and such (you really need to know everything about it), and make the box boot, once booting into the box, then you can modify passwords and such... This might be an option I'd guess, a slow one given the disk copy, though it might reduce time on installing and configuring packages, and so on... Greetings ! -- Javier [1] https://gitlab.archlinux.org/archlinux/archiso/-/blob/master/configs/releng/packages.x86_64 [2] https://wiki.archlinux.org/title/Wpa_supplicant [3] https://wiki.archlinux.org/title/Wpa_supplicant#Connections_to_pure_WPA3-SAE_access_points [4] https://wiki.archlinux.org/title/Dhcpcd [5] https://wiki.archlinux.org/title/Dhcpcd#10-wpa_supplicant
OpenPGP_signature.asc
Description: OpenPGP digital signature
