WLAN device misrecognized as wired Ethernet interface

[afewgoodman]

Hi,

If I can reproduce it in my side, I will further happy.

Did you install iw package also?

BR.

[tchaikovsky8]

If I can reproduce it in my side, I will further happy.

Thank you very much.
Now that we tried in many ways, I suspect that my PC hardware (Toshiba dynabook EX/33J, 2009) is too old to be supported by CentOS 7.

Did you install iw package also?

Yes, iw package is already installed.

# yum list iw
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: ftp.iij.ad.jp
* extras: ftp.iij.ad.jp
* updates: ftp.iij.ad.jp
Installed Packages
iw.x86_64 4.3-2.el7 @anaconda

# yum info iw
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: ftp.iij.ad.jp
* extras: ftp.iij.ad.jp
* updates: ftp.iij.ad.jp
Installed Packages
Name : iw
Arch : x86_64
Version : 4.3
Release : 2.el7
Size : 159 k
Repo : installed
From repo : anaconda
Summary : A nl80211 based wireless configuration tool
URL : http://wireless.kernel.org/en/users/Documentation/iw
License : ISC
Description : iw is a new nl80211 based CLI configuration utility for wireless devices.
: Currently you can only use this utility to configure devices which
: use a mac80211 driver as these are the new drivers being written -
: only because most new wireless devices being sold are now SoftMAC.

[afewgoodman]

Looking into your log again,

It seems to miss ifcfg-enp2s0 in the /etc/sysconfig/network-scripts. Has it been there right?

If not exist, you create it also as you did for wlp3s0.

BR.

[tchaikovsky8]

It seems to miss ifcfg-enp2s0 in the /etc/sysconfig/network-scripts. Has it been there right?
If not exist, you create it also as you did for wlp3s0.

I have deleted /etc/sysconfig/network-scripts/ifcfg-enp2s0 on March 12 as posted at that time.
Now I have recreated the file as shown below.

# nmcli d
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected ???? 1
virbr0 bridge connected virbr0
wlp3s0 ethernet unavailable --
lo loopback unmanaged --
virbr0-nic tun unmanaged --

# nmcli c
NAME UUID TYPE DEVICE
???? 1 e40dc6c6-91d1-37a8-bbef-1138e505affc ethernet enp2s0
virbr0 c204754c-91d2-4aa4-bbb6-1c8d3b460267 bridge virbr0
???? 2 a3c22102-0aa0-3167-8b9f-cb79d6cc38f0 ethernet --

# ls /etc/sysconfig/network-scripts/ifcfg-*
/etc/sysconfig/network-scripts/ifcfg-lo /etc/sysconfig/network-scripts/ifcfg-wlp3s0

# nmcli con add type ethernet con-name enp2s0 ifname enp2s0
Connection 'enp2s0' (79ce2dd5-4692-45c9-be81-8a3299d2ddac) successfully added.

# ls /etc/sysconfig/network-scripts/ifcfg-*
/etc/sysconfig/network-scripts/ifcfg-enp2s0 /etc/sysconfig/network-scripts/ifcfg-lo /etc/sysconfig/network-scripts/ifcfg-wlp3s0

# cat /etc/sysconfig/network-scripts/ifcfg-enp2s0
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp2s0
UUID=79ce2dd5-4692-45c9-be81-8a3299d2ddac
DEVICE=enp2s0
ONBOOT=yes

# systemctl restart NetworkManager

# nmcli d
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
virbr0 bridge connected virbr0
wlp3s0 ethernet unavailable --
lo loopback unmanaged --
virbr0-nic tun unmanaged --

# nmcli c
NAME UUID TYPE DEVICE
enp2s0 ac7b28bf-bd5e-442e-8fc8-9514e97ac072 ethernet enp2s0
virbr0 47d71ab5-26c1-4ae7-b911-de2d768ee32d bridge virbr0
enp2s0 79ce2dd5-4692-45c9-be81-8a3299d2ddac ethernet --
???? 1 cc03886c-ecf8-3b8b-92e8-0b31d1f375a5 ethernet --

# reboot

# ls /etc/sysconfig/network-scripts/ifcfg-*
/etc/sysconfig/network-scripts/ifcfg-enp2s0 /etc/sysconfig/network-scripts/ifcfg-lo /etc/sysconfig/network-scripts/ifcfg-wlp3s0

# nmcli d
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
virbr0 bridge connected virbr0
wlp3s0 ethernet unavailable --
lo loopback unmanaged --
virbr0-nic tun unmanaged --

# nmcli c
NAME UUID TYPE DEVICE
enp2s0 79ce2dd5-4692-45c9-be81-8a3299d2ddac ethernet enp2s0
virbr0 824a4152-fe31-4f8d-9e01-23b2c21df438 bridge virbr0
???? 1 cc03886c-ecf8-3b8b-92e8-0b31d1f375a5 ethernet --

[afewgoodman]

Hi

I found such a string in the /etc/sysconfig/network-scripts/network-functions

140 Wireless)
141 DEVICETYPE="eth"

I don't understand why it is mapped to "eth". I am not sure but, it would be "wireless".

Can you modify it and try again?

BR.

[tchaikovsky8]

I found such a string in the /etc/sysconfig/network-scripts/network-functions

140 Wireless)
141 DEVICETYPE="eth"

I don't understand why it is mapped to "eth". I am not sure but, it would be "wireless".

Can you modify it and try again?

Thank you.
But it made no change.

# vi /etc/sysconfig/network-scripts/network-functions

# cat -n /etc/sysconfig/network-scripts/network-functions
.....
140 Wireless)
141 # DEVICETYPE="eth"
142 DEVICETYPE="wireless"
.....

# reboot

# nmcli d
DEVICE TYPE STATE CONNECTION
enp2s0 ethernet connected enp2s0
virbr0 bridge connected virbr0
wlp3s0 ethernet unavailable --
lo loopback unmanaged --
virbr0-nic tun unmanaged --

[afewgoodman]

Hi,

I am looking into NetworkManager.

I got a conclusion that if make_wireless_security_setting get an error, wireless connection would not created and then, NetworkManager create unhandled connection.

Mar 13 16:16:05 yokohama NetworkManager[895]: <warn> [1584083765.0901] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlp3s0" fails: Invalid WEP key length.

The above error is from make_wep_setting function which is called make_wireless_security_setting and make_wireless_security_setting is called by wireless_connection_from_ifcfg which make connection for wireless.

You can see this procedure as follows.

2 5974 /home/bchoi/work/NetworkManager/src/settings/plugins/ifcfg-rh/nms-ifcfg-rh-reader.c <<<unknown>>>
connection = wireless_connection_from_ifcfg (filename, main_ifcfg, error);

So, I think your WEP key would not correct. If you modify it correctly, you will get correct type as "wireless"

BR.

[tchaikovsky8]

I think your WEP key would not correct. If you modify it correctly, you will get correct type as "wireless"

I checked the key again, but it is correct.

[chemal]

You need to find out what/who decides that your wlan device is an ethernet device. Candidates are kernel/driver, systemd, NetworkManager. I'd start with looking at the output of dmesg.

[afewgoodman]

I think your WEP key would not correct. If you modify it correctly, you will get correct type as "wireless"

I checked the key again, but it is correct.

How about try again without WEP key?

"nmcli con add" command would not function with WEP key, "nmcli device" command handle WEP key.

https://developer.gnome.org/NetworkMana ... nmcli.html

BR.