Wireless will not authenticate with MSChapV2

Bug #291975 reported by J. Thomas Shaw
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

With Ubuntu 8.10 final release up to date, I was having issues with wireless authentication.
I am using the Broadcom restricted driver, connecting using WPA, WPA2 Enterprise with PEAP and MSChapV2.
MSChapV2 information is not being passed on when authenticating, and on Monday I should be able to obtain logs to show this compared to working authentications. This was not an issue with 8.04, and I have talked to several people who have confirmed this wireless issue.

'02:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)'

Tags: regression
Revision history for this message
Evan (ev) wrote :

Please attach /var/log/syslog after attempting to connect.

Thanks

Revision history for this message
Alexander Sack (asac) wrote :

sounds similar to bug 272185 ... though thats iwl chipset. please test the packages i posted there.

Changed in network-manager:
status: New → Incomplete
Revision history for this message
J. Thomas Shaw (v-admin-jtsnetworks-net) wrote :

Totally forgot about this, found a workaround by using a different wireless network here on campus (registered my mac address for the pda specific network that is just mac filtered).

Revision history for this message
ProfessorKaos64 (mdeguzis) wrote :

Yes, I was quite content using 8.04 LTS, but ill have to see about registering my MAC

Revision history for this message
Descention (descention) wrote :

booted, attempted connection to wildcats ( the wpa/peap network ), failed, then connected to pda (unsecured/open), success.

Revision history for this message
Descention (descention) wrote :

For that previous syslog, that was after using the package recommended by Alexander Sack.

Revision history for this message
Descention (descention) wrote :

I have installed Jaunty Alpha 5 onto a flash drive, booted as a live CD, and successfully connected to the wpa/peap network called "wildcats" without any issue. The form to fill out upon attempting to connect was filled in as such:

Authentication: Protected EAP
Anonymous Identity: *do not put anything in*
User Name: <email address hidden>
Password: *network password*

does not require a CA Certificate.

Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.