CentOS

How about try again without WEP key?

Thank you. Still no change.

It can be same result if no WEP or WPA key because finally it return NULL in the NetworkManager.

WEP key would be such format.

(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep
KEY=0123456789abcdef0123456789
(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep-104-ascii
KEY1=s:LoremIpsumSit
(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep-40-ascii
KEY1=s:Lorem
(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep-adhoc
KEY=0123456789abcdef0123456789
(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep-eap-ttls-chap
IEEE_8021X_PASSWORD="foobar baz"

(base) [bchoi@localhost network-scripts]$ cat keys-test-wifi-wep-passphrase
KEY_PASSPHRASE1="foobar222blahblah"
(base) [bchoi@localhost network-scripts]$ pwd
/home/bchoi/work/NetworkManager/src/settings/plugins/ifcfg-rh/tests/network-scripts

Can you show me your KEY value?

I believe the mis-identification of wireless chips as wired is something to do with the kernel module involved. There have been numerous reports of this on the forums in the last few years, usually involving kernel modules that have been self-built. No-one has (yet) worked out what causes it nor how to solve it. It usually seems to be easier and cheaper (if you put a $ value on your time) to just give up and purchase a supported adapter.

It usually seems to be easier and cheaper (if you put a $ value on your time) to just give up and purchase a supported adapter.

Thank you. I agree with your conclusion.

I would like to express my sincere appreciation for the supporters of this thread.