Still not fixed on 2022-12-27. Ubuntu 20.04 LTS 64-bits. NetworkManager
version 1.22.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to
Hi,
I really do not remember any more how that somehow disappeared. Could
it be that changing the channel at the wifi router could help?
Unfortunately I did not remember that I reported the problem otherwise
I would have immediately reported a possible workaround.
Best regards, Martin.
--
You
Affects me too at WeWork in 2021!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Status in
I also have the problem with 18.04.4 LTS (up to date at time of writting). It
seems to be related to the Wifi infrastructure since the problem appeared for
me a few months ago (running successfully from May 2018 to Oct 2019).
However many other devices can connect successfully to the Wifi
Note that the problem also occurs in all debian distros including the
most recent testing (but again not fedora 29+/arch ones). I feel like if
we can find the difference in how the MSCHAPV2 or etc is handled, we can
solve this pesky bug.
--
You received this bug notification because you are a
I have this same issue. What's very curious though is that I can connect to my
work's network with Fedora 29+ (28 didn't work) as well as Arch/Manjaro based
distros but not any Ubuntu version (including most recently 19.10) I can't.
Just get repeated authentication failures. It's something to
I have the problem despite I tried to forget the network and tried
connecting again.
snadar@ThinkPad-T480:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
snadar@ThinkPad-T480:~$ cat
Think it has something to do with the browser used for hotpot
If anyone can find what confi controls in network manager for what browser to
use (suspect chromium because it exhibits same behavior and is default install,
but Firefox works) can find way to change configuration to use working
Hi... I have this problem in ubuntu 19.04 right now. Any clue? Thanks
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to
I confirm this bug on 19.04. Wifi worked well on Ubuntu 16.04. Why
doesn't Ubuntu go back to whatever worked in 16.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I confirm the issue in 19.04. I just upgraded from 16.04. I used to get
in fine on eduroam not anymore.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Nothing helpful in this post but can confirm this issue still exists in
19.04. :(
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect
Confirmed the same problem, ubuntu 18.04.2 LTS AMD64, when trying to
connect to "eduroam" in several sites in several countries.
I have to say this is pretty annoying.
Same message as mentioned before:
124171.865640] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by
ac:a3:1e:c5:84:a0
Use Firefox to connect to the hotspot is working for me .. need to find out
how to rejig the Ubuntu hotspot connector to use firefox .. might just be a
browser negotiation issue.
On Sat, Mar 23, 2019 at 10:25 AM fossfellow
wrote:
> I have the same problem on Ubuntu 16.04 LTS
> WiFi works
I have the same problem on Ubuntu 16.04 LTS
WiFi works perfectly from home (WPA2/WEP)
Does not connect to WPA2 Enterprise with PEAP. Checked with IT department ,
they could not solve it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Looking at the dmesg | grep wlp2s0 can also put some light on this.
Apparently, TX Power Saver causes connection loss for networks with PEAP
authentication.
WiFi works fine on home networks (WPA2/WEP)
Drops at college/work. (PEAP)
This was my last output.
[570105.023727] wlp2s0: Limiting TX
Bug #1761003 also may be related.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Status in
OK, how'd this slip through? No WPA options anywhere? Only 2 WEP
options. 2 new installs, on different machines, I can not connect to my
WPA (TKIP+AES) network wirelessly!!!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Could be a good idea to report it upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I am facing the same issue with my ubuntu 18.04. My PC gets connected to
unprotected wifi easily, however it shows activation error while trying
to connect to a protected wifi.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I would have expected something in dmesg. After test, check timestamps
of other logfiles in /var/log - maybe you then find a log which contains
useful information.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
How to activate log to understand what blocks the wifi connection ?
I watched "dmesg," but i saw nothing.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Then it really looks like a bug. It would be good to have logfiles for
both cases to compare them.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
@Martin: On the same PC, it is impossible to connect to WiFi with Ubuntu
18.10, but it works with a bootable USB key Ubuntu 16.04.05
WiFi-Security :
- Security: WPA2 Enterprise
- Authentification: Protected EAP (PEAP)
- CA certificate : No CA certificate
- PEAP version : version 0
- Inner
@Vivien: Most probably they did not tell you the correct settings -
please verify with the responsible IT admin that you are using the
correct settings.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in
I m still unable to connect to WPA2 Enterprise Network after installing
all the apt updates with Ubuntu 18.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
@VascoT: Delete the configuration and reconnect to the wifi doing the
configuration from fresh.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
With the newest packages on 18.04 I can still not connect to eduroam. In
system-settings -> network, when I click on eduroam a round "progress"
thing starts to rotate, but no question is asked for credentials. Also
no log messages are showed in syslog or kern.log. How to debug this
issue?
--
You
Bug is also happening on 18.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Status in
It is still an issue for me. The wifi authentication works perfectly
with Eduroam (that requires a CA certificate) that is not the case with
the other Wifi network (without CA certificate but all the same for the
other settings).
--
You received this bug notification because you are a member of
Fixed for me, I didn't do anything different or change anything, I guess
one of the Ubuntu updates must've fixed it
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
I m still unable to connect to WPA2 Enterprise Network after installing
all the apt updates
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem
I am glad that I could help somehow. I had the issue with a wifi provided by a
Ubiquity AaccessPoint. I am pretty sure that there was no update on that in the
meantime as it was a new install and configuration (however I am not the admin
on that net and I have no details).
In the meantime I got
@mwildam : Due to your comment on that it might be resolved, I also checked the
bug again.
For me this issue is now also resolved.
I m not sure why this is resolved, but I can think of two reasons:
- The wifi I previously attempt to connect to got updated/upgraded and now
supports connections
In my case I was able to solve the problem by changing some settings:
Security: WPA & WPA2 Enterprise
* Authentication: Protected EAP (PEAP)
* No certificate is required: Checked
PEAP version: Automatic
* Inner authentication: MSCHAPv2
Now I am not sure, if I am simply not affected by the bug and
@BrettSkogen - thanks for reporting back. I was going to try the OpenSSL
downgrade myself but haven't had the time. I'd be curious to see what
you find out by looking at the update-crypto-policies command. Let us
know what you find out. Going to take a look at it myself now.
--
You received this
I can tell you something that doesn't work, to hopefully save you some
time. One of the earlier comments on this bug suggested that the issue was
being caused by support for 3DES being removed from Bionic Beaver. I
downloaded the source code for OpenSSL 1.1.0i, and compiled the code with
the
I also ran into this issue after upgrading from 16.04 to 18.04.
Any updates on this?
What's the Ubuntu equivalent of the Fedora workaround for this? ($
update-crypto-policies --set LEGACY)
If it is not available, is it possible to make a fix by downgrading openSSL? If
so, can you please explain
I wanted to try the
update-crypto-policies --set LEGACY
but I am using Ubuntu 18.04.1 and I could not find an equivalent command.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Any updates on this? I ran into this issue after upgrading from 16.04 to
18.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect
** Attachment added: "Connection attempt second wifi with PEAP"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+attachment/5188874/+files/wlan-connection-attempt-20180914b.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Kernel log for the previous attempts.
** Attachment added: "Kernel log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+attachment/5188875/+files/wlan-connection-attempt-20180914.log
--
You received this bug notification because you are a member of Ubuntu
Touch
Dell Precision 7520, I also cannot connect to WPA2/PEAP WIFI. Here are
my logs - I tried to connect to two slightly different configured wifi
networks using that PEAP (I never heard of that before).
** Attachment added: "Connection attempt first wifi with PEAP"
I tried downgrading wpa-supplicant (mentioned by Lauwie), and it did not
help this.
If Petr is correct, the fix would actually require downgrading OpenSSL
(or whatever used to supply the missing 3DES cipher prior to Bionic),
right?
What's the Ubuntu equivalent of the Fedora workaround for this?
** Description changed:
- Connection to open or WPA secured wifi works without any issues.
- Connection to WPA2/PEAP fails. Repeatedly asks for username/password.
+ This problem is also happened on my desktop.
- Possible gnome-shell integration issue.
+ After upgrading OS from Ubuntu 16.04 to
Update:
We have made sofar couple of discoveries, thanks to Petr Jediny.
We suspected OpenSSL incompatibility in the OS, so as the PEAP is
creating underlying TLS tunnel for auth and we see an error in
wpa_supplicant regarding TLS negotiation (hello).
tl;dr - Cypher set of Ubuntu bionic do not
This affects all academic users that uses eduroam to connect to the
internet. Please fix. Eduroam did work with ubuntu 17.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
A potential fix has been proposed in my askubuntu quesion:
https://askubuntu.com/questions/1046810/cannot-downgrade-wpa-supplicant-to-fix-wifi-connection-to-a-corporate-network-w
However, I have not been able to test if this works yet. (as I got some
deadlines and cannot afford a potentially
Same problem here. Eduroam cannot be connected. Please solve!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI
same here. A fix would be highly appreciated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Same issue on a Lenovo T480s.
I tried to apply this without any success :
https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
I have the same issue with (a clean/full wipe/ fresh install) Ubuntu
18.04 on a Dell XPS 15 9550.
Previously, on Ubuntu 16.04 downgrading wpa_supplicant to version 2.1
helped resolve this. See here: https://askubuntu.com/questions/690032
Same issue with Ubuntu 18.04 on a Dell XPS 15 9560.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI -
Same problem here in Kubuntu 18.04.
The authentication layer works fine, but for some reason it fails in
configuring the network.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
This affects me as well. And can't connect to my company tools.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI
This affects me as well. I consider this a security issue because the
enterprise I'm connecting to only offers this encryption or no
encryption, so until this is fixed, my network traffic is unencrypted.
And that's sad.
--
You received this bug notification because you are a member of Ubuntu
Also got it. Up
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Status in network-manager
Also happens on 17.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to connect to WPA2/PEAP WIFI - gnome-shell
Status in network-manager
This could be related https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1761003
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
I tried downgrading network-manager and wpasupplicant to the artful versions.
Still can't authenticate.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Just an update, I was in a different office location today using WPA2 / PEAP
and wifi connected right away. Same business, NW engineers tell me
infrastructure is exactly the same in both locations - so mystery - phone
Android connected perfectly but laptop did not (in other building)!
So pity
Same problem here, standard WPA2 works fine but not WPA2/PEAP.
Worked fine in 17.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1748839
Title:
Problem to
This affects me too, 18.04 WPA2/PLEAP connect via phone tether OK but
fails as above directly, worked fine under 17.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
** Summary changed:
- Problem to connect to WPA2/PLEAP WIFI - gnome-shell
+ Problem to connect to WPA2/PEAP WIFI - gnome-shell
** Description changed:
Connection to open or WPA secured wifi works without any issues.
- Connection to WPA2/PLEAP fails. Repeatedly asks for username/password.
+
65 matches
Mail list logo
