Note: sudo netctl stop or start a profile works correct.
Here is the profile file of the netctl:
Description='A simple WPA encrypted wireless connection'
Interface=wlan0
Connection=wireless
Security=wpa
IP=dhcp
ESSID='myrouter'
# Prepend hexadecimal keys with \"
# If your key starts with ", write it as '""<key>"'
# See also: the section on special quoting rules in netctl.profile(5)
Key='232psdfsf9'
# Uncomment this if your ssid is hidden
#Hidden=yes
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:12:cc:33:2f:5e brd ff:ff:ff:ff:ff:ff
$ sudo wifi-menu
Invalid interface specification
Usage: wifi-menu [-h | --help] [-o | --obscure] [INTERFACE]
Interactively connect to a wireless network on INTERFACE using netctl.
If only one wireless interface is available, INTERFACE can be omitted.
Arguments:
-h, --help Show this help
-o, --obscure Show asterisks for the characters of the password
and store the password as a hexadecimal string
$ journalctl -xn
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 14:18:30 EES
May 15 14:16:04 rootuser network[701]: The interface of network profile 'profile
May 15 14:16:11 rootuser sudo[707]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session opened for u
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session closed for u
May 15 14:17:00 rootuser sudo[719]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:17:00 rootuser sudo[719]: pam_unix(sudo:session): session opened for u
May 15 14:17:42 rootuser sudo[719]: pam_unix(sudo:session): session closed for u
May 15 14:18:30 rootuser sudo[729]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session opened for u
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session closed for u
lines 1-11/11 (END)...skipping...
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 14:18:30 EEST. --
May 15 14:16:04 rootuser network[701]: The interface of network profile 'profile' is already up
May 15 14:16:11 rootuser sudo[707]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:16:11 rootuser sudo[707]: pam_unix(sudo:session): session closed for user root
May 15 14:17:00 rootuser sudo[719]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:17:00 rootuser sudo[719]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:17:42 rootuser sudo[719]: pam_unix(sudo:session): session closed for user root
May 15 14:18:30 rootuser sudo[729]: cypro : TTY=pts/0 ; PWD=/home/cypro ; USER=root ; COMMAND=/usr
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session opened for user root by cypro(u
May 15 14:18:30 rootuser sudo[729]: pam_unix(sudo:session): session closed for user root
$ systemctl status -l netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: inactive (dead)
Docs: man:netctl.profile(5)
May 15 14:15:55 rootuser systemd[1]: Stopped Networking for netctl profile profile1.
Now I dont know if this a problem, I have two profiles the
profile
and the
profile1
I don't think that I have never link the profiles with the netctl, but when I am stop or start a profile all looks perfect.
]]>Once you undo the problem that was created with that new udev rule, make sure your profile has interface=XXXXXX where the X's are the actual interface name given by `ip a` (it will be wlp2s0, unless you opt for the sybolic link to /dev/null which I'd discourage at this point - in that case it would be wlan0).
At that point we'll have gone back to where we were at post 18 of this thread at which point you should have answered ewaller's question. The result there was almost certainly *not* the same. The end product of "not working" may have been the same, but the error message almost certainly would be different. We'd need to know what that error message was in order to continue working on the problem.
]]>Please realize that troubleshooting will often have multiple steps - each one building on the last. We are not trying random things hoping one will work. So the progress we had already made was important ... we need to keep your interface name and profile settings matching and then work on the next step.
]]>$ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp1s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
link/ether 00:21:cc:55:f2:5e brd ff:ff:ff:ff:ff:ff
$ sudo netctl start profile1
Job for netctl@profile1.service failed. See 'systemctl status netctl@profile1.service' and 'journalctl -xn' for details.
$ systemctl status -l netctl@profile1.service
netctl@profile1.service - Networking for netctl profile profile1
Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
Active: failed (Result: exit-code) since Thu 2014-05-15 02:32:15 EEST; 1min 26s ago
Docs: man:netctl.profile(5)
Process: 680 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
Main PID: 680 (code=exited, status=1/FAILURE)
May 15 02:32:15 router network[680]: Starting network profile 'profile1'...
May 15 02:32:15 router network[680]: Interface 'wlan0' does not exist
May 15 02:32:15 router network[680]: Failed to bring the network up for profile 'profile1'
May 15 02:32:15 router systemd[1]: netctl@profile1.service: main process exited, code=exited, status=1/FAILURE
May 15 02:32:15 router systemd[1]: Failed to start Networking for netctl profile profile1.
May 15 02:32:15 router systemd[1]: Unit netctl@profile1.service entered failed state.
$ sudo wifi-menu
Invalid interface specification
Usage: wifi-menu [-h | --help] [-o | --obscure] [INTERFACE]
Interactively connect to a wireless network on INTERFACE using netctl.
If only one wireless interface is available, INTERFACE can be omitted.
Arguments:
-h, --help Show this help
-o, --obscure Show asterisks for the characters of the password
and store the password as a hexadecimal string
$ journalctl -xn
-- Logs begin at Tue 2014-01-28 02:18:46 EET, end at Thu 2014-05-15 02:34:20 EEST. --
May 15 02:32:15 router network[680]: Starting network profile 'profile1'...
May 15 02:32:15 router network[680]: Interface 'wlan0' does not exist
May 15 02:32:15 router network[680]: Failed to bring the network up for profile 'profile1'
May 15 02:32:15 router systemd[1]: netctl@profile1.service: main process exited, code=exited, stat
May 15 02:32:15 router systemd[1]: Failed to start Networking for netctl profile profile1.
-- Subject: Unit netctl@profile1.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit netctl@profile1.service has failed.
--
-- The result is failed.
May 15 02:32:15 router systemd[1]: Unit netctl@profile1.service entered failed state.
May 15 02:32:15 router sudo[674]: pam_unix(sudo:session): session closed for user root
May 15 02:34:20 router sudo[692]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr
May 15 02:34:20 router sudo[692]: pam_unix(sudo:session): session opened for user root by user(u
May 15 02:34:20 router sudo[692]: pam_unix(sudo:session): session closed for user root
First was the interface name problem - that is fixed. Next was the fact that another service was already running - that should now be fixed. Now there is a new problem, but we can't guess what it is until we see the error message output from the systemctl status output for that service.
]]> Invalid interface specification
And for the netctl command the message steel the same.
]]>you are probably running into the devices getting renamed upon each reboot. you probably need to create a file /udev/rules.d/10-network.rules with the following:
SUBSYSTEM=="net", ATTR{address}=="<your wifi MAC address>", NAME="wlan0"
then make sure the "Interface" line in the netctl profile says:
Interface=wlan0