#StackBounty: #wifi #key-authentication #iwd iwd with EAP-TLS fails with 'Failed to load <pem>'

Bounty: 50

I want to connect to an EAP-TLS access point using iwd, however this fails because it apparently cannot open my client key:

# iwctl
[iwd]# station wlan0 connect foo
Not configured

iwd says:

src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

My kernel is the latest stable one and I’ve enabled CONFIG_PKCS8_PRIVATE_KEY_PARSER:

# uname -r
5.2.1
# lsmod | grep pkcs8_key_parser
pkcs8_key_parser       16384  0

iwd

# /usr/libexec/iwd --version
0.18
# export IWD_TLS_DEBUG=1
# /usr/libexec/iwd -d
[..]
src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

/var/lib/iwd/foo.8021x

[Security]
EAP-Method=TLS
EAP-TLS-ClientCert=/var/lib/wirelss/skybert.pem
EAP-TLS-ClientKey=/var/lib/wireless/skybert.des3.key 
EAP-TLS-ClientKeyPassphrase=youwish
EAP-Identity=skybert

The corresponding, working, wpa_supplicant block was:

network={
   ssid="foo"
   key_mgmt=WPA-EAP
   proto=WPA2
   eap=TLS
   identity="skybert"
   client_cert="/var/lib/wireless/skybert.pem"
   private_key="/var/lib/wireless/skybert.des3.key"
   private_key_passwd="youwish"
}

OS

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

(trying to) read the source

From what I can tell, it’s ell/ell/pem.c (called from iwd/src/eap-tls-common.c) which cannot load the certificate, but that’s as far as I’ve come. The error message is the same if the path exists or if it doesn’t.

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #wifi #key-authentication #iwd iwd with EAP-TLS fails with 'Failed to load <pem>'

Bounty: 50

I want to connect to an EAP-TLS access point using iwd, however this fails because it apparently cannot open my client key:

# iwctl
[iwd]# station wlan0 connect foo
Not configured

iwd says:

src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

My kernel is the latest stable one and I’ve enabled CONFIG_PKCS8_PRIVATE_KEY_PARSER:

# uname -r
5.2.1
# lsmod | grep pkcs8_key_parser
pkcs8_key_parser       16384  0

iwd

# /usr/libexec/iwd --version
0.18
# export IWD_TLS_DEBUG=1
# /usr/libexec/iwd -d
[..]
src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

/var/lib/iwd/foo.8021x

[Security]
EAP-Method=TLS
EAP-TLS-ClientCert=/var/lib/wirelss/skybert.pem
EAP-TLS-ClientKey=/var/lib/wireless/skybert.des3.key 
EAP-TLS-ClientKeyPassphrase=youwish
EAP-Identity=skybert

The corresponding, working, wpa_supplicant block was:

network={
   ssid="foo"
   key_mgmt=WPA-EAP
   proto=WPA2
   eap=TLS
   identity="skybert"
   client_cert="/var/lib/wireless/skybert.pem"
   private_key="/var/lib/wireless/skybert.des3.key"
   private_key_passwd="youwish"
}

OS

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

(trying to) read the source

From what I can tell, it’s ell/ell/pem.c (called from iwd/src/eap-tls-common.c) which cannot load the certificate, but that’s as far as I’ve come. The error message is the same if the path exists or if it doesn’t.

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #wifi #key-authentication #iwd iwd with EAP-TLS fails with 'Failed to load <pem>'

Bounty: 50

I want to connect to an EAP-TLS access point using iwd, however this fails because it apparently cannot open my client key:

# iwctl
[iwd]# station wlan0 connect foo
Not configured

iwd says:

src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

My kernel is the latest stable one and I’ve enabled CONFIG_PKCS8_PRIVATE_KEY_PARSER:

# uname -r
5.2.1
# lsmod | grep pkcs8_key_parser
pkcs8_key_parser       16384  0

iwd

# /usr/libexec/iwd --version
0.18
# export IWD_TLS_DEBUG=1
# /usr/libexec/iwd -d
[..]
src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

/var/lib/iwd/foo.8021x

[Security]
EAP-Method=TLS
EAP-TLS-ClientCert=/var/lib/wirelss/skybert.pem
EAP-TLS-ClientKey=/var/lib/wireless/skybert.des3.key 
EAP-TLS-ClientKeyPassphrase=youwish
EAP-Identity=skybert

The corresponding, working, wpa_supplicant block was:

network={
   ssid="foo"
   key_mgmt=WPA-EAP
   proto=WPA2
   eap=TLS
   identity="skybert"
   client_cert="/var/lib/wireless/skybert.pem"
   private_key="/var/lib/wireless/skybert.des3.key"
   private_key_passwd="youwish"
}

OS

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

(trying to) read the source

From what I can tell, it’s ell/ell/pem.c (called from iwd/src/eap-tls-common.c) which cannot load the certificate, but that’s as far as I’ve come. The error message is the same if the path exists or if it doesn’t.

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #wifi #key-authentication #iwd iwd with EAP-TLS fails with 'Failed to load <pem>'

Bounty: 50

I want to connect to an EAP-TLS access point using iwd, however this fails because it apparently cannot open my client key:

# iwctl
[iwd]# station wlan0 connect foo
Not configured

iwd says:

src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

My kernel is the latest stable one and I’ve enabled CONFIG_PKCS8_PRIVATE_KEY_PARSER:

# uname -r
5.2.1
# lsmod | grep pkcs8_key_parser
pkcs8_key_parser       16384  0

iwd

# /usr/libexec/iwd --version
0.18
# export IWD_TLS_DEBUG=1
# /usr/libexec/iwd -d
[..]
src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

/var/lib/iwd/foo.8021x

[Security]
EAP-Method=TLS
EAP-TLS-ClientCert=/var/lib/wirelss/skybert.pem
EAP-TLS-ClientKey=/var/lib/wireless/skybert.des3.key 
EAP-TLS-ClientKeyPassphrase=youwish
EAP-Identity=skybert

The corresponding, working, wpa_supplicant block was:

network={
   ssid="foo"
   key_mgmt=WPA-EAP
   proto=WPA2
   eap=TLS
   identity="skybert"
   client_cert="/var/lib/wireless/skybert.pem"
   private_key="/var/lib/wireless/skybert.des3.key"
   private_key_passwd="youwish"
}

OS

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

(trying to) read the source

From what I can tell, it’s ell/ell/pem.c (called from iwd/src/eap-tls-common.c) which cannot load the certificate, but that’s as far as I’ve come. The error message is the same if the path exists or if it doesn’t.

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #wifi #key-authentication #iwd iwd with EAP-TLS fails with 'Failed to load <pem>'

Bounty: 50

I want to connect to an EAP-TLS access point using iwd, however this fails because it apparently cannot open my client key:

# iwctl
[iwd]# station wlan0 connect foo
Not configured

iwd says:

src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

My kernel is the latest stable one and I’ve enabled CONFIG_PKCS8_PRIVATE_KEY_PARSER:

# uname -r
5.2.1
# lsmod | grep pkcs8_key_parser
pkcs8_key_parser       16384  0

iwd

# /usr/libexec/iwd --version
0.18
# export IWD_TLS_DEBUG=1
# /usr/libexec/iwd -d
[..]
src/network.c:network_connect() 
src/network.c:network_connect_8021x() 
Failed to load /var/lib/wireless/skybert.pem

/var/lib/iwd/foo.8021x

[Security]
EAP-Method=TLS
EAP-TLS-ClientCert=/var/lib/wirelss/skybert.pem
EAP-TLS-ClientKey=/var/lib/wireless/skybert.des3.key 
EAP-TLS-ClientKeyPassphrase=youwish
EAP-Identity=skybert

The corresponding, working, wpa_supplicant block was:

network={
   ssid="foo"
   key_mgmt=WPA-EAP
   proto=WPA2
   eap=TLS
   identity="skybert"
   client_cert="/var/lib/wireless/skybert.pem"
   private_key="/var/lib/wireless/skybert.des3.key"
   private_key_passwd="youwish"
}

OS

❯ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 10 (buster)
Release:        10
Codename:       buster

(trying to) read the source

From what I can tell, it’s ell/ell/pem.c (called from iwd/src/eap-tls-common.c) which cannot load the certificate, but that’s as far as I’ve come. The error message is the same if the path exists or if it doesn’t.

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #kernel #wifi #firmware #yocto Yocto Boot2Qt Build for Colibri iMX6ULL no wifi interface

Bounty: 50

I have built the linux distro Boot2Qt from source with the yocto tools for the board Colibri iMX6ULL which has the integrated wifi chip Marvell W8997-M1216.

I installed the whole linux firmware-stack and i think also the correct kernel modules for the wifi chip.

There is no mlan interface showing up.

What exactly creates the mlan interface?
Is there something else i need to install?


Get this bounty!!!

#StackBounty: #raspbian #wifi #wpa Wifi Connectivity — Pi 3 Model B

Bounty: 50

I have recently been unable to connect to wifi with my raspberry pi 3 (model B). I have tried a number of solutions to no avail.

The networks button on the upper banner says “connection to dhcpcd lost” or “no wireless interfaces found”.

However, when I try iwlist wlan0 scan to search for networks, I can see dozens of wifi networks, including my own. I then go to sudo nano /etc/wpa_supplicant/wpa_supplicant.conf and add my network and password at the bottom of the file. Even following a reboot I have no networks displaying on the upper bar and no wifi connection.

How come in the terminal my raspberry pi recognizes networks, but not in the GUI? How can I resolve this problem to be able to connect?

Any help would be much appreciated.


Get this bounty!!!

#StackBounty: #wifi #arduino-yun REST API on Industrial 101 (Yún family) lags, then crashes

Bounty: 100

I have tried to set up a very simple REST API on an Arduino Industrial 101 (which is, as far as I understand, equivalent to a Yún). The Arduino is hooked up to a temperature sensor, which value is returned over the REST interface. Everything works fine at first, but over the course of a day it starts taking longer and longer for the device to respond until it completely crashes and becomes unresponsive. (At that point it also doesn’t respond to ping and ssh anymore.)

On the Arduino forum there are several threads reporting similar problems (e.g. this one) but they all seem to be at least a few years old and have been solved in the mean time. (The solution reported here, for instance, has already been incorporated in my Linino version.)

If I reset the ATMega the problem persists, but if I reboot the OS it is solved for a day, so I have reason to suspect something on the Linino side is not working properly. Any help would be much appreciated, although I realize this is quite an old board.

My sketch is basically a dumbed-down version of the Bridge example:

#include <Bridge.h>
#include <BridgeServer.h>
#include <BridgeClient.h>

BridgeServer server;

void setup() {
  pinMode(13, OUTPUT);
  digitalWrite(13, LOW);
  Bridge.begin();
  digitalWrite(13, HIGH);

  server.listenOnLocalhost();
  server.begin();
}

void loop() {
  // Get clients coming from server
  BridgeClient client = server.accept();

  // There is a new client?
  if (client) {
    // Process request
    process(client);

    // Close connection and free resources.
    client.stop();
  }

  delay(50); // Poll every 50ms
}

void process(BridgeClient client) {
  // no matter what the command is, return value on A1 sampled 4096 times

  int pin = 1;
  float val = 0;
  for (int i = 0; i < 4096; i++){
    val += float(analogRead(pin))/4096.0;
  }
  client.println(val*5.0/1024.0, 5); //multiply by 5/1024 to get volts

}


Get this bounty!!!

#StackBounty: #wifi #realtek #chromium-os #samsung Trying to get wifi working on a Samsung N130 running Chromium OS

Bounty: 50

I have just installed Chromium OS on an old 32bit Samsung N130 netbook.
I used the latest 32bit image (60.0.3112.102) from Arnold the Bat.

Using the lscpi command , I found that it has the Realtek RTL8192E/RTL8192SE Wifi NIC which is listed as supported in the release notes.

When I try to switch the wifi on using the normal settings it just doesn’t go on.

Having looked into this, I found that this chipset had given problems for people with this laptop before in other Linux distributions. I have encountered similar problems in the past trying to get Broadcom WiFi to work when installing Ubuntu or Debian on older Apple hardware and it could be fixed by installing an application to extract the firmware and install it e.g fwcutter

I know that Chromium OS is Gentoo-based and I do not know the best way to proceed to check if the right driver is installed and to make sure that the wifi can be activated. I have read that Gentoo is for more advanced users and I miss apt-get!

When I next get the chance, I will try installing Ubuntu, saving the /lib/firmware folder and then reinstall Chromium and merge the firmware folder with the Ubuntu one. It might work…

Following the advice from Emmanuel Rosa below:
screenshot as copy/paste didn't work


Get this bounty!!!

#StackBounty: #javascript #cordova #ionic-framework #wifi #hotspot Hotspot plugin scanWifi() is not working in Andoid ionic cordova

Bounty: 50

I’m facing an issue while scanning nearest wifi. I’m using ionic Cordova framework.
I have used a scanWifi method of Hotspot plugin to scan wifi list.
I have referred to the following link:
https://ionicframework.com/docs/native/hotspot/

My code is:

import { Hotspot, HotspotNetwork } from '@ionic-native/hotspot';

this.hotspot.scanWifi().then((networks: Array<HotspotNetwork>) => {
   this.availableWifiList = networks;
});

When app trying to scan the nearest wifi it returns an empty array of wifi list. But it’s working on other Android devices.

The issue is reproduce in the following android device only for me.

Micromax:
Model Number: Micromax Q452
Android Version: 7.0
Android Security Patch Level: May 5, 2017

Also, it is working on other Android device having the same Android version.
Any help will be much appreciated.


Get this bounty!!!