WLAN device misrecognized as wired Ethernet interface

Issues related to configuring your network
User avatar
TrevorH
Forum Moderator
Posts: 29069
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: WLAN device misrecognized as wired Ethernet interface

Post by TrevorH » 2020/03/11 11:54:24

Now watch /var/log/messages while you first remove both modules and then add them back and see what is logged.
CentOS 6 will die in November 2020 - migrate sooner rather than later!
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 is dead, do not use it.
Full time Geek, part time moderator. Use the FAQ Luke

tchaikovsky8
Posts: 23
Joined: 2020/03/09 02:42:43

Re: WLAN device misrecognized as wired Ethernet interface

Post by tchaikovsky8 » 2020/03/11 16:05:02

Now watch /var/log/messages while you first remove both modules and then add them back and see what is logged.
Mar 12 00:59:00 yokohama avahi-daemon[844]: Withdrawing workstation service for enp3s0.
Mar 12 00:59:00 yokohama NetworkManager[893]: <info> [1583942340.7452] device (enp3s0): state change: unavailable -> unmanaged (reason 'removed', sys-iface-state: 'removed')
Mar 12 00:59:00 yokohama ModemManager[781]: <info> (net/enp3s0): released by modem /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0
Mar 12 00:59:00 yokohama kernel: Freeing irq 17
Mar 12 00:59:17 yokohama kernel: perf: interrupt took too long (3152 > 3135), lowering kernel.perf_event_max_sample_rate to 63000
Mar 12 01:00:01 yokohama systemd: Created slice User Slice of root.
Mar 12 01:00:01 yokohama systemd: Started Session 2 of user root.
Mar 12 01:00:02 yokohama systemd: Removed slice User Slice of root.
Mar 12 01:01:01 yokohama systemd: Created slice User Slice of root.
Mar 12 01:01:01 yokohama systemd: Started Session 3 of user root.
Mar 12 01:01:01 yokohama systemd: Removed slice User Slice of root.
Mar 12 01:01:23 yokohama systemd: Stopped Network Manager Wait Online.
Mar 12 01:01:23 yokohama systemd: Stopping Network Manager Wait Online...
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4310] caught SIGTERM, shutting down normally.
Mar 12 01:01:23 yokohama journal: Removing a network device that was not added
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4714] dhcp4 (enp2s0): canceled DHCP transaction, DHCP client pid 1058
Mar 12 01:01:23 yokohama systemd: Stopping Network Manager...
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4715] dhcp4 (enp2s0): state changed bound -> done
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4715] device (enp2s0): DHCPv4: 480 seconds grace period started
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4775] dhcp6 (enp2s0): canceled DHCP transaction
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4775] dhcp6 (enp2s0): state changed terminated -> done
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4775] dhcp6 (enp2s0): canceled DHCP transaction
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.4894] manager: NetworkManager state is now CONNECTED_SITE
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.5093] device (virbr0-nic): released from master device virbr0
Mar 12 01:01:23 yokohama NetworkManager[893]: <info> [1583942483.5469] exiting (success)
Mar 12 01:01:23 yokohama dbus[799]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 12 01:01:23 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 12 01:01:23 yokohama systemd: Stopped Network Manager.
Mar 12 01:01:23 yokohama journal: Removing a network device that was not added
Mar 12 01:01:23 yokohama systemd: Starting Network Manager...
Mar 12 01:01:23 yokohama journal: Removing a network device that was not added
Mar 12 01:01:23 yokohama dbus[799]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Mar 12 01:01:23 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 12 01:01:23 yokohama journal: JS WARNING: [resource:///org/gnome/shell/ui/status/network.js 1999]: reference to undefined property "state"
Mar 12 01:01:23 yokohama NetworkManager[3521]: <info> [1583942483.8191] NetworkManager (version 1.18.0-5.el7_7.2) is starting... (after a restart)
Mar 12 01:01:23 yokohama NetworkManager[3521]: <info> [1583942483.8215] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
Mar 12 01:01:23 yokohama systemd: Started Network Manager.
Mar 12 01:01:23 yokohama systemd: Starting Network Manager Wait Online...
Mar 12 01:01:23 yokohama NetworkManager[3521]: <info> [1583942483.8779] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar 12 01:01:23 yokohama NetworkManager[3521]: <info> [1583942483.8785] manager[0x562129404060]: monitoring kernel firmware directory '/lib/firmware'.
Mar 12 01:01:23 yokohama journal: updated_properties: error reading NMClient properties: パス /org/freedesktop/NetworkManager のオブジェクト上にインターフェース 'org.freedesktop.DBus.Properties' がありません
Mar 12 01:01:23 yokohama dbus[799]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service'
Mar 12 01:01:23 yokohama systemd: Starting Hostname Service...
Mar 12 01:01:24 yokohama dbus[799]: [system] Successfully activated service 'org.freedesktop.hostname1'
Mar 12 01:01:24 yokohama systemd: Started Hostname Service.
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0323] hostname: hostname: using hostnamed
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0324] hostname: hostname changed from (none) to "yokohama"
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0333] dns-mgr[0x5621293e8220]: init: dns=default,systemd-resolved rc-manager=file
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0377] manager[0x562129404060]: rfkill: Wi-Fi hardware radio set enabled
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0377] manager[0x562129404060]: rfkill: WWAN hardware radio set enabled
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0540] settings: Loaded settings plugin: SettingsPluginIfcfg ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ifcfg-rh.so")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0553] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ibft.so")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0564] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0598] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g (8933a33f-b79e-44cd-abb8-443f53840696,"aterm-0238fa-g")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0620] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp3s0 (cc03886c-ecf8-3b8b-92e8-0b31d1f375a5,"enp3s0")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0640] ifcfg-rh: new connection /etc/sysconfig/network-scripts/ifcfg-enp2s0 (3df020e1-33b3-404e-a7c5-2245ff487638,"enp2s0")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0848] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0870] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0910] manager: Networking is enabled by state file
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.0925] dhcp-init: Using DHCP client 'dhclient'
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1000] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-adsl.so)
Mar 12 01:01:24 yokohama nm-dispatcher: req:1 'hostname': new request (4 scripts)
Mar 12 01:01:24 yokohama nm-dispatcher: req:1 'hostname': start running ordered scripts...
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1145] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-team.so)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1191] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wifi.so)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1283] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-bluetooth.so)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1298] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wwan.so)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1340] device (lo): carrier: link connected
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1403] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1603] device (enp2s0): carrier: link connected
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1669] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1858] manager: (enp2s0): assume: will attempt to assume matching connection 'enp2s0' (3df020e1-33b3-404e-a7c5-2245ff487638) (indicated)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.1880] device (enp2s0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2164] device (enp2s0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2323] device (enp2s0): Activation: starting connection 'enp2s0' (3df020e1-33b3-404e-a7c5-2245ff487638)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2395] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/3)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2563] ifcfg-rh: add connection in-memory (4d7a00f8-a600-4db5-8f92-22be5eb2b8bb,"virbr0")
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2712] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2844] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.2984] device (virbr0): Activation: starting connection 'virbr0' (4d7a00f8-a600-4db5-8f92-22be5eb2b8bb)
Mar 12 01:01:24 yokohama nm-dispatcher: req:2 'connectivity-change': new request (4 scripts)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3056] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/4)
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3709] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3801] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3883] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3926] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.3998] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4048] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4193] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4235] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4317] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4820] policy: set 'enp2s0' (enp2s0) as default for IPv4 routing and DNS
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4844] policy: set 'enp2s0' (enp2s0) as default for IPv6 routing and DNS
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.4845] device (virbr0): Activation: successful, device activated.
Mar 12 01:01:24 yokohama nm-dispatcher: req:3 'up' [virbr0]: new request (4 scripts)
Mar 12 01:01:24 yokohama nm-dispatcher: req:3 'up' [virbr0]: start running ordered scripts...
Mar 12 01:01:24 yokohama NetworkManager[3521]: <info> [1583942484.8703] modem-manager: ModemManager available
Mar 12 01:01:25 yokohama systemd: Unit iscsi.service cannot be reloaded because it is inactive.
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.0721] agent-manager: req[0x562129457630, :1.72/org.gnome.Shell.NetworkAgent/1000]: agent registered
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.0818] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.0867] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.1148] dhcp4 (enp2s0): dhclient started with pid 3587
Mar 12 01:01:25 yokohama dhclient[3587]: DHCPREQUEST on enp2s0 to 255.255.255.255 port 67 (xid=0x5746d585)
Mar 12 01:01:25 yokohama dhclient[3587]: DHCPACK from 192.168.0.1 (xid=0x5746d585)
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2931] dhcp4 (enp2s0): address 192.168.0.5
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2935] dhcp4 (enp2s0): plen 24 (255.255.255.0)
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2935] dhcp4 (enp2s0): gateway 192.168.0.1
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2935] dhcp4 (enp2s0): lease time 3600
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2936] dhcp4 (enp2s0): nameserver '192.168.0.1'
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.2936] dhcp4 (enp2s0): state changed unknown -> bound
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.3188] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:25 yokohama dhclient[3587]: bound to 192.168.0.5 -- renewal in 1405 seconds.
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.3359] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.3420] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.3545] manager: NetworkManager state is now CONNECTED_SITE
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.4717] device (enp2s0): Activation: successful, device activated.
Mar 12 01:01:25 yokohama dnsmasq[1573]: reading /etc/resolv.conf
Mar 12 01:01:25 yokohama dnsmasq[1573]: using nameserver 192.168.0.1#53
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.4850] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 12 01:01:25 yokohama nm-dispatcher: req:4 'up' [enp2s0]: new request (4 scripts)
Mar 12 01:01:25 yokohama nm-dispatcher: req:4 'up' [enp2s0]: start running ordered scripts...
Mar 12 01:01:25 yokohama NetworkManager[3521]: <info> [1583942485.5063] manager: startup complete
Mar 12 01:01:25 yokohama nm-dispatcher: req:5 'connectivity-change': new request (4 scripts)
Mar 12 01:01:25 yokohama systemd: Started Network Manager Wait Online.
Mar 12 01:01:25 yokohama systemd: Unit iscsi.service cannot be reloaded because it is inactive.
Mar 12 01:01:25 yokohama nm-dispatcher: req:5 'connectivity-change': start running ordered scripts...
Mar 12 01:01:26 yokohama NetworkManager[3521]: <info> [1583942486.8318] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 12 01:01:26 yokohama NetworkManager[3521]: <info> [1583942486.8420] dhcp6 (enp2s0): dhclient started with pid 3739
Mar 12 01:01:27 yokohama dhclient[3739]: XMT: Info-Request on enp2s0, interval 1030ms.
Mar 12 01:01:27 yokohama dhclient[3739]: RCV: Reply message on enp2s0 from fe80::fab7:97ff:fe2a:8910.
Mar 12 01:01:27 yokohama NetworkManager[3521]: <info> [1583942487.0785] dhcp6 (enp2s0): nameserver '2001:268:fd07:4::1'
Mar 12 01:01:27 yokohama NetworkManager[3521]: <info> [1583942487.0786] dhcp6 (enp2s0): nameserver '2001:268:fd08:4::1'
Mar 12 01:01:27 yokohama NetworkManager[3521]: <info> [1583942487.0786] dhcp6 (enp2s0): state changed unknown -> bound
Mar 12 01:01:27 yokohama dnsmasq[1573]: reading /etc/resolv.conf
Mar 12 01:01:27 yokohama dnsmasq[1573]: using nameserver 2001:268:fd07:4::1#53
Mar 12 01:01:27 yokohama dnsmasq[1573]: using nameserver 2001:268:fd08:4::1#53
Mar 12 01:01:27 yokohama dnsmasq[1573]: using nameserver 192.168.0.1#53
Mar 12 01:01:27 yokohama nm-dispatcher: req:6 'dhcp6-change' [enp2s0]: new request (4 scripts)
Mar 12 01:01:27 yokohama nm-dispatcher: req:6 'dhcp6-change' [enp2s0]: start running ordered scripts...
Mar 12 01:01:27 yokohama NetworkManager[3521]: <info> [1583942487.1393] dhcp6 (enp2s0): client pid 3739 exited with status 0
Mar 12 01:01:27 yokohama NetworkManager[3521]: <info> [1583942487.1394] dhcp6 (enp2s0): state changed bound -> terminated

chemal
Posts: 682
Joined: 2013/12/08 19:44:49

Re: WLAN device misrecognized as wired Ethernet interface

Post by chemal » 2020/03/11 18:52:14

These files should be checked or probably simply removed:

/etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g
/etc/sysconfig/network-scripts/ifcfg-enp2s0
/etc/sysconfig/network-scripts/ifcfg-enp3s0

tchaikovsky8
Posts: 23
Joined: 2020/03/09 02:42:43

Re: WLAN device misrecognized as wired Ethernet interface

Post by tchaikovsky8 » 2020/03/12 01:49:12

These files should be checked or probably simply removed:

/etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g
/etc/sysconfig/network-scripts/ifcfg-enp2s0
/etc/sysconfig/network-scripts/ifcfg-enp3s0
Same result. No wifi device is detected.

# ls /etc/sysconfig/network-scripts/ifcfg-*
/etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g /etc/sysconfig/network-scripts/ifcfg-enp3s0
/etc/sysconfig/network-scripts/ifcfg-enp2s0 /etc/sysconfig/network-scripts/ifcfg-lo

# cat /etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g
HWADDR=00:22:5F:86:2F:CA
ESSID=aterm-0238fa-g
MODE=Managed
MAC_ADDRESS_RANDOMIZATION=default
TYPE=Wireless
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=aterm-0238fa-g
UUID=8933a33f-b79e-44cd-abb8-443f53840696
ONBOOT=yes

# 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=3df020e1-33b3-404e-a7c5-2245ff487638
DEVICE=enp2s0
ONBOOT=yes

# cat /etc/sysconfig/network-scripts/ifcfg-enp3s0
HWADDR=00:22:5F:86:2F:CA
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_PRIVACY=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp3s0
UUID=cc03886c-ecf8-3b8b-92e8-0b31d1f375a5
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999

# mv /etc/sysconfig/network-scripts/ifcfg-aterm-0238fa-g /root/network-scripts/

# mv /etc/sysconfig/network-scripts/ifcfg-enp2s0 /root/network-scripts/

# mv /etc/sysconfig/network-scripts/ifcfg-enp3s0 /root/network-scripts/

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

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

# systemctl restart NetworkManager

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

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

# reboot

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

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

# nmcli d show enp3s0
GENERAL.DEVICE: enp3s0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 00:22:5F:86:2F:CA
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: off

afewgoodman
Posts: 94
Joined: 2019/12/11 03:51:58

Re: WLAN device misrecognized as wired Ethernet interface

Post by afewgoodman » 2020/03/12 03:54:25

Hi,

You may create ifcfg file for wifi and reboot to check if it bring up.

/etc/sysconfig/network-scripts/ifcfg-wlan0
# sudo nmcli con add type wifi con-name wlan0 ifname wlan0 ssid $yourssid
DEVICE=wlan0
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR="yourmacaddress"
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
TYPE=Wireless
USERCTL=no
NETWORKING_IPV6=no
PEERDNS=yes
ESSID= "yourssdid"
CHANNEL=1
MODE=Managed
RATE=Auto
KEY="your128bithexkey"

BR.

tchaikovsky8
Posts: 23
Joined: 2020/03/09 02:42:43

Re: WLAN device misrecognized as wired Ethernet interface

Post by tchaikovsky8 » 2020/03/12 07:59:24

You may create ifcfg file for wifi and reboot to check if it bring up.

/etc/sysconfig/network-scripts/ifcfg-wlan0
Device "enp3s0" changed to "wlan0", but its TYPE is still "ethernet".

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

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

# nmcli con add type wifi con-name wlan0 ifname wlan0 ssid aterm-0238fa-g
Connection 'wlan0' (9607e707-2f32-4268-ae6a-b3dd2115da56) successfully added.

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

# vi /etc/sysconfig/network-scripts/ifcfg-wlan0

# cat /etc/sysconfig/network-scripts/ifcfg-wlan0
DEVICE=wlan0
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=00:22:5F:86:2F:CA
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
TYPE=Wireless
USERCTL=no
NETWORKING_IPV6=no
PEERDNS=yes
ESSID=aterm-0238fa-g
CHANNEL=1
MODE=Managed
RATE=Auto
KEY=9607e707-2f32-4268-ae6a-b3dd2115da56

# reboot

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

# nmcli d show wlan0
GENERAL.DEVICE: wlan0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 00:22:5F:86:2F:CA
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: off

# nmcli c
NAME UUID TYPE DEVICE
???? 1 e40dc6c6-91d1-37a8-bbef-1138e505affc ethernet enp2s0
virbr0 8e5eafe3-8b6a-449d-a849-e1aa70fd592c bridge virbr0
???? 2 a3c22102-0aa0-3167-8b9f-cb79d6cc38f0 ethernet --

afewgoodman
Posts: 94
Joined: 2019/12/11 03:51:58

Re: WLAN device misrecognized as wired Ethernet interface

Post by afewgoodman » 2020/03/13 06:09:26

Hi,

Can you remove ifcfg-wlan0 and regenerate it as suffix name "wlp3s0" and try again ?
And Can you capture "lspci -nn" for Ethernet controller?

Can you show logs Network Manager and detection wifi in /var/log/messages again?

BR.

tchaikovsky8
Posts: 23
Joined: 2020/03/09 02:42:43

Re: WLAN device misrecognized as wired Ethernet interface

Post by tchaikovsky8 » 2020/03/13 07:40:20

Can you remove ifcfg-wlan0 and regenerate it as suffix name "wlp3s0" and try again ?
And Can you capture "lspci -nn" for Ethernet controller?

Can you show logs Network Manager and detection wifi in /var/log/messages again?
Device "wlp3s0" was created, but its TYPE is "ethernet".

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

# nmcli c
NAME UUID TYPE DEVICE
???? 1 e40dc6c6-91d1-37a8-bbef-1138e505affc ethernet enp2s0
virbr0 4a24e9e9-0622-4e91-b1a8-0d053d381849 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-wlan0

# rm /etc/sysconfig/network-scripts/ifcfg-wlan0
rm: remove regular file '/etc/sysconfig/network-scripts/ifcfg-wlan0'? y

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

# nmcli con add type wifi con-name wlp3s0 ifname wlp3s0 ssid aterm-0238fa-g
Connection 'wlp3s0' (5d39f219-d075-41ff-8672-a73fb9da2d2e) successfully added.

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

# vi /etc/sysconfig/network-scripts/ifcfg-wlp3s0

# cat /etc/sysconfig/network-scripts/ifcfg-wlp3s0
DEVICE=wlp3s0
ONBOOT=yes
BOOTPROTO=dhcp
HWADDR=00:22:5F:86:2F:CA
NETMASK=
DHCP_HOSTNAME=
IPADDR=
DOMAIN=
TYPE=Wireless
USERCTL=no
NETWORKING_IPV6=no
PEERDNS=yes
ESSID=aterm-0238fa-g
CHANNEL=1
MODE=Managed
RATE=Auto
KEY=*************

# reboot

# 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 d show wlp3s0
GENERAL.DEVICE: wlp3s0
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 00:22:5F:86:2F:CA
GENERAL.MTU: 1500
GENERAL.STATE: 20 (unavailable)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: off

# nmcli c
NAME UUID TYPE DEVICE
???? 1 e40dc6c6-91d1-37a8-bbef-1138e505affc ethernet enp2s0
virbr0 93cc3bc6-da8e-4ad8-b291-e15cf20c6468 bridge virbr0
???? 2 a3c22102-0aa0-3167-8b9f-cb79d6cc38f0 ethernet --




# grep 'Mar 13' /var/log/messages | grep -e 'Network Manager' -e 'NetworkManager' -e 'nm-'
Mar 13 15:35:32 yokohama systemd: Starting Network Manager...
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.0528] NetworkManager (version 1.18.0-5.el7_7.2) is starting... (for the first time)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.0558] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
Mar 13 15:35:33 yokohama systemd: Started Network Manager.
Mar 13 15:35:33 yokohama systemd: Starting Network Manager Wait Online...
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.1093] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.1128] manager[0x56029724a0a0]: monitoring kernel firmware directory '/lib/firmware'.
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.2920] hostname: hostname: using hostnamed
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.2921] hostname: hostname changed from (none) to "yokohama"
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.2942] dns-mgr[0x560297230220]: init: dns=default,systemd-resolved rc-manager=file
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.2954] manager[0x56029724a0a0]: rfkill: Wi-Fi hardware radio set enabled
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.2955] manager[0x56029724a0a0]: rfkill: WWAN hardware radio set enabled
Mar 13 15:35:33 yokohama dbus[795]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 13 15:35:33 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 13 15:35:33 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.3915] settings: Loaded settings plugin: SettingsPluginIfcfg ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ifcfg-rh.so")
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4018] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ibft.so")
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4019] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Mar 13 15:35:33 yokohama NetworkManager[900]: <warn> [1584081333.4099] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlan0" fails: Invalid WEP key length.
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4805] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4824] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4840] manager: Networking is enabled by state file
Mar 13 15:35:33 yokohama nm-dispatcher: req:1 'hostname': new request (4 scripts)
Mar 13 15:35:33 yokohama nm-dispatcher: req:1 'hostname': start running ordered scripts...
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.4930] dhcp-init: Using DHCP client 'dhclient'
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.5240] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-adsl.so)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.5817] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-team.so)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.5923] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wifi.so)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6158] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-bluetooth.so)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6190] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wwan.so)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6238] device (lo): carrier: link connected
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6306] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6439] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6645] ifcfg-rh: add connection in-memory (e40dc6c6-91d1-37a8-bbef-1138e505affc,"有線接続 1")
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6826] settings: (enp2s0): created default wired connection '有線接続 1'
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.6878] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 13 15:35:33 yokohama nm-dispatcher: req:2 'connectivity-change': new request (4 scripts)
Mar 13 15:35:33 yokohama nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.7894] manager: (wlan0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.8013] ifcfg-rh: add connection in-memory (a3c22102-0aa0-3167-8b9f-cb79d6cc38f0,"有線接続 2")
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.8087] settings: (wlan0): created default wired connection '有線接続 2'
Mar 13 15:35:33 yokohama NetworkManager[900]: <info> [1584081333.8178] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 13 15:35:34 yokohama NetworkManager[900]: <info> [1584081334.9672] modem-manager: ModemManager available
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.2921] device (enp2s0): carrier: link connected
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.2926] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.3016] policy: auto-activating connection '有線接続 1' (e40dc6c6-91d1-37a8-bbef-1138e505affc)
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.3367] device (enp2s0): Activation: starting connection '有線接続 1' (e40dc6c6-91d1-37a8-bbef-1138e505affc)
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.3369] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.3375] manager: NetworkManager state is now CONNECTING
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.3378] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.4586] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.4598] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 13 15:35:36 yokohama NetworkManager[900]: <info> [1584081336.4994] dhcp4 (enp2s0): dhclient started with pid 1058
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2147] dhcp4 (enp2s0): address 192.168.0.5
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2147] dhcp4 (enp2s0): plen 24 (255.255.255.0)
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2148] dhcp4 (enp2s0): gateway 192.168.0.1
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2148] dhcp4 (enp2s0): lease time 3600
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2148] dhcp4 (enp2s0): nameserver '192.168.0.1'
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2148] dhcp4 (enp2s0): state changed unknown -> bound
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2239] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2332] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2368] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.2438] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.3079] manager: NetworkManager state is now CONNECTED_SITE
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.3101] policy: set '有線接続 1' (enp2s0) as default for IPv4 routing and DNS
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.3262] device (enp2s0): Activation: successful, device activated.
Mar 13 15:35:37 yokohama nm-dispatcher: req:3 'up' [enp2s0]: new request (4 scripts)
Mar 13 15:35:37 yokohama nm-dispatcher: req:3 'up' [enp2s0]: start running ordered scripts...
Mar 13 15:35:37 yokohama NetworkManager[900]: <info> [1584081337.3335] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 13 15:35:37 yokohama nm-dispatcher: req:4 'connectivity-change': new request (4 scripts)
Mar 13 15:35:37 yokohama nm-dispatcher: req:4 'connectivity-change': start running ordered scripts...
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.4438] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.4480] dhcp6 (enp2s0): dhclient started with pid 1098
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.4541] policy: set '有線接続 1' (enp2s0) as default for IPv6 routing and DNS
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.5073] dhcp6 (enp2s0): nameserver '2001:268:fd07:4::1'
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.5074] dhcp6 (enp2s0): nameserver '2001:268:fd08:4::1'
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.5074] dhcp6 (enp2s0): state changed unknown -> bound
Mar 13 15:35:38 yokohama nm-dispatcher: req:5 'dhcp6-change' [enp2s0]: new request (4 scripts)
Mar 13 15:35:38 yokohama nm-dispatcher: req:5 'dhcp6-change' [enp2s0]: start running ordered scripts...
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.5530] dhcp6 (enp2s0): client pid 1098 exited with status 0
Mar 13 15:35:38 yokohama NetworkManager[900]: <info> [1584081338.5531] dhcp6 (enp2s0): state changed bound -> terminated
Mar 13 15:35:40 yokohama NetworkManager[900]: <info> [1584081340.8274] manager: startup complete
Mar 13 15:35:40 yokohama systemd: Started Network Manager Wait Online.
Mar 13 15:35:41 yokohama NetworkManager[900]: <warn> [1584081341.1097] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlan0" fails: Invalid WEP key length.
Mar 13 15:35:41 yokohama NetworkManager[900]: <warn> [1584081341.4411] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlan0" fails: Invalid WEP key length.
Mar 13 15:35:41 yokohama NetworkManager[900]: <warn> [1584081341.4944] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlan0" fails: Invalid WEP key length.
Mar 13 15:35:49 yokohama NetworkManager[900]: <info> [1584081349.1421] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
Mar 13 15:35:49 yokohama NetworkManager[900]: <info> [1584081349.2469] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5)
Mar 13 15:35:49 yokohama NetworkManager[900]: <info> [1584081349.3127] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 15:35:49 yokohama NetworkManager[900]: <info> [1584081349.3271] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.0551] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1036] ifcfg-rh: add connection in-memory (4a24e9e9-0622-4e91-b1a8-0d053d381849,"virbr0")
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1187] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1399] device (virbr0): Activation: starting connection 'virbr0' (4a24e9e9-0622-4e91-b1a8-0d053d381849)
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1457] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1535] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1775] keyfile: add connection /var/run/NetworkManager/system-connections/virbr0-nic.nmconnection (6f006713-8449-474a-9d10-c386bae945f7,"virbr0-nic")
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1893] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (6f006713-8449-474a-9d10-c386bae945f7)
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.1937] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2025] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2219] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2300] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2326] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2404] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2455] device (virbr0): bridge port virbr0-nic was attached
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2463] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2543] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.2674] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.3138] device (virbr0): Activation: successful, device activated.
Mar 13 15:35:50 yokohama dbus[795]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.3239] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.3250] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.3694] device (virbr0-nic): Activation: successful, device activated.
Mar 13 15:35:50 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 13 15:35:50 yokohama nm-dispatcher: req:1 'up' [virbr0]: new request (4 scripts)
Mar 13 15:35:50 yokohama nm-dispatcher: req:1 'up' [virbr0]: start running ordered scripts...
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.5524] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.5714] device (virbr0): bridge port virbr0-nic was detached
Mar 13 15:35:50 yokohama NetworkManager[900]: <info> [1584081350.5715] device (virbr0-nic): released from master device virbr0
Mar 13 15:35:50 yokohama nm-dispatcher: req:2 'up' [virbr0-nic]: new request (4 scripts)
Mar 13 15:35:50 yokohama nm-dispatcher: req:3 'down' [virbr0-nic]: new request (4 scripts)
Mar 13 15:35:51 yokohama nm-dispatcher: req:2 'up' [virbr0-nic]: start running ordered scripts...
Mar 13 15:35:51 yokohama nm-dispatcher: req:3 'down' [virbr0-nic]: start running ordered scripts...
Mar 13 15:44:32 yokohama NetworkManager[900]: <info> [1584081872.8639] agent-manager: req[0x5602972c2060, :1.69/org.gnome.Shell.NetworkAgent/1000]: agent registered
Mar 13 15:58:43 yokohama NetworkManager[900]: <info> [1584082723.8551] ifcfg-rh: add connection /etc/sysconfig/network-scripts/ifcfg-wlp3s0 (5d39f219-d075-41ff-8672-a73fb9da2d2e,"wlp3s0")
Mar 13 15:58:43 yokohama NetworkManager[900]: <info> [1584082723.8675] audit: op="connection-add" uuid="5d39f219-d075-41ff-8672-a73fb9da2d2e" name="wlp3s0" pid=3881 uid=0 result="success"
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7496] dhcp4 (enp2s0): address 192.168.0.5
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7524] dhcp4 (enp2s0): plen 24 (255.255.255.0)
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7525] dhcp4 (enp2s0): gateway 192.168.0.1
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7525] dhcp4 (enp2s0): lease time 3600
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7525] dhcp4 (enp2s0): nameserver '192.168.0.1'
Mar 13 16:04:22 yokohama NetworkManager[900]: <info> [1584083062.7526] dhcp4 (enp2s0): state changed bound -> bound
Mar 13 16:04:22 yokohama dbus[795]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 13 16:04:22 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 13 16:04:22 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 13 16:04:22 yokohama nm-dispatcher: req:1 'dhcp4-change' [enp2s0]: new request (4 scripts)
Mar 13 16:04:22 yokohama nm-dispatcher: req:1 'dhcp4-change' [enp2s0]: start running ordered scripts...
Mar 13 16:16:03 yokohama systemd: Starting Network Manager...
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.3225] NetworkManager (version 1.18.0-5.el7_7.2) is starting... (for the first time)
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.3291] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 10-slaves-order.conf)
Mar 13 16:16:04 yokohama systemd: Started Network Manager.
Mar 13 16:16:04 yokohama systemd: Starting Network Manager Wait Online...
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.5001] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.5161] manager[0x5593cb600020]: monitoring kernel firmware directory '/lib/firmware'.
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.7872] hostname: hostname: using hostnamed
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.7872] hostname: hostname changed from (none) to "yokohama"
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.7896] dns-mgr[0x5593cb5e5220]: init: dns=default,systemd-resolved rc-manager=file
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.7927] manager[0x5593cb600020]: rfkill: Wi-Fi hardware radio set enabled
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.7934] manager[0x5593cb600020]: rfkill: WWAN hardware radio set enabled
Mar 13 16:16:04 yokohama dbus[792]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 13 16:16:04 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 13 16:16:04 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 13 16:16:04 yokohama NetworkManager[895]: <info> [1584083764.9167] settings: Loaded settings plugin: SettingsPluginIfcfg ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ifcfg-rh.so")
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.0716] settings: Loaded settings plugin: NMSIbftPlugin ("/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-settings-plugin-ibft.so")
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.0722] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
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.
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.8850] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.8870] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.8887] manager: Networking is enabled by state file
Mar 13 16:16:05 yokohama nm-dispatcher: req:1 'hostname': new request (4 scripts)
Mar 13 16:16:05 yokohama nm-dispatcher: req:1 'hostname': start running ordered scripts...
Mar 13 16:16:05 yokohama NetworkManager[895]: <info> [1584083765.9190] dhcp-init: Using DHCP client 'dhclient'
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.4721] Loaded device plugin: NMAtmManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-adsl.so)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.7065] Loaded device plugin: NMTeamFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-team.so)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.7187] Loaded device plugin: NMWifiFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wifi.so)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.7422] Loaded device plugin: NMBluezManager (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-bluetooth.so)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.7438] Loaded device plugin: NMWwanFactory (/usr/lib64/NetworkManager/1.18.0-5.el7_7.2/libnm-device-plugin-wwan.so)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.8639] device (lo): carrier: link connected
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.8661] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar 13 16:16:06 yokohama NetworkManager[895]: <info> [1584083766.8733] manager: (enp2s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.0919] ifcfg-rh: add connection in-memory (e40dc6c6-91d1-37a8-bbef-1138e505affc,"有線接続 1")
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.1780] settings: (enp2s0): created default wired connection '有線接続 1'
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.1826] device (enp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 13 16:16:07 yokohama nm-dispatcher: req:2 'connectivity-change': new request (4 scripts)
Mar 13 16:16:07 yokohama nm-dispatcher: req:2 'connectivity-change': start running ordered scripts...
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.2813] manager: (wlp3s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/3)
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.2903] ifcfg-rh: add connection in-memory (a3c22102-0aa0-3167-8b9f-cb79d6cc38f0,"有線接続 2")
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.2950] settings: (wlp3s0): created default wired connection '有線接続 2'
Mar 13 16:16:07 yokohama NetworkManager[895]: <info> [1584083767.3002] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Mar 13 16:16:08 yokohama NetworkManager[895]: <info> [1584083768.5451] modem-manager: ModemManager available
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5390] device (enp2s0): carrier: link connected
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5394] device (enp2s0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5475] policy: auto-activating connection '有線接続 1' (e40dc6c6-91d1-37a8-bbef-1138e505affc)
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5878] device (enp2s0): Activation: starting connection '有線接続 1' (e40dc6c6-91d1-37a8-bbef-1138e505affc)
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5895] device (enp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5952] manager: NetworkManager state is now CONNECTING
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.5985] device (enp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.6681] device (enp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.6696] dhcp4 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.7138] dhcp4 (enp2s0): dhclient started with pid 1060
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9093] dhcp4 (enp2s0): address 192.168.0.5
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9094] dhcp4 (enp2s0): plen 24 (255.255.255.0)
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9094] dhcp4 (enp2s0): gateway 192.168.0.1
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9095] dhcp4 (enp2s0): lease time 3600
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9095] dhcp4 (enp2s0): nameserver '192.168.0.1'
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9095] dhcp4 (enp2s0): state changed unknown -> bound
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9195] device (enp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9293] device (enp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9327] device (enp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9399] manager: NetworkManager state is now CONNECTED_LOCAL
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9833] manager: NetworkManager state is now CONNECTED_SITE
Mar 13 16:16:09 yokohama NetworkManager[895]: <info> [1584083769.9854] policy: set '有線接続 1' (enp2s0) as default for IPv4 routing and DNS
Mar 13 16:16:10 yokohama NetworkManager[895]: <info> [1584083770.0122] device (enp2s0): Activation: successful, device activated.
Mar 13 16:16:10 yokohama nm-dispatcher: req:3 'up' [enp2s0]: new request (4 scripts)
Mar 13 16:16:10 yokohama nm-dispatcher: req:3 'up' [enp2s0]: start running ordered scripts...
Mar 13 16:16:10 yokohama NetworkManager[895]: <info> [1584083770.0195] manager: NetworkManager state is now CONNECTED_GLOBAL
Mar 13 16:16:10 yokohama nm-dispatcher: req:4 'connectivity-change': new request (4 scripts)
Mar 13 16:16:10 yokohama nm-dispatcher: req:4 'connectivity-change': start running ordered scripts...
Mar 13 16:16:11 yokohama NetworkManager[895]: <info> [1584083771.6370] dhcp6 (enp2s0): activation: beginning transaction (timeout in 45 seconds)
Mar 13 16:16:11 yokohama NetworkManager[895]: <info> [1584083771.6400] dhcp6 (enp2s0): dhclient started with pid 1100
Mar 13 16:16:11 yokohama NetworkManager[895]: <info> [1584083771.6473] policy: set '有線接続 1' (enp2s0) as default for IPv6 routing and DNS
Mar 13 16:16:12 yokohama NetworkManager[895]: <info> [1584083772.4068] dhcp6 (enp2s0): nameserver '2001:268:fd07:4::1'
Mar 13 16:16:12 yokohama NetworkManager[895]: <info> [1584083772.4069] dhcp6 (enp2s0): nameserver '2001:268:fd08:4::1'
Mar 13 16:16:12 yokohama NetworkManager[895]: <info> [1584083772.4069] dhcp6 (enp2s0): state changed unknown -> bound
Mar 13 16:16:12 yokohama nm-dispatcher: req:5 'dhcp6-change' [enp2s0]: new request (4 scripts)
Mar 13 16:16:12 yokohama nm-dispatcher: req:5 'dhcp6-change' [enp2s0]: start running ordered scripts...
Mar 13 16:16:12 yokohama NetworkManager[895]: <info> [1584083772.4620] dhcp6 (enp2s0): client pid 1100 exited with status 0
Mar 13 16:16:12 yokohama NetworkManager[895]: <info> [1584083772.4621] dhcp6 (enp2s0): state changed bound -> terminated
Mar 13 16:16:14 yokohama NetworkManager[895]: <info> [1584083774.4127] manager: startup complete
Mar 13 16:16:14 yokohama systemd: Started Network Manager Wait Online.
Mar 13 16:16:14 yokohama NetworkManager[895]: <warn> [1584083774.6866] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlp3s0" fails: Invalid WEP key length.
Mar 13 16:16:15 yokohama NetworkManager[895]: <warn> [1584083775.0245] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlp3s0" fails: Invalid WEP key length.
Mar 13 16:16:15 yokohama NetworkManager[895]: <warn> [1584083775.0778] ifcfg-rh: loading "/etc/sysconfig/network-scripts/ifcfg-wlp3s0" fails: Invalid WEP key length.
Mar 13 16:16:22 yokohama NetworkManager[895]: <info> [1584083782.7506] manager: (virbr0): new Bridge device (/org/freedesktop/NetworkManager/Devices/4)
Mar 13 16:16:22 yokohama NetworkManager[895]: <info> [1584083782.8618] manager: (virbr0-nic): new Tun device (/org/freedesktop/NetworkManager/Devices/5)
Mar 13 16:16:22 yokohama NetworkManager[895]: <info> [1584083782.9261] device (virbr0-nic): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 16:16:22 yokohama NetworkManager[895]: <info> [1584083782.9452] device (virbr0-nic): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.7501] device (virbr0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8001] ifcfg-rh: add connection in-memory (93cc3bc6-da8e-4ad8-b291-e15cf20c6468,"virbr0")
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8202] device (virbr0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8438] device (virbr0): Activation: starting connection 'virbr0' (93cc3bc6-da8e-4ad8-b291-e15cf20c6468)
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8484] device (virbr0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8591] device (virbr0): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8772] keyfile: add connection /var/run/NetworkManager/system-connections/virbr0-nic.nmconnection (6808ef05-17fc-4b87-ab5f-a9fa0b8fba37,"virbr0-nic")
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.8968] device (virbr0-nic): Activation: starting connection 'virbr0-nic' (6808ef05-17fc-4b87-ab5f-a9fa0b8fba37)
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9006] device (virbr0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9094] device (virbr0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9314] device (virbr0-nic): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9435] device (virbr0-nic): state change: prepare -> config (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9489] device (virbr0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9576] device (virbr0-nic): state change: config -> ip-config (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9615] device (virbr0): bridge port virbr0-nic was attached
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9626] device (virbr0-nic): Activation: connection 'virbr0-nic' enslaved, continuing activation
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9685] device (virbr0-nic): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:23 yokohama NetworkManager[895]: <info> [1584083783.9865] device (virbr0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.0559] device (virbr0): Activation: successful, device activated.
Mar 13 16:16:24 yokohama dbus[792]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.0650] device (virbr0-nic): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.0662] device (virbr0-nic): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external')
Mar 13 16:16:24 yokohama systemd: Starting Network Manager Script Dispatcher Service...
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.2006] device (virbr0-nic): Activation: successful, device activated.
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.2553] device (virbr0-nic): state change: activated -> unmanaged (reason 'connection-assumed', sys-iface-state: 'external')
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.2771] device (virbr0): bridge port virbr0-nic was detached
Mar 13 16:16:24 yokohama NetworkManager[895]: <info> [1584083784.2771] device (virbr0-nic): released from master device virbr0
Mar 13 16:16:24 yokohama nm-dispatcher: req:1 'up' [virbr0]: new request (4 scripts)
Mar 13 16:16:24 yokohama systemd: Started Network Manager Script Dispatcher Service.
Mar 13 16:16:24 yokohama nm-dispatcher: req:1 'up' [virbr0]: start running ordered scripts...
Mar 13 16:16:24 yokohama nm-dispatcher: req:2 'up' [virbr0-nic]: new request (4 scripts)
Mar 13 16:16:24 yokohama nm-dispatcher: req:3 'down' [virbr0-nic]: new request (4 scripts)
Mar 13 16:16:24 yokohama nm-dispatcher: req:2 'up' [virbr0-nic]: start running ordered scripts...
Mar 13 16:16:25 yokohama nm-dispatcher: req:3 'down' [virbr0-nic]: start running ordered scripts...
Mar 13 16:16:59 yokohama NetworkManager[895]: <info> [1584083819.5441] agent-manager: req[0x5593cb66f4a0, :1.67/org.gnome.Shell.NetworkAgent/1000]: agent registered

afewgoodman
Posts: 94
Joined: 2019/12/11 03:51:58

Re: WLAN device misrecognized as wired Ethernet interface

Post by afewgoodman » 2020/03/13 08:57:51

Can you lspci -nn for your Ethernet card?

tchaikovsky8
Posts: 23
Joined: 2020/03/09 02:42:43

Re: WLAN device misrecognized as wired Ethernet interface

Post by tchaikovsky8 » 2020/03/13 09:58:20

Can you lspci -nn for your Ethernet card?
I am sorry for forgetting it.

# lspci -nn
.....
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL810xE PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8192E/RTL8192SE Wireless LAN Controller [10ec:8192] (rev 01)



# lspci -vv
.....
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192E/RTL8192SE Wireless LAN Controller (rev 01)
Subsystem: Realtek Semiconductor Co., Ltd. Device 8151
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 3000
Region 1: Memory at 98a00000 (32-bit, non-prefetchable)
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <128ns, L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=01
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number ca-2f-86-fe-ff-5f-22-00
Kernel driver in use: rtl819xE
Kernel modules: rtl8192se, r8192e_pc

Post Reply

Return to “CentOS 7 - Networking Support”