[SOLVED] netctl troubleshooting

Niourf · 2014-03-18 18:25:22

Hi guys,

I am trying to connect to my University wifi network (eduroam) with netctl, and I am having trouble understanding what the problem is.

When I try to connect, I get the following error message:

~ » sudo netctl start eduroamBristol                                                                                                     
Job for netctl@eduroamBristol.service failed. See 'systemctl status netctl@eduroamBristol.service' and 'journalctl -xn' for details.

Here are the results of the two suggested commands:

~ » systemctl status netctl@eduroamBristol.service
netctl@eduroamBristol.service - Networking for netctl profile eduroamBristol
   Loaded: loaded (/usr/lib/systemd/system/netctl@.service; static)
   Active: failed (Result: exit-code) since mar. 2014-03-18 18:11:37 CET; 18s ago
     Docs: man:netctl.profile(5)
  Process: 2293 ExecStart=/usr/lib/network/network start %I (code=exited, status=1/FAILURE)
 Main PID: 2293 (code=exited, status=1/FAILURE)

~ » journalctl -xn
-- Logs begin at sam. 2013-06-08 16:22:44 CEST, end at mar. 2014-03-18 18:09:37 CET. --
mars 18 18:09:37 cotier systemd[1710]: Reached target Paths.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
mars 18 18:09:37 cotier systemd[1710]: Starting Timers.
-- Subject: L'unité (unit) UNIT a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a commencé à démarrer.
mars 18 18:09:37 cotier systemd[1710]: Reached target Timers.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
mars 18 18:09:37 cotier systemd[1710]: Starting Sockets.
-- Subject: L'unité (unit) UNIT a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a commencé à démarrer.
mars 18 18:09:37 cotier systemd[1710]: Reached target Sockets.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
mars 18 18:09:37 cotier systemd[1710]: Starting Basic System.
-- Subject: L'unité (unit) UNIT a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a commencé à démarrer.
mars 18 18:09:37 cotier systemd[1710]: Reached target Basic System.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
mars 18 18:09:37 cotier systemd[1710]: Starting Default.
-- Subject: L'unité (unit) UNIT a commencé à démarrer
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a commencé à démarrer.
mars 18 18:09:37 cotier systemd[1710]: Reached target Default.
-- Subject: L'unité (unit) UNIT a terminé son démarrage
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- L'unité (unit) UNIT a terminé son démarrage, avec le résultat done.
mars 18 18:09:37 cotier systemd[1710]: Startup finished in 107ms.
-- Subject: Le démarrage du système est terminé
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Tous les services nécessaires au démarrage du système ont été lancés avec
-- succès. Notez que cela ne signifie pas que le système est maintenant au
-- repos, car des services peuvent encore être en train de terminer leur
-- démarrage.
-- 
-- Le chargement du noyau a nécessité KERNEL_USEC microsecondes.
-- 
-- Le chargement du « RAM disk » initial a nécessité INITRD_USEC microsecondes.
-- 
-- Le chargement de l'espace utilisateur a nécessité 107503 microsecondes.
------------------------------------------------------------

All the french stuff is irrelevant to the issue. If anyone has any tip of how to troubleshot this I would be very grateful.

Just in case, here are the config files for netctl and wpa_supplicant. The wpa_supplicant one is provided by my university so I guess it's correct

~ » cat /etc/netctl/eduroamBristol                                                                                                         nico@cotier
Description='Eduroam university'
Interface=wlan0 
Connection=wireless
Security=wpa-configs
IP=dhcp
ESSID=eduroam
WPAConfigFile="/home/nico/.wifi/eduroamBristol.conf"
------------------------------------------------------------

~/.wifi » cat eduroamBristol.conf                                                                                                          nico@cotier
network={
  # --- MUST CONFIGURE THE FOLLOWING THREE OPTIONS --

  # The 'identity' is the username actually used for authentication.
  # This must be your Bristol username, all lowercase.
        identity="myId"

  # Your normal Bristol password (so make sure the permissions on
  # your wpa_supplicant config file are not world readable!)
        password="myPassword"

  # CA cert from here:
  # https://www.wireless.bris.ac.uk/certs/eaproot/uob-net-ca.crt
  # Change the path to where you downloaded the file
        ca_cert="/home/nico/.wifi/uob-net-ca.crt"

  # --- ONLY CHANGE BELOW IF YOU ARE NOT A MEMBER --
  # --- OF THE UNIVERSITY OF BRISTOL, UK          --

  # Bristol supports PEAP and TTLS.
        eap=PEAP TTLS

  # The 'anonymous_identity' is the identity used for routing
  # the authentication to Bristol. It must end with '@bris.ac.uk'
  # or '@bristol.ac.uk'. It must be all lowercase. If you have 
  # anything preceding the @ it must be all lowercase letters or 
  # a hyphen (no spaces, punctuation etc) 
  # e.g. "wireless-user@bristol.ac.uk" would be ok
        anonymous_identity="@bristol.ac.uk"

  # Bristol use MS-CHAPv2 as the inner authentication scheme,
  # with the traditional label
  phase1="peaplabel=0"
  phase2="auth=MSCHAPV2"

  # Set priority to a big number
  priority=999

  # --- DONT CHANGE THE REST OF THIS BLOCK --

  # Enable this network block
  disabled=0

  # eduroam please
        ssid="eduroam"

  # SSID should be broadcast, so don't scan.
  scan_ssid=0

  # Infrastructure mode
  mode=0

  # WPA/WPA2 require OPEN
  auth_alg=OPEN

  # WPA and WPA2 (RSN) are both used for eduroam 
  # (depending on which organisation you are at)
  # In the future 'WPA' can be removed (WPA2 only).
  proto=WPA RSN

  # CCMP (AES) is stronger, but some organisations use TKIP.
  # In the future 'TKIP' can be removed.
  pairwise=CCMP TKIP

  # Use EAP
        key_mgmt=WPA-EAP

  # Use PMKSA caching
        proactive_key_caching=1

}

Thanks a lot!

Last edited by Niourf (2014-03-19 10:11:00)

orschiro · 2014-03-18 20:20:05

Have you tried: https://aur.archlinux.org/packages/netctl-eduroam/

progandy · 2014-03-18 21:40:03

Please post the output of "sudo journalctl -xn". Some messages are only shown if you are root or int the group "systemd-journal".
As to your profile:
- Does wlan0 exist or is it something else? Check with "ip link"
- There is an "s" too much in the Security line. "wpa-configs" It must be "wpa-config" for WPAConfigFile, or if you want to use WPAConfigSection "wpa-configsection"
- Maybe put your certificate and your wpa config in /etc instead of your home directory.

Last edited by progandy (2014-03-18 21:42:05)

Niourf · 2014-03-19 10:10:04

Hi guys, thanks a lot for your help.
I used the eduroam example file from the netctl-eduroam package.
I had to change the wpa_supplicant "phase2" option though : PAP would not work, I had to use MSCHAPV2.
Also put the certificate in /etc as suggested, I don't know if it would have worked fine as well if I had left it in my home directory.

I did not know I had to be root for journalctl -xn, thanks a lot it helped me to debug the rest.

Here is my working netctl config file :

Connection='wireless'
Interface=wlan0
Security='wpa-configsection'
Description="eduroam network"
IP='dhcp'
TimeoutWPA=30
WPAConfigSection=(
    'ssid="eduroam"'
    'key_mgmt=WPA-EAP'
    'eap=TTLS'
    'proto=WPA2'
    'phase2="auth=MSCHAPV2"'
    'anonymous_identity="@bristol.ac.uk"'
    'identity="id"'
    'ca_cert="/etc/ssl/certs/uob-net-ca.crt"'
    'password="password"'
)

Thanks again!
Bye

Arch Linux

#1 2014-03-18 18:25:22

[SOLVED] netctl troubleshooting

#2 2014-03-18 20:20:05

Re: [SOLVED] netctl troubleshooting

#3 2014-03-18 21:40:03

Re: [SOLVED] netctl troubleshooting

#4 2014-03-19 10:10:04

Re: [SOLVED] netctl troubleshooting

Board footer