MediaWiki - Recent changes [en]

HowTo One Liners

Rwh — Thu, 05 Nov 2026 01:13:23 GMT

Use ssh-keygen To Remove An Incorrect Host Key

← Older revision		Revision as of 20:13, 4 November 2026
(3 intermediate revisions by the same user not shown)
Line 224:		Line 224:

	rmsshhost 54		rmsshhost 54

			== Use ssh-keygen To Remove An Incorrect Host Key ==
			To remove all keys belonging to the specified hostname in the default known host file: "'''~/.ssh/known_hosts'''" use the following: '''ssh-keygen -R hostname \| [hostname]:port [-f known_hosts_file]''':

			taco:~ pkb$ ssh-keygen -R salsa-e
			# Host salsa-e found: line 54

	= Find File Differences in Two Directories =		= Find File Differences in Two Directories =

HowTo Increase DNF Download Threads

Rwh — Mon, 02 Nov 2026 16:25:01 GMT

Overview

@@ Line 1: / Line 1: @@
 __TOC__
 == '''Overview''' ==
-To increase the number of simultaneous package download threads (parallel downloads) in [https://en.wikipedia.org/wiki/DNF_(software) DNF], edit the DNF configuration file and add or modify the max_parallel_downloads setting. The default value is 3.
+To increase the number of simultaneous package download threads (parallel downloads) in [https://en.wikipedia.org/wiki/DNF_(software) DNF], edit the DNF configuration file and add or modify the "'''max_parallel_downloads'''" setting. The default value is 3.

HowTo Increase DNF Download Threads

Rwh — Mon, 02 Nov 2026 16:06:42 GMT

Created page with "__TOC__ == '''Overview''' == To increase the number of simultaneous package download threads (parallel downloads) in [https://en.wikipedia.org/wiki/DNF_(software) DNF], edit the DNF configuration file and add or modify the max_parallel_downloads setting. The default value is 3."

New page

__TOC__
== '''Overview''' ==
To increase the number of simultaneous package download threads (parallel downloads) in [https://en.wikipedia.org/wiki/DNF_(software) DNF], edit the DNF configuration file and add or modify the max_parallel_downloads setting. The default value is 3.

HowTos

Rwh — Mon, 02 Nov 2026 16:05:21 GMT

← Older revision		Revision as of 11:05, 2 November 2026
Line 21:		Line 21:
	* [[HowTo Geolocate Data Using The NST WUI]]		* [[HowTo Geolocate Data Using The NST WUI]]
	* [[HowTo Headless Intel NUC vPro AMT]]		* [[HowTo Headless Intel NUC vPro AMT]]
			* [[HowTo Increase DNF Download Threads]]
	* [[HowTo Install Microsoft PowerShell]]		* [[HowTo Install Microsoft PowerShell]]
	* [[HowTo Install The MATE (GNOME 2) Desktop]]		* [[HowTo Install The MATE (GNOME 2) Desktop]]

HowTo Quickly Setup A VPN Using WireGuard On NST

Rwh — Mon, 19 Oct 2026 17:08:41 GMT

WireGuard Re-Resolve DNS When The Peer IP Address Changes

← Older revision		Revision as of 12:08, 19 October 2026
(10 intermediate revisions by the same user not shown)
Line 24:		Line 24:

	=== Example VPN Setup Steps ===		=== Example VPN Setup Steps ===
	In this example we will setup a WireGuard VPN between two (2) NST systems across the Internet. Both NST systems are behind a '''[https://en.wikipedia.org/wiki/Network_address_translation NAT]'''ed firewall. We will use the template IP Addresses for the VPN tunnel endpoints.		In this example we will setup a WireGuard VPN between two (2) NST systems across the Internet. Both NST systems are behind a '''[https://en.wikipedia.org/wiki/Network_address_translation NAT]'''ed firewall. We will use the template IP Addresses for the VPN tunnel endpoints. We will configure a wireguard "'''wg0'''" interface.

	'''***Note''': All WireGuard VPN configuration and command execution requires "'''root'''" access. One can "'''su -'''" to the "'''root'''" user or use the "'''sudo'''" command with the "'''nst'''" user for configuration and command execution. The "'''root'''" user was used for this example VPN setup.		'''***Note''': All WireGuard VPN configuration and command execution requires "'''root'''" access. One can "'''su -'''" to the "'''root'''" user or use the "'''sudo'''" command with the "'''nst'''" user for configuration and command execution. The "'''root'''" user was used for this example VPN setup.
Line 491:		Line 491:
	[root@pktcap28 ~]# systemctl enable wg-quick@wg0.service;		[root@pktcap28 ~]# systemctl enable wg-quick@wg0.service;
	[root@pktcap28 ~]# systemctl status wg-quick@wg0.service;		[root@pktcap28 ~]# systemctl status wg-quick@wg0.service;

			==== WireGuard Re-Resolve DNS When The Peer IP Address Changes ====
			WireGuard resolves the Endpoint hostname only once — when the interface is brought up (or when you explicitly set it). It then caches that IP Address. PersistentKeepalive (e.g. 25 seconds) keeps the tunnel alive and lets the other side update its idea of your IP, but it does not cause the client to re-look up a changed server IP Address. This is a well-known limitation with [https://en.wikipedia.org/wiki/Dynamic_DNS DDNS] setups.

			NST has a configured systemd timer and service unit for keeping the peer endpoint DNS entry current. If the peer endpoint (i.e. wireguard server) is behind an ISP offering a DHCP IPv4 Address and [https://en.wikipedia.org/wiki/Network_address_translation NAT]ed, then periodically the public facing IPv4 Address will change. The wireguard tools project contribute section offers a script: "'''reresolve-dns.sh'''" that can be used to automatically re-resolves DNS when the endpoint IPv4 Address changes or the tunnel fails.

			As an example lets say you configured an "'''wg0'''" interface. Simply run:

			[nst@nst44 ~]$ sudo systemctl enable --now wg-reresolve-dns@wg0.timer

			to keep your wireguard "'''wg0'''" tunnel alive when the peer's IPv4 Address changes.

			<div class="centerBlock"><div class="noteMessage">'''Note:''' This setup will only work if the peer wireguard server is using DDNS.</div></div>

	== Server With Multiple Clients/Peers ==		== Server With Multiple Clients/Peers ==