*** This bug is a duplicate of bug 105899 ***
https://bugs.launchpad.net/bugs/105899
** Changed in: network-manager
Status: Confirmed => Fix Released
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a me
*** This bug is a duplicate of bug 105899 ***
https://bugs.launchpad.net/bugs/105899
** Changed in: network-manager
Status: New => Confirmed
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of U
*** This bug is a duplicate of bug 105899 ***
https://bugs.launchpad.net/bugs/105899
The problem reported here and in most of the comments is that
KNetworkManager doesn't allow you to select TKIP, which is the same as
bug 105899. Network-manager supports it, knetworkmanager is just
missing th
** Changed in: network-manager
Status: Unknown => New
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.
--
kubuntu-bugs mailing
** Bug watch added: GNOME Bug Tracker #471525
http://bugzilla.gnome.org/show_bug.cgi?id=471525
** Also affects: network-manager via
http://bugzilla.gnome.org/show_bug.cgi?id=471525
Importance: Unknown
Status: Unknown
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad
hans: sorry, that was my bad, I did not properly understood the triaging
proces by then.
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bug
** Tags added: networkmanager nm-applet
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTE
Putting this bug back to "new" from "invalid". Someone needs to justify
why they put this one as "invalid". If it is because the problem is not
the Network Manager per say, but the Gnome application, then nm-applet
should be listed too.
** Changed in: network-manager (Ubuntu)
Status: Inva
The problem still persist in Hardy Heron 08.04 Alpha 4 (A4), at least
for TTLS.
BTW, why is this bug stated as "invalid" against the network-manager?
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Ubu
For the Key Type Problem, see this beg : #105899
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL
Hi,
looks like there is a patch that adds Key Type to the dialog but it
can't be applied to current gutsy knetworkmanager.
You can found it there : http://bugs.kde.org/show_bug.cgi?id=138504
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug no
I've just upgraded to Gutsy, and knetworkmanager still fails to connect
to a PEAP-based network. WPA-Personal works fine, even through
knetworkmanager, but the PEAP option doesn't seem to work.
knetworkmanager 1:0.2ubuntu1-0ubuntu4
network-manager 0.6.5-0ubuntu11
--
networkmanager can't use PEA
After a few more researches, this is NetworkManager 0.6.5, that will be
included in Gutsy Gibbon :-)
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
It also seems that there is a NetworkManager version on which phase2 is
available (I don't know which version this image comes from) :
http://rorschach.concordia.ca/neg/remote_access/wireless/gnome-network-
manager.png
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/10732
That is this bug ID (107321).
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in ubuntu.
--
kubuntu-bugs mailing list
[EMAIL PROTECTED]
https:/
can you guys see if this is the same issue?
https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/107321
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for
I added knetworkmanager to this bug ... as this appears to be not a
network-manager issue.
** Also affects: knetworkmanager (Ubuntu)
Importance: Undecided
Status: New
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notification beca
I am using all latest packages from Gutsy. I have also wiped my
installation and performed a clean install from Tribe 4 CD and all
updates.
Packages are:
network-manager-kde 1:0.2ubuntu1-0ubuntu1
network-manager 0.6.5-0ubuntu9
wpasupplicant
On Fri, Aug 10, 2007 at 08:56:48PM -, Tix6174 wrote:
> I disagree with that last comment as this isn't a LEAP issue, but rather
> with the configuration options available within KNetworkManager.
>
> I can connect to any network using any valid security configuration as
> long as wpa_supplicant
I disagree with that last comment as this isn't a LEAP issue, but rather
with the configuration options available within KNetworkManager.
I can connect to any network using any valid security configuration as
long as wpa_supplicant is used. If I use KNetworkManager, I can only
connect consistenly
This has been fixed upstream (http://mail.gnome.org/archives
/networkmanager-list/2006-July/msg00034.html - here is a patch that adds
the support), therefore it will undoubtly be included in Gutsy. I reject
this because it will not get solved before Gutsy anyway...
** Changed in: network-manager (
A week ago I was at a commercial center and there was a secure AP that I
mistakenly clicked on. To my surprise, NM showed me PEAP options (I
should have taken a screenshot). Of course, I could not connect since I
did not had any authorization, so I could not test if an actual
connection was possi
This should be confirmed. This is really annoying to use an outdated method
while it could just work if it was integrated with NM.
I am willing to pay to see this feature implemented.
--
networkmanager can't use PEAP or TTLS
https://bugs.launchpad.net/bugs/107321
You received this bug notificat
This should be confirmed. A simple search with Google reveals a lot of
people with the same problem:
http://www.google.com/search?hl=en&q=peap+network.manager&btnG=Google+Search
I have this problem with the Concordia University Wireless network
(Montreal). A user provides a workaround:
http://
Very similar situation for me: I have to be able to use eap=TLS and
pairwise=TKIP, but there is no way to specify it in knetworkmanager.
With wpasupplicant configured "by hand" everything works well.
The same bug for knetworkmanager can be found in KDE's bugtracker:
http://bugs.kde.org/show_bug.c
I can confirm this.
I spent the better part of today trying to connect to my University's
TTLS network before figuring it out via wpa_supplicant.
Here is my wpa_supplicant configuration:
ctrl_interface_group=0
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
fast_reauth=1
network
26 matches
Mail list logo
