Mailinglist Archive: opensuse-bugs (8956 mails)

< Previous Next >
[Bug 216063] New: Knetworkmanager exhaust allowed time (60s) for wireless connection
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 28 Oct 2006 06:15:50 -0600 (MDT)
  • Message-id: <bug-216063-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=216063

Summary: Knetworkmanager exhaust allowed time (60s) for wireless
connection
Product: SUSE Linux 10.1
Version: Final
Platform: i686
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Network
AssignedTo: bnc-team-screening@xxxxxxxxxxxxxxxxxxxxxx
ReportedBy: guillermo.gomez@xxxxxx
QAContact: qa@xxxxxxx


I can connect to my institution AP's by manually invoking the wpa_supplicant
with a wpa_supplicant.conf file from my institution.
I can NOT connect using KnetworkManager directly (supplying the necessary info
in the corresponding pop-up windows). Diving into log files, I see that the
wpa_supplicant is invoked as manually (except for the conf file) and starts an
endless tour of negotiation with accesible AP's till it exhausts its time).
I can feed into Knetworkmanager almost all info the config file has, as far as
acronyms are concerned(I am not expert): WPA-EAP, TTLS, WPA1. The conf file
entries I do not find pop-up options for them are:
phase2="auth=PAP",ap_scan=1,fast_reauth=1,priority=6.

I do not know if this is a bug or just a lengthy negotiation. In any case:
Would it be possible to force Knetwormanager to use my conf file? or
Would it be possible to fill the (missing? )info in the knetworkmanagerrc
file?.

My (working) conf file is:

# WPA conffiguration
ctrl_interface=/var/run/wpa_supplicant
#ctrol_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1

network={
ssid="myssid"
key_mgmt=WPA-EAP
proto=WPA
eap=TTLS
anonymous_identity="anonymousidentity"
identity="myidentity"
password="mypasswrd"
priority=6
phase2="auth=PAP"
}


Thanks a lot


--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

< Previous Next >
This Thread
  • No further messages