Ubuntu
network-manager package

NetworkManager Should Support MSCHAPv2

Bug #81462 reported by Jonathan Anderson
4
Affects Status Importance Assigned to Milestone
Deluge
Invalid
Undecided
Unassigned
NetworkManager
Fix Released
Wishlist
network-manager (Ubuntu)
Fix Released
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: network-manager

NetworkManager uses wpa_supplicant as a backend, right?

My university (and, by reading blog posts, I'm not alone) uses WPA with MSCHAPv2 for Phase 2 authentication. wpa_supplicant supports this behaviour, but there is no way to configure it with NetworkManager, so after being super-impressed with NM, I'm back to using wpa_supplicant.conf and "sudo ifup eth1". This is really unfortunate, because NetworkManager handles Suspend quite well (it brings the network down before sleeping, so that the driver doesn't get all confused when it wakes up).

Anyway, here's my redacted wpa_supplicant.conf:

network={
        ssid="<ssid>"
        scan_ssid=1
        key_mgmt=WPA-EAP
        eap=PEAP
        identity="<username>"
        password="<password>"
        phase1="include_tls_length=1 peaplabel=0"
        phase2="auth=MSCHAPV2"
}

Can we get NetworkManager to configure the phase2 field?

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Ummm... this doesn't affect Deluge. I'm not sure why Launchpad says it does.

Revision history for this message
Zach Tibbitts (zachtib) wrote : Re: [Bug 81462] Re: NetworkManager Should Support MSCHAPv2

that's odd, i don't know either

On 1/25/07, Jon Anderson <email address hidden> wrote:
>
> Ummm... this doesn't affect Deluge. I'm not sure why Launchpad says it
> does.
>
> ** Bug watch added: GNOME Bug Tracker #400605
> http://bugzilla.gnome.org/show_bug.cgi?id=400605
>
> ** Also affects: deluge (upstream) via
> http://bugzilla.gnome.org/show_bug.cgi?id=400605
> Importance: Unknown
> Status: Unknown
>
> ** Also affects: network-manager (upstream) via
> http://bugzilla.gnome.org/show_bug.cgi?id=400605
> Importance: Unknown
> Status: Unknown
>
> ** Changed in: deluge (upstream)
> Importance: Unknown => Undecided
> Bugwatch: GNOME Bug Tracker #400605 => None
> Status: Unknown => Unconfirmed
>
> --
> NetworkManager Should Support MSCHAPv2
> https://launchpad.net/bugs/81462
>

--
Zach Tibbitts - <email address hidden>
http://collegegeek.org

Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
status: Unknown → Unconfirmed
Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
status: Unconfirmed → Rejected
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Does not affect Deluge.

Changed in deluge:
status: Unconfirmed → Rejected
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

GNOME bug was a dupe. Linking to new (old) bug.

Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
status: Unknown → Unconfirmed
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Please test if you can... I see "'SET_NETWORK 0 eap MSCHAPV2' ... response was 'OK'" in NetworkManager's output, so it seems to be interacting properly with wpa_supplicant. I am, however, having (unrelated) problems with the campus wireless, so I wouldn't call my testing complete.

Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :
Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Jonathan Anderson (jonathan-anderson) wrote :

Forget my earlier patches, they were for EAP, not phase2 within PEAP.

Anyway, there were tarballs posted in the upstream bug... they let me connect (just once, but that could be due to some problems with the campus wireless).

Please test.

Revision history for this message
Basilio Kublik (sourcercito) wrote :

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the package name in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at [WWW] http://wiki.ubuntu.com/BugSquad/ManagingStatus . Thank you again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in network-manager:
assignee: nobody → desktop-bugs
status: New → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
status: Incomplete → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in network-manager:
importance: Unknown → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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