Micromet wrote:For my current and future education, could you explain, in general (so that I can follow up on this) exactly what your queries are looking for - and what you found.
Sure, no problem, so let's try to break it down.
- Code: Select all
ps -ef | grep -v grep | grep -iE "net|wpa"
This would show the running processes filtered for network-related processes, allowing to see whether net_applet (the default Mageia network applet) and/or networkmanager are running, and whether one or more wpa_supplicant processes (relevant for wireless encryption) are running or not. Seems you forgot to run that, please add the output for that
- Code: Select all
[root@localhost colin]# lspcidrake -v | grep -iE "wlan|wifi|wireless|net"
r8169 : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1849 subd:8168) (rev: 02)
lspcidrake shows the hardware devices, including their PCI product and vendor IDs to identify which chipset and variant and what driver is currently loaded. And with the grep I try to filter for only network and wireless devices.
lspcidrake is a Mageia-specific wrapper around lspci, so if you want a more generic command working on all distros, lspci -nnk should provide the same information.
Although in your case it only shows the wired network interface, not the wireless. So please add the complete output of
lspcidrake -v so we can see what the wireless adapter shows up as.
- Code: Select all
[root@localhost colin]# ifconfig -a
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.141 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::219:66ff:fe79:dda8 prefixlen 64 scopeid 0x20<link>
ether 00:19:66:79:dd:a8 txqueuelen 1000 (Ethernet)
RX packets 5239 bytes 3188660 (3.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2498 bytes 271051 (264.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Local Loopback)
RX packets 211 bytes 30794 (30.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 211 bytes 30794 (30.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
ifconfig -a shows all currently active network interfaces, and if there are IP adresses assigned to them. In your case there's only enp2s0 which looks like a wired interface, which has IP adress 192.168.1.141 assigned to it. No wireless interface in sight here.
- Code: Select all
[root@localhost colin]# rfkill list all
rfkill should show the rfkill state of all wireless and bluetooth interfaces known to the system, usually there's a softblock and a hardblock. softblock is usually a software switch which disables wireless, often a key combo like Fn+F7 or something like that, and hardblock is usually some hardware switch that disables wireless/bluetooth. As no device is known to the system, rfkill will not output anything.
- Code: Select all
[root@localhost colin]# systemctl status network.service -a
● network.service - LSB: Bring up/down networking
Loaded: loaded (/etc/rc.d/init.d/network)
Active: active (running) since Fri 2016-12-16 10:48:12 GMT; 24min ago
Process: 2358 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/network.service
├─2533 /sbin/ifplugd -I -b -i enp2s0
└─3031 dhclient -1 -q -lf /var/lib/dhclient/dhclient--enp2s0.lease -pf /var/run/dhclient-enp2s0.pid enp2s0
Dec 16 10:48:12 localhost.localdomain network[2358]: Bringing up interface enp2s0: [ OK ]
Dec 16 10:48:12 localhost.localdomain systemd-sysctl[2554]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/51-alt-sysrq.conf'.
Dec 16 10:48:12 localhost.localdomain systemd-sysctl[2554]: Overwriting earlier assignment of net/ipv4/icmp_ignore_bogus_error_responses in file '/etc/sysctl.d/99-sysctl.conf'.
Dec 16 10:48:12 localhost.localdomain systemd-sysctl[2554]: Overwriting earlier assignment of net/ipv4/conf/all/log_martians in file '/etc/sysctl.d/99-sysctl.conf'.
Dec 16 10:48:14 localhost.localdomain ifplugd(enp2s0)[2533]: Link beat detected.
Dec 16 10:48:15 localhost.localdomain ifplugd(enp2s0)[2533]: Executing '/etc/ifplugd/ifplugd.action enp2s0 up'.
Dec 16 10:48:16 localhost.localdomain dhclient[2859]: DHCPREQUEST on enp2s0 to 255.255.255.255 port 67
Dec 16 10:48:16 localhost.localdomain dhclient[2859]: DHCPACK from 192.168.1.1
Dec 16 10:48:16 localhost.localdomain ifplugd(enp2s0)[2533]: client: Determining IP information for enp2s0... done.
Dec 16 10:48:16 localhost.localdomain ifplugd(enp2s0)[2533]: Program executed successfully.
[root@localhost colin]#
This shows the status of the network service, and the last 10 lines of the log from it. We can see that the wired network interface properly received an IP adress from your router, but no wireless interface in sight here.
I've omitted the output from journalctl -ab | grep -iE "fw|firmware|iwl|wifi|wire|80211" as that only shows firewall messages, although nothing about firmware or anything related to wireless, which seems strange to me. FWIW, journalctl -ab queries the log for the current boot.