Differences

This shows you the differences between two versions of the page.

--- distros:opensuse_tumbleweed_server [2024/05/10 20:59] – Sean Rhone
+++ distros:opensuse_tumbleweed_server [2024/06/02 12:06] – [NetworkManager] Sean Rhone
@@ Line 103: / Line 103: @@
   * Last updated: 2024/05/10
-<code>preempt='none' nohz='off' pci='pcie_bus_perf,realloc,pcie_scan_all,big_root_window' pcie_aspm='off' reboot='pci'</code>
+<code>preempt='none' nohz='off' pci='pcie_bus_perf,realloc,pcie_scan_all,big_root_window' pcie_aspm='off' modprobe.blacklist='sp5100_tco' nowatchdog</code>
-===== Network =====
+===== NetworkManager =====
-****
+<code>nmcli con show</code>
-  sudo yast2 'lan'
+<code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.dns' '192.168.1.1,9.9.9.9,149.112.112.112'</code>
-==== Hostname/DNS ====
+<code>sudo nmcli connection modify 'Wired connection 1' 'ipv6.dns' '2620:fe::fe,2620:fe::9,2606:4700:4700::1112'</code>
-  * https://quad9.net/
+<code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.address' '192.168.1.152/24'</code>
-  * See [[notes:dns_servers|DNS servers]] for other DNS servers
-  * Static Hostname: ''Computer name''
+<code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.gateway' '192.168.1.1'</code>
-  * Modify DNS Configuration: ''Use Custom Policy''
-  * Name Server 1: ''9.9.9.9''
-  * Name Server 2: ''149.112.112.112''
-  * Name Server 3: ''1.1.1.2''
-==== Routing ====
+<code>sudo nmcli connection modify 'Wired connection 1' 'ipv4.method' 'manual'</code>
-  * Destination: ''default''
+<code>sudo nmcli connection up 'Wired connection 1'</code>
-  * Gateway: ''192.168.1.1''
-  * Device: ''-''
 ===== lm_sensors =====
@@ Line 157: / Line 150: @@
 ===== 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
   * TODO: Figure out ''chrony'' command to do NTP sync