** Changed in: network-manager-applet
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445487
Title:
Network-Manager fails WPA2 Enterprise configuration
To m
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: network-manager-applet (Ubuntu Lucid)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bu
karmic has seen the end of its life and is no longer receiving any
updates. Marking the karmic task for this ticket as "Won't Fix".
** Changed in: network-manager-applet (Ubuntu Karmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Changed in: network-manager-applet
Status: Unknown => In Progress
** Changed in: network-manager-applet
Importance: Unknown => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/44548
** Bug watch added: GNOME Bug Tracker #719982
https://bugzilla.gnome.org/show_bug.cgi?id=719982
** Changed in: network-manager-applet
Importance: High => Unknown
** Changed in: network-manager-applet
Status: Invalid => Unknown
** Changed in: network-manager-applet
Remote watch: GNO
** Changed in: network-manager-applet
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/445487
Title:
Network-Manager fails WPA2 Enterprise configuration
To manage notific
Anybody still experiencing this bug should file a new report with
specific steps to reproduce. This bug has gotten too confused to be
useful anymore.
** Changed in: network-manager-applet (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
Sorry, my fault. Please ignore my last two postings. The Button remains
grayed out, because I did not enter/select an SSID name. With the name
provided, the button is not grayed out anymore - neither on 10.04, nor
10.10 nor 11.04-alpha3.
Unfortunately I can't test what happens when you click it, b
Here we go. I have just set up a Virtual Machine and booted 11.04-alpha3
inside it. Then I configured a Wireless connection with WPA2-Enterprise
with PEAP/MSCHAPv2. As you can see in the attached screenshot, the apply
button (in 11.04 it is named "save" now) remains grayed out, although
all informa
Unfortunately there are many things that can go wrong when handling the
certificates, security levels, and all of that.
I also don't happen to have a way to reproduce the required environment,
so no possibility for me to easily reproduce and work on a fix. What
*would* be helpful though would be i
Can we do something to get the QA-Teams attention on this bug, so it
will get finally fixed in 11.04?
I just tried to reproduce this bug with the instructions given above
both on a fully updated 10.04 and 10.10 and it failed in BOTH
environments, with the described symptom: The "apply" button rema
Is this bug still active or has it been relegated to the trash bin?
I've been living with this issue for months now. Can anyone confirm
that this has been fixed in the 10.10? As previously posted, this is
only relevant to PEAP/MSCHAPv2 networks, unfortunately I spent a
majority of my day in that
I have had this same problem on our corporate network (PEAP/MSCHAPv2)
for so long now, I almost don't notice the smirks and eyerolls when I
have to scrounge for a wired connection in a conference room.
Is there a way to use something akin to the p12 workaround in the
PEAP/MSCHAPv2 (login/password)
Did some more tests with a new p12 certificate and it works!
The only thing that I can tell now is that you have to fill in all
fields in the settings dialogue (also the ID).
So far I only can tell sorry for my previous entry, should have done
more testing before posting.
My configuration:
Ubun
For me right now it's working more or less, but when you have lots of
networks with the same name close each other, the connection jumps from
one to another disconnecting you all the time.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received t
http://www.eduroam.org/ - note there isn't one single eduroam configuration --
I've seen setups using EAP/TLS (certificates), and I've seen setups using
PEAP/MSCHAPv2 (with login/password).
Side remark, considering how long such bugs have been open (and even Fedora 14
at point of this writing sti
Schlomo, does it work however if you use the previously discussed
workaround of repackaging the certificates?
What's the difference between the certificates? Is eduroam using
somespecial method to issue certificates?
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.n
We also have this issue with our corporate network (both lucid and
maverick). It really is a showstopper because Ubuntu users cannot use
their laptops without a network cable. This actually prevented several
people from migrating their Windows laptop to Ubuntu because they use
their laptop 80% in c
I can confirm that bug is occurring in Maverick as well, the workaround
is to "repackage" the .p12 exported user certificate (both private and
public key) as Remco Poortinga explained above.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received
For me using "Tunneled TLS" for Authentication and "PAP" for Inner
Authentication does work reasonably well. It still is not nearly as
stable as it's for Windows or Mac clients but since there doesn't seem
to be any maintainer using an eduroam network it's probably the best
we'll get.
--
Network-
Further investigation turns out, it doesn't connect to eduroam on a
liveusb version of Lucid either.
I have attached dmesg prints, iwlist scan results and the certificate
for my network.
** Attachment added: "files.tar.bz2"
https://bugs.launchpad.net/network-manager-applet/+bug/445487/+attach
I can confirm having this bug on a fully updated Maverick. I tried using
three different network cards, none were able to connect to my schools
WPA2 Enterprise network (eduroam). The network uses PEAP and MSCHAPv2.
The network cards I tried are using the modules: ipw2200, p54 and ath9k.
I am only
finally
On Thu, Sep 16, 2010 at 3:35 PM, Bug Watch Updater <
445...@bugs.launchpad.net> wrote:
> ** Changed in: network-manager-applet
>Importance: Unknown => High
>
> --
> Network-Manager fails WPA2 Enterprise configuration
> https://bugs.launchpad.net/bugs/445487
> You received this bug not
** Changed in: network-manager-applet
Importance: Unknown => High
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Tags added: regression-release
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
In Lucid I'm still seeing the issue which is addressed by the workaround
in post #15. Specifically, the GUI will not load a PKCS12 file which is
lacking the friendlyName attribute. The workaround in #15 adds it. This
is a pretty silly bug, and might even be understandable if the GUI ever
displayed
Patrick, that commit is in the Lucid version. I guess you're seeing a
different issue.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
There is a further easy workaround which works also with nm-connection-
editor on karmic. Just concatenate your privatekey together with your
cert like
cat key.pem cert.pem > mynewkey.pem # key.pem needs to be encryted
with a password!
Then use mynewkey.pem as new "private key" and the Apply
** Changed in: network-manager-applet
Status: Unknown => New
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
** Changed in: network-manager-applet (Ubuntu)
Status: Fix Released => Confirmed
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubu
** Bug watch added: GNOME Bug Tracker #590644
https://bugzilla.gnome.org/show_bug.cgi?id=590644
** Also affects: network-manager-applet via
https://bugzilla.gnome.org/show_bug.cgi?id=590644
Importance: Unknown
Status: Unknown
--
Network-Manager fails WPA2 Enterprise configuration
Attached a patch, which lets you use a .pem as private-key-file in nm-
connection-editor. The button "Apply" should then work. I tested it in
the nm-connection-editor in Karmic, but couldn't test it with wlan
neither with lucid. You have to use your .pem file together with a
password, otherwise net
With nm-connection-editor I still have problems. As workaround I avoided
using it and used a system-connection file instead. See the attached
example file. It works for Karmic and Lucid. HTH, Patrick
** Attachment added: "A network-manager system-connection file to avoid
nm-connection-editor"
I can confirm note #23:
Bug still exists and Workaround #15 works. In my case I had .pem files and had
to convert them to .p12
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs
network-manager 0.8-0ubuntu3 still has this problem, it is not fixed in
Lucid. The workaround works however.
** Changed in: network-manager-applet (Ubuntu Lucid)
Status: Fix Released => Confirmed
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
Hi!
Same problem as Tyrael has.
The options for key type selection on WPA-Enterprise selection don't
exists.
Since i Need for my college connection to select a WPA-EAP connection
with key type = TKIP, i'm unable to connect to it using network-manager,
and when it does, it drops quickly. Using no
Yesterday I tried to connect to my university wifi network with Ubuntu Lucid
Beta 2.
To connect to the network I have to use the config in the attachment but with
the new version of network I can't.
** Attachment added: "config needed for wifi network"
http://launchpadlibrarian.net/44252912/u
I have just tested this, it is now working properly in Lucid's network-
manager package. Closing Lucid task.
** Changed in: network-manager-applet (Ubuntu Lucid)
Status: Confirmed => Fix Released
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
Any news of a patch?
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
I can confirm solution #15 by "Remco Poortinga - van Wijnen" works just
fine for me. Thanks a lot Remco. And why haven't they released a patch
to fix this? Not good.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification be
** Tags added: iso-testing
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
** Also affects: network-manager-applet (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: network-manager-applet (Ubuntu Lucid)
Importance: Undecided
Status: Confirmed
** Changed in: network-manager-applet (Ubuntu Karmic)
Status: New => Confirmed
--
N
Thanks guys, I've spent 3hrs yesterday trying to fixing it. I used the
latest image of Karmic on Dec 21. How come a bug like this stays unfixed
for 2 months...hmmm...
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification b
Thank You!
On Nov 23, 2009, at 3:16 AM, Remco Poortinga - van Wijnen wrote:
> A colleague of mine (Thank you Francois) found a workaround that worked for
> me:
> My situation: similar error message in .xsession-errors, wasn't able to
> 'apply' or select the .p12 certificate for WPA(2)-Enterpri
A colleague of mine (Thank you Francois) found a workaround that worked for me:
My situation: similar error message in .xsession-errors, wasn't able to 'apply'
or select the .p12 certificate for WPA(2)-Enterprise, separate .pem files for
usercert and key didn't work either.
Repackaging the orig
Problem confirmed (Lenove T61, iwlagn)
- Same here, unable to access corporate WLAN. This is a serious
regression!
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
same problem here. cannot connect to corporate WLAN :-(
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bug
You still may use my workaround patch. You may get a prebuilt package
from my repo if you trust other's builds: http://repo.paulus.ru/. You
need a libnm-util1 package.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification
Forget the remark about "system CA certificates", I'd been looking at
the wrong version; the one that ships with Karmic doesn't offer this.
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of
A workaround for Karmic that I was recently pointed to is (assuming WPA2
enterprise with TLS auth and that your CA provides .p12 files - my eduroam site
does):
- enter your identity as usual (this often matches what's in your user
certificate)
- leave "User Certificate" blank
- provide the root
Is there presently a work-around?
I tried forcing version to the Jaunty versions of network-manager,
network-manager-dev and network-manager-gnome, and no joy. The menu
appears, and it shows the networks, but have the same error with the
correct password not being accepted.
I may have to re-inst
** Changed in: network-manager-applet (Ubuntu)
Status: New => Confirmed
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- Apply button remains disabled when configuring 802.1x
+ Network-Manager fails WPA2 Enterprise configuration
--
Network-Manager fails WPA2 Enterprise configuration
https://bugs.launchpad.net/bugs/445487
You received this bug notification because you are a member of Ubuntu
Bu
53 matches
Mail list logo
