network is a complex thing to configure correctly and involve some files.
First, your wpa_supplicant is very clear about your troubles. Like said wat-now you have a another wpa_supplicant started before the one supervised by 66. So, the one managed by 66 refuse to start as long as you have an already wpa_supplicant daemon running.
To detect it you have several way, i prefer htop. Run it, found the process and kill it and look at the wpa_supplicant service if it start or not.
Now, you need to take care about your /etc/resolv.conf, /etc/hosts, /etc/hostname files.
Personally i use wpa_supplicant with dhclient. I also use the wpa_supplicant@ service with a specific interface. You can follow the Arch wiki about that.
A word about the environnement file. No bug here and expected behavior. The doted one is the original file created when the enable the service. If the frontend file contain a [environment] section, this file is automatically created. Now when you use the 66-env tool, a new environment file is created by a copy of the original one (the doted) with the same name WITHOUT the dot.
Now when you start the service the environment files found at the /etc/66/conf/<service>/<version> directory is read by alphabetical order. That means that for a same key=value pair the last one is picked, so your personnal modification is took.
First, your wpa_supplicant is very clear about your troubles. Like said wat-now you have a another wpa_supplicant started before the one supervised by 66. So, the one managed by 66 refuse to start as long as you have an already wpa_supplicant daemon running.
To detect it you have several way, i prefer htop. Run it, found the process and kill it and look at the wpa_supplicant service if it start or not.
Now, you need to take care about your /etc/resolv.conf, /etc/hosts, /etc/hostname files.
Personally i use wpa_supplicant with dhclient. I also use the wpa_supplicant@ service with a specific interface. You can follow the Arch wiki about that.
A word about the environnement file. No bug here and expected behavior. The doted one is the original file created when the enable the service. If the frontend file contain a [environment] section, this file is automatically created. Now when you use the 66-env tool, a new environment file is created by a copy of the original one (the doted) with the same name WITHOUT the dot.
Now when you start the service the environment files found at the /etc/66/conf/<service>/<version> directory is read by alphabetical order. That means that for a same key=value pair the last one is picked, so your personnal modification is took.