3 ms·

> (in my experience on Arch at least, network configuration was a bitch) What exactly about this was hard? I have one config file - /etc/wpa_supplicant/wpa_su

> (in my experience on Arch at least, network configuration was a bitch) What exactly about this was hard? I have one config file - /etc/wpa_supplicant/wpa_supplicant-wlan0.conf - which you can add to simply with wpa_passphrase "MySSID" "MyKey" > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf Then I ran a couple commands once: systemctl enable wpa_supplicant@wlan0 systemctl enable dhcpcd@wlan0 And now it happily connects to any of the wireless networks I've set up in the config file. If I want to control it or switch networks or reload my config, I can use wpa_cli to do this easily. Totally minimal, no need for NetworkManager or netctl or anything, and works flawlessly. Obviously if your net setup is more complex, this could require a better tool, but most of weird stuff would be done with iproute2 or whatever.

ultramancool 12y ago
I had a personal dev server running arch with a simple static IP. I had tutorials on arch telling me to manually create and edit systemd scripts to start and stop the interface, then add and enable them. To configure a simple static IP, which should be an extremely trivial task. Now compare with FreeBSD, just add 1 single line to /etc/rc.conf and I'm done, 2 if I want a default gateway too. Here's a link to what I was dealing with: https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd https://wiki.archlinux.org/index.php/Network_configuration#P... 20+ lines vs 2. You tell me which is simpler. Also, our of curiosity, do you know what systemctl enable does? What files does it modify and how would you do it on a remote system (ie: one you'd mounted)? Would you need to chroot?
- dnlrn 12y ago
  You are comparing apples and oranges. Network management in Arch was replaced by netctl. It’s very easy to set up your static network that way (you just have to edit 1 line). systemctl actually tells you what it does as output. It symlinks a service file from one directory to another. You can always do that by hand.
antihero 12y ago
Frankly, that's a poor way to do it. A much better way would be to simply run `systemctl enable dhcpcd@eth0` and then edit the dhcpcd config. https://wiki.archlinux.org/index.php/Dhcpcd#Running https://wiki.archlinux.org/index.php/Dhcpcd#Running And/or have your IPs configured by a DHCP server.

ultramancool 12y ago

I had a personal dev server running arch with a simple static IP. I had tutorials on arch telling me to manually create and edit systemd scripts to start and stop the interface, then add and enable them. To configure a simple static IP, which should be an extremely trivial task. Now compare with FreeBSD, just add 1 single line to /etc/rc.conf and I'm done, 2 if I want a default gateway too. Here's a link to what I was dealing with: https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd https://wiki.archlinux.org/index.php/Network_configuration#P... 20+ lines vs 2. You tell me which is simpler. Also, our of curiosity, do you know what systemctl enable does? What files does it modify and how would you do it on a remote system (ie: one you'd mounted)? Would you need to chroot?

dnlrn 12y ago
You are comparing apples and oranges. Network management in Arch was replaced by netctl. It’s very easy to set up your static network that way (you just have to edit 1 line). systemctl actually tells you what it does as output. It symlinks a service file from one directory to another. You can always do that by hand.

antihero 12y ago

Frankly, that's a poor way to do it. A much better way would be to simply run `systemctl enable dhcpcd@eth0` and then edit the dhcpcd config. https://wiki.archlinux.org/index.php/Dhcpcd#Running https://wiki.archlinux.org/index.php/Dhcpcd#Running And/or have your IPs configured by a DHCP server.