I want to ask about netctl-auto and wifi-menu.
netctl-auto works fine - it connects to one of generated profiles automatically at startup without problems. But when I'm somewhere else, where aren't any known APs, netctl-auto is useless. So usually I try to connect to other AP by using wifi-menu command. But when I try to connect to other AP using wifi-menu, i get an error: "Interface 'wlp1s0' is controlled by netctl-auto.
So I have to disable netctl-auto using "systemctl stop email@example.com", which also automatically run command "rfkill block wlan". I have to turn on using "rfkill unblock wlan" and then I can use "wifi-menu". It looks to me really complicated and I don't understand, why netctl-auto has so high priority. Even when you want to change profile when is netctl-auto on, you have to do same stupidity, because otherwise it says:
Job for netctl@<interface><profile>.service failed. See 'systemctl status netctl@<interface><profile>.service' and 'journalctl -xn' for details
There is no known way for me to change it directly using something simple like "netctl start <profile>" when is netctl-auto on.
I guess there should be some better way. Does any one know?
I experience the same inconveniences. As soon as I find the time and the motivation I'll check out wicd.
Unfrotunately WICD is getting old. Main developer wrote at lunchpad that he "is lacking manpower". Is there suggestion list for netctl?
Or maybe it is complicated on purpose and I'm blind to it. Maybe someone knows why.
File a bug report.
Allan-Volunteer on the (topic being discussed) mailn lists. You never get the people who matters attention on the forums.
jasonwryan-Installing Arch is a measure of your literacy. Maintaining Arch is a measure of your diligence. Contributing to Arch is a measure of your competence.
Griemak-Bleeding edge, not bleeding flat. Edge denotes falls will occur from time to time. Bring your own parachute.