![]() ![]() The more stable solution would be to use the existing /etc/NetworkManager/conf.d directory and place your custom configuration in there. Even though your package manager may alert you to the conflict - apt usually does - rather play it safe. However, editing the nf file can only be considered a short-term solution as that file might be replaced/updated in a package update. Problem was caused by linux-firmware updateĪ lack of the entry seemed to be the issue for me on Kali 2022 running on a RasPi 4, exactly as suggested by other answers here (so kudos to the answers above!). Then I restarted NetworkManager and problem resolved. Managed=true #Fixed this: This was "false" <<<<<<<<<Īnd I Added the missing plus devices string <<<<<<: Update-initramfs: Generating /boot/initrd.img-5.4.0-65-generic Update-initramfs: Generating /boot/initrd.img-5.4.0-66-generic This was when /var/log/apt showed: Preparing to unpack. Performing sudo apt update caused ethernet to not show in networks widget, but network connections via ethernet continued to work. Last run command: sudo service network-manager restartĪnd all showed correctly in the network manger after a couple hours of fighting! This is for a home server, it may have been caused me configuring the IP during setup, which added values for a static IP in /etc/network/interfaces. Unmanaged-devices=*,except:type:wifi,except:type:wwan,except:type:ethernetĬurrent /etc/NetworkManager/nf This also prevented me from using openvpn via network manager. ![]() A fresh install, to server 17.10 with LXDE had this issue reading all over and trying everything. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |