On Wed, Feb 18, 2015 at 9:45 PM, Adam Carter <adamcart...@gmail.com> wrote:
>>
>> If it's a static network (meaning, the computer does not usually moves
physically), why don't you use a .network unit file (man 5 systemd.network)?
>>
>>
>> I'm converting my configs over to that now. Thanks.
>
>
> Another question - i have a wired interface that's always on, and
wireless interface that doesnt start at boot and it not always running. I
used to just run the openrc init script to start and stop it, since openrc
used per interface scripts. With systemd the wired interface is fine using
/etc/systemd/network/<interface>.network, but AFAIK I wont be able to use a
*.network file for the wireless interface because then its status will be
tied to the wired interface.
>
> What's the standard systemd way for me to control the wireless interface?

There isn't one. networkd is only for really simple networks, and wireless
networks are not considered as such.

You can use wpa_supplicant.service, or wpa_supplicant@<interface>.service,
or just go to a full fledged network management program like wicd,
NetworkManager, or several others.

I use networkd in all my wired machines. For  wireless machines, I use
NetworkManager.

I believe you can use wpa_supplicant to handle all your wireless (and even
wired) needs. Check out "man 5 wpa_supplicant.conf", and then just enable
and start wpa_supplicant@<interface>.service.

Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México

Reply via email to