Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
04-13-2016, 07:50 AM
|
#16
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep: 
|
Quote:
Originally Posted by ardvark71
Hi...
Awesome! If you could identify the culprit, perhaps a patch could be released by the folks who develop/maintain it. 
Regards... |
Yes, I shall try to do that. It is important to pinpoint the issue because it is already inherited by fc23, which cannot connect to TLS network either, not even from a LiveCD.
Only I need to find the time for debugging. The TLS network in question is a corporate network, so I must do all this experimenting during the work time. The important thing is that I'm mobile again and do not have to boot Windows when going to meetings. |
|
|
|
|
04-13-2016, 12:24 PM
|
#17
|
|
LQ Veteran
Registered: Feb 2015
Location: USA
Distribution: Lubuntu 14.04, 22.04, Windows 8.1 and 10
Posts: 6,282
|
Quote:
Originally Posted by blnl
Yes, I shall try to do that. It is important to pinpoint the issue because it is already inherited by fc23, which cannot connect to TLS network either, not even from a LiveCD.
Only I need to find the time for debugging. The TLS network in question is a corporate network, so I must do all this experimenting during the work time. The important thing is that I'm mobile again and do not have to boot Windows when going to meetings.
|
Hi...
Let us know what you find out.
Regards... |
|
|
|
|
04-14-2016, 05:12 AM
|
#18
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep:
|
At this point in time, as long as the TLS network connection works with kernel version:
Code:
kernel.x86_64 4.0.4-301.fc22 @fedora
I decided to try out if it still works with the latest kernel. To my surprise and disappointment, it does not.
It does not work with the latest kernel version:
Code:
kernel.x86_64 4.4.6-201.fc22 @updates
Now I'm totally confused. I do not understand this kernel dependency...
With the latest kernel the wifi interface does not exist at all. Not only TLS network, but any other wireless network is not available. There is nothing to choose from.
This is the iwconfig output with 4.4.6-201.fc22 kernel:
Code:
/boris@E7440 ~/$ iwconfig
virbr0-nic no wireless extensions.
virbr0 no wireless extensions.
eno1 no wireless extensions.
lo no wireless extensions.
This is the iwconfig output with 4.0.4-301.fc22 kernel (with wifi turned off):
Code:
[boris@E7440 ~]$ iwconfig
virbr0-nic no wireless extensions.
virbr0 no wireless extensions.
wlp2s0 IEEE 802.11abgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=off
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on
eno1 no wireless extensions.
lo no wireless extensions.
|
|
|
|
|
04-14-2016, 07:32 AM
|
#19
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep:
|
For the time being I'm stuck with the 4.0.4-301.fc22 kernel. Now I'm proceeding with the evaluation of the individual packages.
So far, NetworkManager related and gnutls related packages have been eliminated as potential root-cause for this issue.
These are my remaining suspects...
Code:
[root@E7440 boris]# dnf update
Last metadata expiration check performed 1:21:56 ago on Thu Apr 14 13:03:42 2016.
Dependencies resolved.
==============================================================================================================================================
Package Arch Version Repository Size
==============================================================================================================================================
Upgrading:
iwl100-firmware noarch 39.31.5.1-61.fc22 updates 154 k
iwl1000-firmware noarch 1:39.31.5.1-61.fc22 updates 217 k
iwl105-firmware noarch 18.168.6.1-61.fc22 updates 238 k
iwl135-firmware noarch 18.168.6.1-61.fc22 updates 247 k
iwl2000-firmware noarch 18.168.6.1-61.fc22 updates 241 k
iwl2030-firmware noarch 18.168.6.1-61.fc22 updates 250 k
iwl3160-firmware noarch 1:25.30.13.0-61.fc22 updates 979 k
iwl3945-firmware noarch 15.32.2.9-61.fc22 updates 92 k
iwl4965-firmware noarch 228.61.2.24-61.fc22 updates 105 k
iwl5000-firmware noarch 8.83.5.1_1-61.fc22 updates 298 k
iwl5150-firmware noarch 8.24.2.2-61.fc22 updates 151 k
iwl6000-firmware noarch 9.221.4.1-61.fc22 updates 171 k
iwl6000g2a-firmware noarch 18.168.6.1-61.fc22 updates 314 k
iwl6000g2b-firmware noarch 18.168.6.1-61.fc22 updates 314 k
iwl6050-firmware noarch 41.28.5.1-61.fc22 updates 247 k
iwl7260-firmware noarch 1:25.30.13.0-61.fc22 updates 2.5 M
wpa_supplicant x86_64 1:2.4-7.fc22 updates 1.0 M
Transaction Summary
==============================================================================================================================================
Upgrade 17 Packages
Total download size: 7.5 M
Is this ok [y/N]: n
Operation aborted.
|
|
|
|
|
04-14-2016, 02:53 PM
|
#20
|
|
LQ Veteran
Registered: Feb 2015
Location: USA
Distribution: Lubuntu 14.04, 22.04, Windows 8.1 and 10
Posts: 6,282
|
This is some excellent detective work.
Regards... |
|
|
|
|
04-19-2016, 04:11 AM
|
#21
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep:
|
At last, all firmware (iwl*-firmware) packages have been upgraded, TLS wifi network still works (also with the latest kernel version).
There is only one package left, wpa_supplicant...
So the conclusion of this exercise is following:
TLS network connection works fine:
Code:
[root@E7440 ~]# dmesg | tail -n 15
[ 222.992544] iwlwifi 0000:02:00.0: RF_KILL bit toggled to enable radio.
[ 222.992865] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 222.993194] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 223.201102] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 223.201429] iwlwifi 0000:02:00.0: L1 Enabled - LTR Enabled
[ 223.219686] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 223.240283] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[ 225.748795] wlp2s0: authenticate with 84:b8:02:de:99:11
[ 225.751748] wlp2s0: send auth to 84:b8:02:de:99:11 (try 1/3)
[ 225.752802] wlp2s0: authenticated
[ 225.753297] wlp2s0: associate with 84:b8:02:de:99:11 (try 1/3)
[ 225.755509] wlp2s0: RX AssocResp from 84:b8:02:de:99:11 (capab=0x431 status=0 aid=22)
[ 225.756869] wlp2s0: associated
[ 225.756900] IPv6: ADDRCONF(NETDEV_CHANGE): wlp2s0: link becomes ready
It works with the latest kernel version too:
Code:
[root@E7440 ~]# uname -a
Linux E7440.DELL 4.4.6-201.fc22.x86_64 #1 SMP Wed Mar 30 18:30:16 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
The system is fully updated, except for the wpa_supplicant package.
Code:
[root@E7440 ~]# dnf update
Last metadata expiration check performed 0:21:56 ago on Tue Apr 19 10:40:34 2016.
Dependencies resolved.
=========================================================================================================================
Package Arch Version Repository Size
=========================================================================================================================
Upgrading:
wpa_supplicant x86_64 1:2.4-7.fc22 updates 1.0 M
Transaction Summary
=========================================================================================================================
Upgrade 1 Package
Total download size: 1.0 M
Is this ok [y/N]: n
Operation aborted.
Hence, the wpa_supplicant is the root-cause for the TLS network connection issue.
Before filing a bug report, I'm going to verify this by upgrading the wpa_supplicant... |
|
|
|
|
04-19-2016, 02:08 PM
|
#22
|
|
LQ Veteran
Registered: Feb 2015
Location: USA
Distribution: Lubuntu 14.04, 22.04, Windows 8.1 and 10
Posts: 6,282
|
Quote:
Originally Posted by blnl
Before filing a bug report, I'm going to verify this by upgrading the wpa_supplicant...
|
Hi...
If you would, if you make a bug report, please post the link to it.
Regards... |
|
|
|
|
04-20-2016, 10:52 AM
|
#23
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep:
|
Quote:
Originally Posted by ardvark71
Hi...
If you would, if you make a bug report, please post the link to it.
Regards... |
The bug report can be found at: - Bug 1328927 - wpa_supplicant TLS network connection issue
So, that is done, now we wait ... |
|
|
|
|
04-20-2016, 11:29 AM
|
#24
|
|
LQ Veteran
Registered: Feb 2015
Location: USA
Distribution: Lubuntu 14.04, 22.04, Windows 8.1 and 10
Posts: 6,282
|
Quote:
Originally Posted by blnl
The bug report can be found at: - Bug 1328927 - wpa_supplicant TLS network connection issue
So, that is done, now we wait ... |
Thank you. Just as a suggestion, I wonder if including a link to this thread might be helpful.
Regards... |
|
|
|
|
04-21-2016, 04:49 AM
|
#25
|
|
Member
Registered: Nov 2009
Location: The Netherlands
Distribution: Fedora
Posts: 95
Original Poster
Rep:
|
Quote:
Originally Posted by ardvark71
Thank you. Just as a suggestion, I wonder if including a link to this thread might be helpful.
Regards... |
I'm not sure, it might just confuse the conversation. In the bug report, I have given the essential details of the issue. The given information should be sufficient for the developers to reproduce the issue (the debugging process described in the thread is not relevant).
If I can find the source code for the two wpa_supplicant versions, I will diff them to see if something interesting/obvious pops up. That could be more useful for the bug report... |
|
|
|
All times are GMT -5. The time now is 07:21 PM.
|
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
|
 Latest Threads
LQ News
|
|
