Bug ID 1057592
Summary Cannot connect to EAP secured wireless network with wicked
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Major
Priority P5 - None
Component Network
Assignee bnc-team-screening@forge.provo.novell.com
Reporter lmb@suse.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

I have trouble connecting my laptop to a PEAP secured wireless network,
embarrassingly the AttachemateGroup one at SUSE HQ.

The network settings seem to be right and match:

BOOTPROTO='dhcp'
BROADCAST=''
DHCLIENT_SET_DEFAULT_ROUTE='yes'
ETHTOOL_OPTIONS=''
IPADDR=''
MTU=''
NAME='Wireless 7260'
NETMASK=''
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='manual'
WIRELESS_AP=''
WIRELESS_AP_SCANMODE='1'
WIRELESS_AUTH_MODE='eap'
WIRELESS_BITRATE='auto'
WIRELESS_CA_CERT=''
WIRELESS_CHANNEL=''
WIRELESS_CLIENT_CERT=''
WIRELESS_CLIENT_KEY=''
WIRELESS_CLIENT_KEY_PASSWORD=''
WIRELESS_DEFAULT_KEY='0'
WIRELESS_EAP_AUTH='MSCHAPV2'
WIRELESS_EAP_MODE='PEAP'
WIRELESS_ESSID='AttachmateGroup'
WIRELESS_FREQUENCY=''
WIRELESS_KEY=''
WIRELESS_KEY_0=''
WIRELESS_KEY_1=''
WIRELESS_KEY_2=''
WIRELESS_KEY_3=''
WIRELESS_KEY_LENGTH='128'
WIRELESS_MODE='Managed'
WIRELESS_NICK=''
WIRELESS_NWID=''
WIRELESS_PEAP_VERSION=''
WIRELESS_POWER='no'
WIRELESS_WPA_ANONID=''
WIRELESS_WPA_IDENTITY='lmb'
WIRELESS_WPA_PASSWORD='xxxxxxxx'
WIRELESS_WPA_PSK=''


Sep 07 13:44:40 hermes kernel: iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Sep 07 13:44:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:f0
Sep 07 13:44:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:f0 (try 1/3)
Sep 07 13:44:43 hermes kernel: wlp3s0: authenticated
Sep 07 13:44:43 hermes kernel: wlp3s0: associate with f0:5c:19:1f:93:f0 (try
1/3)
Sep 07 13:44:43 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:93:f0
(capab=0x1411 status=0 aid=9)
Sep 07 13:44:43 hermes kernel: wlp3s0: associated
Sep 07 13:44:43 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4
lease with UUID 4957ae59-c728-0b00-f205-000033000000
Sep 07 13:44:43 hermes kernel: wlp3s0: Limiting TX power to 23 (23 - 0) dBm as
advertised by f0:5c:19:1f:93:f0
Sep 07 13:44:46 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:93:f0
by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 07 13:44:53 hermes wickedd-dhcp4[1521]: unable to confirm lease
Sep 07 13:44:58 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached
(state INIT)
Sep 07 13:45:00 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:97:f0
Sep 07 13:45:00 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:97:f0 (try 1/3)
Sep 07 13:45:00 hermes kernel: wlp3s0: authenticated
Sep 07 13:45:00 hermes kernel: wlp3s0: associate with f0:5c:19:1f:97:f0 (try
1/3)
Sep 07 13:45:00 hermes kernel: wlp3s0: RX AssocResp from f0:5c:19:1f:97:f0
(capab=0x1411 status=0 aid=13)
Sep 07 13:45:00 hermes kernel: wlp3s0: associated
Sep 07 13:45:00 hermes wickedd-dhcp4[1521]: wlp3s0: Request to acquire DHCPv4
lease with UUID 4957ae59-c728-0b00-f205-000033000000
Sep 07 13:45:00 hermes kernel: wlp3s0: Limiting TX power to 30 (30 - 0) dBm as
advertised by f0:5c:19:1f:97:f0
Sep 07 13:45:03 hermes kernel: wlp3s0: deauthenticating from f0:5c:19:1f:97:f0
by local choice (Reason: 3=DEAUTH_LEAVING)
Sep 07 13:45:10 hermes wickedd-dhcp4[1521]: unable to confirm lease
Sep 07 13:45:15 hermes wickedd-dhcp4[1521]: wlp3s0: defer timeout 15 reached
(state INIT)
Sep 07 13:45:41 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0
Sep 07 13:45:41 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3)
Sep 07 13:45:41 hermes kernel: wlp3s0: f0:5c:19:1f:93:e0 denied authentication
(status 17)
Sep 07 13:45:43 hermes wickedd-nanny[1523]: device wlp3s0: got signal linkDown
Sep 07 13:45:43 hermes kernel: wlp3s0: authenticate with f0:5c:19:1f:93:e0
Sep 07 13:45:43 hermes kernel: wlp3s0: send auth to f0:5c:19:1f:93:e0 (try 1/3)
Sep 07 13:45:43 hermes kernel: wlp3s0: aborting authentication with
f0:5c:19:1f:93:e0 by local choice (Reason: 3=DEAUTH_LEAVING)

So there are a bunch of successful authentication attempts, but then DHCP
doesn't work. Eventually the server throws me out again though.

And no, the password is not incorrect. ;-)


You are receiving this mail because: