[intrepid] network-manager-gnome 0.7 missing PEAP-GTC option

[Fajar A. Nugraha]

Binary package hint: network-manager-gnome

Using Intrepid (beta, up-to-date) on multiple laptops, also is an issue on the release version of Intrepid.

network-manager-gnome 0.7~~svn20081015t194645-0ubuntu1 doesn't have the option to choose GTC for inner authentication when using IEEE8021.x or WPA2 Enterprise. Only MSCHAPv2 and MD5 supported.

This is a regression from Hardy (network-manager-gnome 0.6.6) which supports PEAP-GTC just fine.

[Major (major-redhat-bugs)]

Description of problem:
GTC encapsulation support is unavailable when you choose WPA2 -> PEAP in NetworkManager. Only
MSCHAP/v2 and CHAP are shown, even though GTC is included in wpa_supplicant. The same versions
of NetworkManager on other distributions includes support for GTC.

Version-Release number of selected component (if applicable):
NetworkManager-0.7.0-0.6.7.svn3370.fc8 (Fedora 8)

Steps to Reproduce:
1. Click NetworkManager applet in GNOME
2. Choose a WPA-2 network
3. Choose LEAP
4. GTC is unavailable

Actual results:
GTC does not appear as a selection

Expected results:
GTC should appear as a selection

Additional info:
GTC is already included in wpa_supplicant, but is mysteriously missing in NetworkManager

[Dan (dan-redhat-bugs)]

Some of the infrastructure is not there yet, but support for this should be coming in the future. Not sure how long.

[S. (s.-redhat-bugs)]

Looking at nm-supplicant-settings-verify.c, taken from NetworkManager-0.7.0-0.11.svn4022.fc8.src.rpm, I see:
const char * phase2_allowed[] = {"auth=PAP", "auth=CHAP", "auth=MSCHAP",
                                   "auth=MSCHAPV2", "auth=GTC", "auth=OTP",
                                   "auth=MD5", "auth=TLS", "autheap=MD5",
                                   "autheap=MSCHAPV2", "autheap=OTP",
                                   "autheap=GTC", "autheap=TLS", NULL };
But I'm not seeing GTC as an option for PEAP (nor TTLS). The last discussion regarding GTC support I'm finding on the networkmanager-list archives is from early 2007. Is there more still needed to be done or other configure options needed? Willing to help, unsure where to start.

[Cam Cope (ccope)]

Confirmed, this is a must for many college campus networks.

[Markov Chaney (keno888)]

Confirmed, GTC was an option in NM 0.6, but is now missing. wicd still works with GTC, so the underlying machinery isn't broken, just the NM interface.

[Jeff Rash (jeffrash)]

Same here and it's a must for my office network.

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 8 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 8. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '8'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 8's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 8 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Jeff Rash (jeffrash)]

Here's my version info:

$ aptitude show network-manager | grep Version
Version: 0.7~~svn20081018t105859-0ubuntu2~nm4

$ aptitude show wpasupplicant | grep Version
Version: 0.6.4-2

[m-p{3} (m-p-3)]

I confirm the bug, I cannot connect anymore to the corporate Wifi network from NetworkManager 0.7~~svn20081020t000444-0ubuntu1 (intrepid)

[Bruckj (rpicivil2011)]

I also confirm the bug, I am unable to connect to my universities Wifi network from NetworkManager
0.7~~svn20081018t105859-0ubuntu1 (intrepid)

[Matthew Lye (matthew.lye)]

Confirmed by multiple people.

[Connor Imes (ckimes)]

Setting importance following multiple confirmations.

[Mitch Anderson (metarx)]

I'm having the same issue.

Connecting to an Aruba Networks AP with WPA2-Enterprise.

I authentication against a Windows 2003 Radius Server, with PEAP and MSCHAPv2

The Error I see in the Windows Log file is:

 Authentication-Type = PEAP
 EAP-Type = <undetermined>
 Reason-Code = 66
 Reason = The user attempted to use an authentication method that is not enabled on the matching remote access policy.

When a valid one looks like:

 Proxy-Policy-Name = Use Windows authentication for all users
 Authentication-Provider = Windows
 Authentication-Server = <undetermined>
 Policy-Name = Aruba Wireless
 Authentication-Type = PEAP
 EAP-Type = Secured password (EAP-MSCHAP v2)

It appears as if network-manager isn't passing the type as MSCHAPv2...

This worked fine yesterday before I upgraded to Intrepid.

[Bug (bug-redhat-bugs)]

Fedora 8 changed to end-of-life (EOL) status on 2009-01-07. Fedora 8 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Jeff Rash (jeffrash)]

Is anyone working this issue? I've been months now without being able to access my corporate network.

[Jeff Rash (jeffrash)]

BTW, Mitch...

This bug is only for PEAP and GTC. It has nothing to do with MSCHAPv2.

[aptgetmoo (dezull)]

Hello Jeff.

You can try removing the network-manager and installing the one from hardy.

Works for me.

On 1/24/09, Jeff Rash <email address hidden> wrote:
> BTW, Mitch...
>
> This bug is only for PEAP and GTC. It has nothing to do with MSCHAPv2.
>
> --
> [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option
> https://bugs.launchpad.net/bugs/284211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Dzul Nizam Bin Mahmud Pauzi

[David Orman (ormandj)]

See also:

http://bugzilla.gnome.org/show_bug.cgi?id=565065
https://bugzilla.redhat.com/show_bug.cgi?id=474723

This also affects me, and quite a few others. It still exists in Jaunty, with today's updates:

ii network-manage 0.7-0ubuntu2 network management framework daemon

David

[James (james-redhat-bugs)]

This "Bug" (or lack of a feature) is still present in F10. I think it was available in on older version, but I'm not sure.

related: http://bugzilla.gnome.org/show_bug.cgi?id=565065

[Dan (dan-redhat-bugs)]

*** Bug 474723 has been marked as a duplicate of this bug. ***

[Meawoppl (meawoppl)]

confirmed.

[Rob Adams (readams)]

Is this by any chance fixed in the recent upstream 0.7.1 release?

[David Orman (ormandj)]

It does not appear to be resolved. I just downloaded 0.7.1 and checked:
libnm-util/nm-setting-8021x.c: { "gtc", NULL, NULL }, // FIXME: implement

[Alexander Sack (asac)]

triaged upstream.

[m-p{3} (m-p-3)]

I guess we won't see this fixed in time for 9.04. Another release that we won't be able to use in our corporation.

[aptgetmoo (dezull)]

There is a temporary workaround. You can install the one from Hardy. I tried
and it worked. But the 3G-broadband setup will become harder, since you will
have to do it manually. But if you are just going to use the wifi
connection, there shouldn't be any problem.

On Tue, Apr 21, 2009 at 10:12 PM, m-p{3} <email address hidden> wrote:

> I guess we won't see this fixed in time for 9.04. Another release that
> we won't be able to use in our corporation.
>
> --
> [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option
> https://bugs.launchpad.net/bugs/284211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jeff Rash (jeffrash)]

> aptgetmoo wrote on 2009-04-21: (permalink)
>
>There is a temporary workaround. You can install the one from Hardy. I tried
>and it worked. But the 3G-broadband setup will become harder, since you will
>have to do it manually. But if you are just going to use the wifi
>connection, there shouldn't be any problem.

Can you explain how to do this?

[aptgetmoo (dezull)]

These are the steps for Jaunty.

First go to packages.ubuntu.com,search and download these packages(make sure
you download the hardy ones)
network-manager hold
network-manager-gnome
dhcdbd
gnome-system-tools
libnm-glib0
libnm-util0
Put these files in a folder. Make sure no other *.deb file in this folder

Then kill related processes:
killall nm-applet -9
sudo killall NetworkManager -9
sudo killall NetworkManagerDispatcher -9

then remove some packages:
sudo apt-get remove network-manager network-manager-gnome libnm-glib0
libnm-util1

then go the folder directory where you put all the downloaded packages, run:
sudo dpkg -i *.deb
echo "network-manager hold" | sudo dpkg --set-selections
echo "network-manager-gnome hold" | sudo dpkg --set-selections
echo "dhcdbd hold"| sudo dpkg --set-selections
echo "gnome-system-tools hold"| sudo dpkg --set-selections
echo "libnm-glib0 hold"| sudo dpkg --set-selections
echo "libnm-util0 hold" | sudo dpkg --set-selections
sudo NetworkManager&
nm-applet&

Then you networkmanager should work again with GTC.
If not try restarting your machine. This may not be the best way. In fact,
I tried several times before getting the right packages to remove and
install. There are another application, WICD I think, that can replace
networkmanager. But I'm not sure it will work with GTC.
On Wed, May 6, 2009 at 1:15 AM, Jeff Rash <email address hidden> wrote:

> > aptgetmoo wrote on 2009-04-21: (permalink)
> >
> >There is a temporary workaround. You can install the one from Hardy. I
> tried
> >and it worked. But the 3G-broadband setup will become harder, since you
> will
> >have to do it manually. But if you are just going to use the wifi
> >connection, there shouldn't be any problem.
>
> Can you explain how to do this?
>
> --
> [intrepid] network-manager-gnome 0.7 missing PEAP-GTC option
> https://bugs.launchpad.net/bugs/284211
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Jeff Rash (jeffrash)]

I now have to have GTC for my wired network at work. I have downgraded to 0.6.6 and GTC is working on the wired network, however I'm still having issues with the wireless.

This bug is now 8 months old. Is anyone working on the problem?

[m-p{3} (m-p-3)]

I guess we won't see a fix in time for Karmic Koala. Too bad we cannot implement it on some laptops at the office just because of this. I've tried an older version of Network-Manager, but GTC doesn't work properly over a wireless connection.

[Dan (dan-redhat-bugs)]

Fixed upstream in :

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm master)
272cf183c7963dfaf019b2f5afc816c0bd2dfd73 (applet master)

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm 0.7)
0461fff8039ce612fb5a50ce760b782f62457d59 (applet 0.7)

[Dan Williams (dcbw)]

Fixed upstream in :

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm master)
272cf183c7963dfaf019b2f5afc816c0bd2dfd73 (applet master)

272c6a626a27f4d3a88a1aedd7887d63f6a818d5 (nm 0.7)
0461fff8039ce612fb5a50ce760b782f62457d59 (applet 0.7)

[m-p{3} (m-p-3)]

I gotta try that tomorrow when I get at the office. Thanks!

[Sunirb (sunirbmag)]

How can I try it?

[Markov Chaney (keno888)]

Thanks, Dan. Working now in Jaunty using the NM PPA here:
https://launchpad.net/~network-manager/+archive/ppa
Instructions for installing on that page, PEter.

[Jonathan Thomas (echidnaman)]

The fix has been released to Ubuntu: https://lists.ubuntu.com/archives/karmic-changes/2009-August/005571.html

The KDE frontend doesn't offer the option yet, however. (bug 417667)

[Ravikiran (ravikiran-redhat-bugs)]

Is there any chance we can get an update for F-11? If not, would it be possible to rebuild the current 20090708 rpm after updating the sources to the 0.7 branch head (on both nm and applet), i.e., is the source on the 0.7 branch similar enough that the current spec file will work?

[Dan (dan-redhat-bugs)]

Yeah, we'll get an update for F10 and F11 soon here.

[Dan (dan-redhat-bugs)]

Fix has actually been in updates-testing for a bit...

F11 update:

https://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696

F10 update:

https://admin.fedoraproject.org/updates/F10/FEDORA-2009-10546

[Fedora (fedora-redhat-bugs)]

NetworkManager-0.7.1.998-1.fc11, mobile-broadband-provider-info-1.20090918-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with
 su -c 'yum --enablerepo=updates-testing update NetworkManager mobile-broadband-provider-info'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-10696

[Bug (bug-redhat-bugs)]

This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

[Fedora (fedora-redhat-bugs)]

mobile-broadband-provider-info-1.20090918-1.fc11, NetworkManager-0.7.2-1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.

[Bug (bug-redhat-bugs)]

Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.