You are not logged in.
Pages: 1
Hey everyone,
I attempted to upgrade to netctl from netcfg and ended up with a bit of a problem. I have installed netctl, removed netcfg (obviously), and even disabled all of the netcfg process I could think of. However, netctl will still not connect to my local WEP protected network. I simply says "Job netctl@wlp3s0-<profile>.service failed. See systemctl status netctl@wlp3s0-<profile> and journalctl -xn for more information." I have inspected both of them and can't figure out what the heck is wrong. I have used wifi-menu to create the profile and netctl enable/start <profile> to attempt to get connected; however, when I attempt to start netctl it throws the aforementioned error.
Here is my journalctl -xn output.
I am working on the systemctl output.
Offline
It would be helpful to see the contents of your netctl profile that's failing, too.
Offline
Ok, have you attempted to manually start the profile; Just reread and you say you did.
# netctl start nameofprofile
Consider using a non-quoted string for your Key= line, i.e;
Key=\"123456789
If there's no joy with this then consider increasing the timeout for dhcp, with;
TimeoutDHCP=30
I understand 10 is the default. Have a good trawl though the man pages for netctl, these are the first places I look with a simple wifi setup.
-- edit below --
Also, a little off-topic - no flippancy intended - if you have control over the access point; consider switching to WPA instead of the broken WEP.
Last edited by opt1mus (2013-04-15 05:55:00)
Offline
Installing wicd is not a fix to the problems you're experiencing with netctl, it's a third-party network manager. It may have been benefit to others, including Jouke, to know what steps you'd taken in attempting to really fix it.
-- edit --
Had you - for example - made sure that wpa_actiond was installed?
Last edited by opt1mus (2013-04-23 09:56:34)
Offline
It's worth inspecting the output of netctl with NETCTL_DEBUG='yes' also. Should give you more information about where exactly the process is failing.
NETCTL_DEBUG='yes' netctl start <profile>
Offline
-- edit --
Had you - for example - made sure that wpa_actiond was installed?
That's a dependency for when using netctl-auto@<interface>.service, but the OP uses "regular" netctl@<profile>.service.
(The netctl wiki article states to install wpa_actiond under the explenation for using encrypted passwords, but that's entirelly unrelated... I'm gonna remove that line from the wiki now, btw...)
@DaBungalow
If you still want to fix your netctl issue, then use a non-quoted key in your profile as op1mus previously suggested.
Last edited by mhertz (2013-04-23 16:54:35)
Offline
netctl works, often, for me. But when it fails I'm at a loss to figure out why. Right now it's failing at a local cafe. I suspect maybe because the wifi uses WEP.
Here's what I see on the console:
[root@archX60 ~]# NETCTL_DEBUG='yes' netctl start wlan0-mercury\ cafe
Job for netctl@wlan0\x2dmercury\x20cafe.service failed. See 'systemctl status netctl@wlan0\x2dmercury\x20cafe.service' and 'journalctl -xn' for details.
[root@archX60 ~]# journalctl -xn
May 06 11:06:43 archX60 network[10857]: Starting network profile 'wlan0-mercury cafe'...
May 06 11:06:43 archX60 kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 06 11:06:59 archX60 network[10857]: WPA association/authentication failed for interface 'wlan0'
May 06 11:06:59 archX60 network[10857]: Failed to bring the network up for profile 'wlan0-mercury cafe'
May 06 11:06:59 archX60 systemd[1]: netctl@wlan0\x2dmercury\x20cafe.service: main process exited, code=exited, status=1/FAILURE
May 06 11:06:59 archX60 systemd[1]: Failed to start Networking for netctl profile wlan0-mercury cafe.
-- Subject: Unit netctl@wlan0\x2dmercury\x20cafe.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit netctl@wlan0\x2dmercury\x20cafe.service has failed.
--
-- The result is failed.
May 06 11:06:59 archX60 systemd[1]: MESSAGE=Unit netctl@wlan0\x2dmercury\x20cafe.service entered failed state.
I don't really understand the "link is not ready" message. Wifi in general works, as I'm now connected to my phone's hotspot in order to post this message.
I think the "WPA association/authentication failed" is the real problem. My phone's hotspot is WPA, but the cafe's router uses WEP according to the file generated by wifi-menu. That file looks like this:
Description='Automatically generated profile by wifi-menu'
Interface=wlan0
Connection=wireless
Security=wep
ESSID=mercury\ cafe
IP=dhcp
Key=1112223333
Offline
I found the solution for my problem in /etc/netctl/examples/wireless-wep. I just needed to prepend \" to the key.
Users of wifi-menu should note the automatically generated file will not work as is for some WEP routers, apparently.
Description='Automatically generated profile by wifi-menu, then modified by Dave'
Interface=wlan0
Connection=wireless
Security=wep
ESSID=mercury\ cafe
IP=dhcp
Key=\"1112223333
Offline
Thank you Dave, your solution worked for me as well. Is this a problem with wifi-menu or netctl?
Offline
Same problem, and opt1mus & Dave's solution worked for me too. The WEP key here is 128-bit, and I'm not sure if that, the router, or netctl is the problem, but perhaps a fix is in order for those of us who have no control over our AP.
Offline
Thank you Dave, your solution worked for me as well. Is this a problem with wifi-menu or netctl?
This is not a problem with anything. You should read the documentation.
Offline
Still wifi-menu should generate a working profile right?
Offline
Apparently not if you are using a hex key; it seems that netctl defaults to assuming a user will not be entering a hex value for the key. I haven't tested it, but I'm thinking that adding \" before a your hex key would create a working profile from wifi-menu.
EDIT: I'm a stickler for grammar...
Last edited by WurdahMekanik (2013-06-14 17:49:13)
Offline
Pages: 1