| Both sides previous revision Previous revision Next revision | Previous revision |
| network_configuration [2023/02/21 07:49] – evie | network_configuration [2023/08/11 22:55] (current) – Move to bootnote evie |
|---|
| |
| ===== Checking the connection ===== | ===== Checking the connection ===== |
| **A bug in the ''iproute2'' package causes the ''ping'' command to be marked as non-executable, this can be solved by running ''chmod +x /usr/bin/ping'' (which marks it as executable) as root.** | <bootnote warning> |
| | A bug in the ''iproute2'' package causes the ''ping'' command to be marked as non-executable, this can be solved by running ''chmod +x /usr/bin/ping'' (which marks it as executable) as root. |
| | </bootnote> |
| |
| There's a chance you may already be connected to your network, you can test this by using the ''ping'' utility to try and reach a host. | There's a chance you may already be connected to your network, you can test this by using the ''ping'' utility to try and reach a host. |
| |
| ===== Wireless networking ===== | ===== Wireless networking ===== |
| //yiffOS does not provide the legacy ''iwconfig'' package, as a result, ''iw'' is provided and will be used instead to connect to wireless networks.// | <bootnote> |
| | yiffOS does not provide the legacy ''iwconfig'' package, as a result, ''iw'' is provided and will be used instead to connect to wireless networks. |
| | </bootnote> |
| | |
| |
| ==== Device driver/firmware ==== | ==== Device driver/firmware ==== |
| |
| ==== Connecting to a wireless network ==== | ==== Connecting to a wireless network ==== |
| //These commands require you to run them with root permissions. Running them as a user might not throw errors, but they will also not produce the correct output either.// | <bootnote> |
| | These commands require you to run them with root permissions. Running them as a user might not throw errors, but they will also not produce the correct output either. |
| | </bootnote> |
| | |
| |
| === Get the interface name === | === Get the interface name === |
| |
| === Activate the interface (if required) === | === Activate the interface (if required) === |
| //If you get an error like ''Operation not possible due to RF-kill'', check to see if a hardware switch isn't mistakenly set to the off position.// | <bootnote> |
| | If you get an error like ''Operation not possible due to RF-kill'', check to see if a hardware switch isn't mistakenly set to the off position. |
| | </bootnote> |
| | |
| Your card might require the kernel interface to be activated before it can be used in iw. ''ip link set <interface> up'' | Your card might require the kernel interface to be activated before it can be used in iw. ''ip link set <interface> up'' |
| |
| |
| === Search for access points === | === Search for access points === |
| //If this command outputs ''Interface does not support scanning'', then you are most likely missing firmware. In some cases, this can also be caused by running iw as a regular user.// | <bootnote> |
| | If this command outputs ''Interface does not support scanning'', then you are most likely missing firmware. In some cases, this can also be caused by running iw as a regular user. |
| | </bootnote> |
| | |
| |
| Now that the interface is up, we can scan nearby access points with ''iw dev scan''. | Now that the interface is up, we can scan nearby access points with ''iw dev scan''. |
| |
| === Installation and Usage === | === Installation and Usage === |
| **If you're coming from systemd-networkd, make sure you delete the systemd-networkd configuration files and disable the service using ''systemctl disable --now systemd-networkd.service'' before starting NetworkManager.** | <bootnote warning> |
| | If you're coming from systemd-networkd, make sure you delete the systemd-networkd configuration files and disable the service using ''systemctl disable --now systemd-networkd.service'' before starting NetworkManager. |
| | </bootnote> |
| |
| Install the ''networkmanager'' package using ''bulge i networkmanager''. Once NetworkManager is installed, you can start the daemon by running ''systemctl enable --now NetworkManager.service''. It should automatically connect to any "available connections" (like Ethernet) upon the service starting. Networks like WiFi networks will require configuration before NetworkManager will automatically connect to it. | Install the ''networkmanager'' package using ''bulge i networkmanager''. Once NetworkManager is installed, you can start the daemon by running ''systemctl enable --now NetworkManager.service''. It should automatically connect to any "available connections" (like Ethernet) upon the service starting. Networks like WiFi networks will require configuration before NetworkManager will automatically connect to it. |
| |
| ==== systemd-networkd ==== | ==== systemd-networkd ==== |
| //If you aren't using any other DNS resolver (like ''dnsmasq''), you may want to also enable ''systemd-resolved'', you can do this by running ''systemctl enable --now systemd-resolved''. If you ARE, you should disable it instead by running ''systemctl disable --now systemd-resolved''.// | <bootnote warning> |
| | If you aren't using any other DNS resolver (like ''dnsmasq''), you may want to also enable ''systemd-resolved'', you can do this by running ''systemctl enable --now systemd-resolved''. If you ARE, you should disable it instead by running ''systemctl disable --now systemd-resolved''. |
| | </bootnote> |
| | |
| |
| In order to get the network device interface name, you can run ''ip a'' to get the information for all interfaces connected to your computer. Ethernet interfaces will commonly start with the letter "e" and wireless interfaces will commonly start with the letter "w". | In order to get the network device interface name, you can run ''ip a'' to get the information for all interfaces connected to your computer. Ethernet interfaces will commonly start with the letter "e" and wireless interfaces will commonly start with the letter "w". |
evie