| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| distros:opensuse_tumbleweed_server [2024/05/10 21:24] – Sean Rhone | distros:opensuse_tumbleweed_server [2024/06/02 12:33] (current) – [NetworkManager] Sean Rhone |
|---|
| |
| ===== NetworkManager ===== | ===== NetworkManager ===== |
| | |
| | * TODO: Make a static Ethernet profile with these settings, attach it to a device(?), and activate it to replace whatever gets created by-default ((''Wired connection 1'' appeared after replacing a network card and didn't follow the ''enp0s'' scheme)) |
| |
| <code>nmcli con show</code> | <code>nmcli con show</code> |
| |
| <code>sudo nmcli connection modify 'enp2s0' 'ipv4.dns' '9.9.9.9,149.112.112.112,1.1.1.2'</code> | <code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.dns' '192.168.1.1,9.9.9.9,149.112.112.112'</code> |
| |
| <code>sudo nmcli connection modify 'enp2s0' 'ipv6.dns' '2620:fe::fe,2620:fe::9,2606:4700:4700::1112'</code> | <code>sudo nmcli connection modify 'Wired connection 1' 'ipv6.dns' '2620:fe::fe,2620:fe::9,2606:4700:4700::1112'</code> |
| |
| <code>sudo nmcli connection modify 'enp2s0' 'ipv4.address' '192.168.1.152/24'</code> | <code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.address' '192.168.1.152/24'</code> |
| |
| <code>sudo nmcli connection modify 'enp2s0' 'ipv4.gateway' '192.168.1.1'</code> | <code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.gateway' '192.168.1.1'</code> |
| |
| <code>sudo nmcli connection modify 'enp2s0' 'ipv4.method' 'manual'</code> | <code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.method' 'manual'</code> |
| |
| <code>sudo nmcli connection up 'enp2s0'</code> | <code>sudo nmcli connection up 'Wired connection 1'</code> |
| |
| ===== lm_sensors ===== | ===== lm_sensors ===== |
| ===== Time ===== | ===== Time ===== |
| |
| * :!: 2024/05/06: Even though ''chrony'' does NTP sync, it doesn't seem to write it to the hardware clock which is usually wrong after a CMOS reset ((starting Firefox quickly after rebooting has a wrong system clock certificate failure error)) | * :?: 2024/05/06: On GNOME, even though ''chrony'' does NTP sync, it doesn't seem to write it to the hardware clock which is usually wrong after a CMOS reset ((starting Firefox quickly after rebooting has a wrong system clock certificate failure error)); it's not known if this affects Server |
| * This sets the hardware clock to the current system/OS clock | * This sets the hardware clock to the current system/OS clock |
| * TODO: Figure out ''chrony'' command to do NTP sync | * TODO: Figure out ''chrony'' command to do NTP sync |
