[SOLVED] WPA2-Enterprise connection problems

darlac · 2017-11-14 18:38:42

Hi all,
I use network manager to control my network connections. I works fine for ethernet and regular wifi connections. At my work a new WPA2-Enterprise authentication mechanism has been adopted - I cannot connect to that wireless system. A linux script is provided (https://cloud.securew2.com/public/09325 … ss_Secure/), that runs fine in my system but fails to configure the wireless network (it works fine in mint and opensuse systems).
I tried to manually set the wireless network (details here: https://ruwireless.rutgers.edu/ruwirele … nual-setup), the set up is saved but cannot connect to wireless network (it seems to get stuck at CA certificate validation step).
I believe the wpa enterprise is not operating fine under network manager - I read about wpa_supplicant, but my understanding is that it is separate from the network manager.
Is there a way I could use network manager with wpa enterprise wifi network?

Last edited by darlac (2017-11-17 15:16:17)

lo1 · 2017-11-15 14:24:25

The links you're providing point to void pages (the first one works, but don't think anyone here would like to "join" whatever that is to read a script and help you).
Post any relevant configuration, network profiles and script (inside code tags), then we can help you.
Regarding wpa_supplicant: you got it right, wpa_supplicant is another story, so before trying that be sure you disable any network manager to avoid conflict.

darlac · 2017-11-15 22:32:01

Hi lo1, thanks for pointing out the void link - I fixed the 2nd which has the detailed information for setting the connection.
For some reason the CA certificate provided from my university does not register in my system - I cannot seem to figure out the problem
here are the results for my network status -

systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
           └─NetworkManager-ovs.conf
   Active: active (running) since Wed 2017-11-15 17:11:04 EST; 11min ago
     Docs: man:NetworkManager(8)
 Main PID: 459 (NetworkManager)
    Tasks: 3 (limit: 4915)
   CGroup: /system.slice/NetworkManager.service
           └─459 /usr/bin/NetworkManager --no-daemon

Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2017] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2027] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2032] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2034] manager: NetworkManager state is now CONNECTED_LOCAL
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2089] manager: NetworkManager state is now CONNECTED_SITE
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2091] policy: set 'Auto DEES_Main_Office' (wlp2s0) as default for IPv4 routing and DNS
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2092] dns-mgr: Writing DNS information to /usr/bin/resolvconf
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2435] device (wlp2s0): Activation: successful, device activated.
Nov 15 17:11:11 dimitris NetworkManager[459]: <info>  [1510783871.2441] manager: startup complete
Nov 15 17:11:12 dimitris NetworkManager[459]: <info>  [1510783872.4641] manager: NetworkManager state is now CONNECTED_GLOBAL

and

 journalctl -u NetworkManager -b
-- Logs begin at Thu 2017-04-20 22:23:14 EDT, end at Wed 2017-11-15 17:26:04 EST. --
Nov 15 17:11:04 dimitris systemd[1]: Starting Network Manager...
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.2911] NetworkManager (version 1.10.0-1, Arch Linux) is starting... (for the first time)
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.2912] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.3135] manager[0x55e2200b9040]: monitoring kernel firmware directory '/usr/lib/firmware'.
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4531] hostname: hostname: using hostnamed
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4531] hostname: hostname changed from (none) to "dimitris"
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4533] dns-mgr[0x55e2200d4840]: init: dns=default, rc-manager=resolvconf
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4538] rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0/ieee80211/phy0/rfkill1) (driver iwlwifi)
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4538] manager[0x55e2200b9040]: rfkill: WiFi hardware radio set enabled
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4538] manager[0x55e2200b9040]: rfkill: WWAN hardware radio set enabled
Nov 15 17:11:04 dimitris systemd[1]: Started Network Manager.
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4762] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4771] settings: loaded plugin iBFT: (c) 2014 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list. (/usr/lib/NetworkManager/l
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.4918] keyfile: new connection /etc/NetworkManager/system-connections/eduroam (df54e285-26f8-43a8-a238-4151a00810a1,"eduroam")
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.5046] keyfile: new connection /etc/NetworkManager/system-connections/Auto RUWireless (a2b52a65-90fd-48e6-a351-0f8f78dab875,"Auto RUWireless")
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.6750] keyfile: new connection /etc/NetworkManager/system-connections/Rutgers (c323a3c1-3024-40be-98d1-1978bec6cfff,"Rutgers")
Nov 15 17:11:04 dimitris NetworkManager[459]: <info>  [1510783864.6823] keyfile: new connection /etc/NetworkManager/system-connections/Auto DEES_Main_Office (1886900a-4fb0-4ce4-add9-aa08f4dd02ce,"Auto DEES_Main_
.....

in the above RUwireless_secure does not appear, although I have set it up, both manually and through the script...
RUwireless is the non wpa version, that allows you to download the script, and then log in to the secure one...

hope this post has more information

lo1 · 2017-11-16 11:45:49

This does bring more info, but given that the script is provided from your university there's very little we can do.
After you're connected to RUWireless, have a look at

cat /etc/resolv.conf
cat /etc/resolvconf.conf
ip route
ip address

Also, from the wiki:

NetworkManager can generate WPA2 Enterprise profiles with graphical front ends. nmcli and nmtui do not support this, but may use existing profiles.

darlac · 2017-11-17 15:16:01

Hi Io1, thanks again - i read the wiki multiple times, and the links therein but could not resolve the settings;
I finally managed to connect through netctl (following this link https://bbs.archlinux.org/viewtopic.php?id=162341; then I transferred the netctl settings to network manager and it worked!
so now I can connect normally!
thanks for the support

Arch Linux

#1 2017-11-14 18:38:42

[SOLVED] WPA2-Enterprise connection problems

#2 2017-11-15 14:24:25

Re: [SOLVED] WPA2-Enterprise connection problems

#3 2017-11-15 22:32:01

Re: [SOLVED] WPA2-Enterprise connection problems

#4 2017-11-16 11:45:49

Re: [SOLVED] WPA2-Enterprise connection problems

#5 2017-11-17 15:16:01

Re: [SOLVED] WPA2-Enterprise connection problems

Board footer