Launchpad has imported 37 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1241930.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Thanks Mathieu for separating the MTU issues from the PMK key mismatch
problems during TLS 1.2 negociation.
I'm facing the latter: and tried to apply this patch:
"EAP-TLS/TTLS/PEAP workaround for incorrect TLS v1.2 MSK derivation"
http://lists.shmoo.com/pipermail/hostap/2015-July/033312.html
For starters, if you're seeing this message: "l2_packet_send - sendto:
Message too long", it likely means that you're hitting that MTU problem
with NM, which has been fixed already as pointed out by Christian.
If you're hitting *any other* problem, please file *your own* bug, using
the following
** Changed in: wpa (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on WPA enterprise networks
To
The corresponding bug in NetworkManager was fixed:
https://bugs.launchpad.net/ubuntu/wily/+source/network-manager/+bug/1499827/comments/12
Should solve this problem as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
See also
https://bugs.launchpad.net/ubuntu/wily/+source/network-manager/+bug/1499827
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on WPA
Setting the MTU for the WiFi connection in NetworkManager from "auto" to
"1500 bytes" solves my problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently
The logs submitted by the bug reporter contain lines like
Sep 30 23:31:07 castiana wpa_supplicant[25653]: l2_packet_send - sendto:
Message too long
I had exactly the same problem, so I checked the MTU of my wireless
interface and noticed that it was set to 1280.
After issuing
ifconfig mtu
I have the same problem Downgrading to wpasupplicant 2.1-0ubuntu7 works
for me on my corporate network.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently
Me too. Same problem, and downgrading fixes it for me too.
What exactly do the WPA Supplicant people think is wrong with the RADIUS
servers? I can't find that anywhere online.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Nevermind, I found the redhat bug with the RADIUS info.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on WPA enterprise networks
To manage
Confirmed that downgrading to wpa 2.1-0ubuntu7.2 fixes the issue for me
on corporate network.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on
Same problem here. Can no longer connect to corporate wifi since
upgrading
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on WPA enterprise
Just noting that installing version 2.1-0ubuntu7.2 from Vivid and
pinning it works as workaround.
In addition, I tend to agree with comment #6 on the importance of having
an adequate understanding of the severity of the issue. Nobody can
expect and force all those faulty Radius servers to be
In my case it's not frequency fails - it always fails. On 3 separate WAP
Enterprise SSIDs.
I understand that the WPA Supplicant people say this is a Radius server
bug and not a supplicant bug. That may be true, but there is little
chance of the offending radius servers on the WPA Enterprise
** Changed in: wpa (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
Wily's wpasupplicant frequently fails on WPA enterprise networks
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wpa (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1501588
Title:
** Bug watch added: Red Hat Bugzilla #1241930
https://bugzilla.redhat.com/show_bug.cgi?id=1241930
** Also affects: hostap via
https://bugzilla.redhat.com/show_bug.cgi?id=1241930
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
I'm also running Wily since a week, and I'm unable to connect to my corporate
WiFi anymore.
I did a downgrade to the wpa-supplicant version in Debian Sid (2.3-2.1) and the
connection works fine again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Arch had same issue it seems:
https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/wpa_supplicant=7562b98bd83fe5bce43e6952e0e922e7791e18b5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Same issue happened again after I downgraded to vivid's version...
Now rebooting my laptop on a vivid kernel to confirm it's a kernel bug
and not a wpasupplicant bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
21 matches
Mail list logo
