3 ms·
I had a similar experience back when I switched to Arch. For some reason, the default at the time for network configuration was netctl. Coming from a world whe
by crabbone 2y ago
I had a similar experience back when I switched to Arch. For some reason, the default at the time for network configuration was netctl. Coming from a world where default = old, true and tried, I assumed that newtorkctl is going to be just that.
Fast-forward few years: I learned that no matter the Linux distro, true and tried is NetworkManager. It has various flaws, which is why there are plenty of complementary / alternative management solutions, but they usually come with more flaws than what they purport to replace / complement.
Also, it's worth learning several commands from nmcli family. Especially, when it comes to wifi:
nmcli d wifi list
nmcli d wifi connect $SSID password $PASSWORD
This will cover most of what you need when connecting to WiFi with your laptop wherever you need most of the time.
- freedomben 2y ago> I assumed that newtorkctl is going to be just that. My morning brain read that like "new torque sea tee ell" and didn't realize there was a typo. It was incredibly confused for several long seconds thinking that one through. Finally after being unable to understand it, I noticed it was a typo.
- crabbone 2y agoYeah :) It's actually netctl. I haven't used it for so long, I forgot what it's called.
- jasonjayr 2y agoNetwork Manager also has 'mntui' -- which is a simple text ui for configuring Wifi. As a systems guy, on Debian, the workflow that works for me is to have wired interfaces defined as 'manual' in /etc/network/interfaces, so NetworkManager skips them, and I can configure them using the typical linux tooling and leave wifi managed by NetworkManager, so it can easily manage the dance between WPA/DHCP/AP association.
- jasonjayr 2y agoPast the edit deadline, that should be 'nmtui'