ThinkServer - Recent changes [en-gb]

OpenSUSE Leap 16.0

Sam — Fri, 10 Jul 2026 14:13:45 GMT

Installation notes/Known Issues =: Removed extra =

← Older revision		Revision as of 14:13, 10 July 2026
Line 20:		Line 20:
	AppArmor is no longer the default security solution, SELinux is now the preferred security solution for openSUSE 16.0. AppArmor can, however, still be used if preferred.		AppArmor is no longer the default security solution, SELinux is now the preferred security solution for openSUSE 16.0. AppArmor can, however, still be used if preferred.

	== Installation notes/Known Issues ===		== Installation notes/Known Issues ==

	* If upgrading, check the "Unneeded Packages" category in Myrlyn once upgraded to remove any lingering unneeded packages from the previous version.		* If upgrading, check the "Unneeded Packages" category in Myrlyn once upgraded to remove any lingering unneeded packages from the previous version.

WireGuard

Sam — Wed, 01 Jul 2026 16:44:37 GMT

Recreated lost page through Wayback Machine

New page

WireGuard is a lightweight VPN server, built-in to the Linux kernel past kernel 5.6, making it very easy to set up on a Linux server. This guide will detail how to install on this server.

== Before you start ==
You will need to install the following packages:
* <code>openresolv</code> (for DNS resolution)
* <code>wireguard-tools</code>

=== Install the required packages ===
* Type <code>sudo zypper in openresolv wireguard-tools</code>
* Press <kbd>Y</kbd> to accept

=== Allow IP forwarding ===
WireGuard requires IP forwarding to function as it will forward packets between your network adapter and a virtual adapter.

* Open a terminal window
* Move to <code>/etc</code> - <code>cd /etc</code>
* Open <code>sysctl.conf</code> for editing - <code>sudo nano sysctl.conf</code>
* Type your root password and press <kbd>Enter</kbd>
* At the end of the file, type the following:
<pre>net.ipv4.ip_forward=1</pre>
* Press <kbd>Ctrl</kbd>+<kbd>X</kbd> then <kbd>Y</kbd> to save then <kbd>Enter</kbd> to confirm saving the file
* Load the changes - <code>sysctl -p</code>

=== Restart the computer ===
* After completing the previous steps, restart the computer. This will active <code>openresolv</code> (no further configuration needed) and ensure IP forwarding is enabled. You are now ready to configure WireGuard.

=== Allow port forwarding on the router ===
* Port 33333 or whatever port you choose later must be port forwarded through your router. Ensure this is for UDP, '''NOT''' TCP.

== Configure the server ==
We will now configure the server settings for WireGuard. WireGuard comes complete with tools to create the the private/public keys needed to function and is configured with a simple configuration file.

=== Become a superuser ===
For the following sets, you may need to become a superuser (<code>su</code>) to access the WireGuard folder.

* Become a superuser - <code>su</code>

=== Move to WireGuard directory ===
* Type your root password and press <kbd>Enter</kbd>. The terminal text should change to red to indicate you are now a superuser.
* Move to the WireGuard directory - <code>cd /etc/wireguard</code>

You will find this directory is empty - we will work in this directory which is secure.

=== Generate a public/private key pair ===
* Generate a private and public key for the server. You can use the following command:
<pre>wg genkey | tee server-privatekey | wg pubkey > server-publickey</pre>
* <code>server-privatekey</code> and <code>server-publickey</code> are filenames and can be anything you want and can be changed accordingly. These files are not directly used by WireGuard.

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
'''Warning'''

The private key generated should '''NEVER''' leave the server. Anyone with the private key can connect to and compromise the server. If the key does become compromised, a new private key should be generated and configured immediately and the old key never used again.

To keep private keys secure once used, it is advisable to store the private key somewhere offline and secure, away from the server. One example would be a USB stick. This way, if the server is compromised, it will be more difficult to compromise the private key. Ensure the permissions are correct as follows so that access is restricted to only superusers.

The public key is safe from compromise, this does not need to be stored with such security.

All private/public keys in this guide were generated as an example and are not in use on this server.
</div>

* Change the permissions of the private key so that only superusers can access the key: <code>chmod 600 server-privatekey</code>
* We need the private key to put in the configuration file: <code>cat server-privatekey</code>. This will display the key on the screen which can then be copied.

=== Create configuration file ===
* We will create a configuration file with the same name as the interface WireGuard will create: <code>nano wg0.conf</code>
* Insert the following into the file:
<pre>
[Interface]
## Local Address : A private IP address for wg0 interface.
Address = 10.20.10.1/24
ListenPort = 33333

## local server privatekey
PrivateKey = iFFxF+gX39U9O4L4qt2mufTS441YWLu5WVt0mMPpLEA=

## The PostUp will run when the WireGuard Server starts the virtual VPN tunnel.
## The PostDown rules run when the WireGuard Server stops the virtual VPN tunnel.
## Specify the command that allows traffic to leave the server and give the VPN clients access to the Internet.
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT
PostUp = iptables -t nat -A POSTROUTING -o em1 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT
PostDown = iptables -t nat -D POSTROUTING -o em1 -j MASQUERADE
</pre>
* Tweak the file to match your server configuration:
** <code>Address = 10.20.10.1/24</code> - this is the address used by the WireGuard interface and should be different from your local network subnet.
** <code>ListenPort = 33333</code> - 33333 is the default WireGuard network port but can be changed to anything you like as long as the port is not already in use by something else.
** <code>PrivateKey = iFFxF+gX39U9O4L4qt2mufTS441YWLu5WVt0mMPpLEA=</code> - Paste the key your generated and copied earlier.
** <code>PostUp = iptables -t nat -A POSTROUTING -o em1 -j MASQUERADE</code> and <code>PostDown = iptables -t nat -D POSTROUTING -o em1 -j MASQUERADE</code> - the interface needs changing according to the name of the Ethernet card on your computer (<code>em1</code> in this example, which can be found by typing <code>ip a</code>. Common names include <code>eth0</code>, <code>eno1</code> and <code>em1</code>.
* Once done, save the file: <kbd>Ctrl</kbd>+<kbd>X</kbd>, <kbd>Y</kbd> then <kbd>Enter</kbd>.
* Change the permissions so that the configuration file can only be accessed by superusers: <code>chmod 600 wg0.conf</code>

== Start WireGuard ==
* Type <code>systemctl start wg-quick@wg0</code> to start WireGuard.
** <code>wg0</code> is the name of the WireGuard interface and configuration file we created. If different, this should be changed to match the same name as the configuration file.
* Check that WireGuard is running: <code>wg show</code>. You should see something similar to the following if all is well:
<pre>
interface: wg0
public key: 7IXE2Ej++JNHXDeP9mt9/N+OslIBmvOAREzCnT0v6To=
private key: (hidden)
listening port: 33333
</pre>
* The public key should match the one generated earlier and can be viewed by typing <code>cat server-publickey</code>
* If you would like WireGuard to start on startup, type the following: <code>systemctl enable wg-quick@wg0</code>

== Setting up a client ==
Client software is available for many operating systems, including Windows, macOS, Linux (native support past Kernel 5.6) and Android. Here we will make a config file and add it to the server configuration, but due to the vast amount of different operating systems supported, we will not cover how to add the configuration to your respective operating system.

The client configuration file is similar to the server configuration file and remains very simple.

=== Generate a public/private key pair ===
* We will generated a public/private key pair much the same way as we did for the server:
<pre>wg genkey | tee client-privatekey | wg pubkey > client-publickey</pre>
** The name <code>client</code> for the file name can be changed to anything you like for convenience.
* Change the permissions of the private key so that only superusers can access the key: <code>chmod 600 client-privatekey</code>
* We need the private key to put in the configuration file: <code>cat client-privatekey</code>. This will display the key on the screen which can then be copied.

=== Creating a configuration file ===
* Open a new configuration file: <code>sudo nano client.conf</code>
** Once again, the name <code>client</code> can be anything you like for convenience.
* Insert the following into the file:
<pre>
[Interface]
PrivateKey = 4JYkCM3VBuRpJAHjj8S8LyunF+Can5ZLCxB8OjXo9WI=
ListenPort = 33333
Address = 10.20.10.2/24
DNS = 1.1.1.1, 1.0.0.1

[Peer]
PublicKey = 7IXE2Ej++JNHXDeP9mt9/N+OslIBmvOAREzCnT0v6To=
AllowedIPs = 0.0.0.0/0
Endpoint = example.com:33333
</pre>
* Tweak the file to match your client configuration:
** <code>PrivateKey = 4JYkCM3VBuRpJAHjj8S8LyunF+Can5ZLCxB8OjXo9WI=</code> - the private key generated for the client ('''NOT''' the server private key).
** <code>ListenPort = 33333</code> - needs to match the <code>ListenPort</code> for the server.
** <code>Address = 10.20.10.2/24</code> - the address to use, within the subnet defined in the server configuration.
** <code>DNS = 1.1.1.1, 1.0.0.1</code> - the DNS server to use to resolve names. Something needs to be defined here as there is no DHCP to define a DNS server. This can be a server of your own on the network, your router or one of the many online services (CloudFlare DNS = 1.1.1.1, 1.0.0.1, Google DNS = 8.8.8.8, 8.8.4.4).
** <code>PublicKey = 7IXE2Ej++JNHXDeP9mt9/N+OslIBmvOAREzCnT0v6To=</code> - the public key of the server, '''NOT''' the client public key.
** <code>AllowedIPs = 0.0.0.0/0</code> - range of addresses that will be passed over the tunnel. Comma-separated list, can include IPv6 addresses if being used. 0.0.0.0/0 forwards everything.
** <code>Endpoint = example.com:33333</code> - DNS address or IP address to connect to the server. An IP address will only be useful if you have a static address, otherwise a DNS address with DynDNS is a better solution.
* Save the file - <kbd>Ctrl</kbd>+<kbd>X</kbd>, <kbd>Y</kbd> then <kbd>Enter</kbd>.
* The file can then be transferred to the client and imported into the WireGuard client ready for use.

=== Adding peers to the server configuration ===
* Open the server configuration file - <code>nano wg0.conf</code>
* Add the <code>[Peer]</code> section, marked in italics, as follows:
<pre>
[Interface]
## Local Address : A private IP address for wg0 interface.
Address = 10.20.10.1/24
ListenPort = 33333

## local server privatekey
PrivateKey = iFFxF+gX39U9O4L4qt2mufTS441YWLu5WVt0mMPpLEA=

## The PostUp will run when the WireGuard Server starts the virtual VPN tunnel.
## The PostDown rules run when the WireGuard Server stops the virtual VPN tunnel.
## Specify the command that allows traffic to leave the server and give the VPN clients access to the Internet.
PostUp = iptables -A FORWARD -i wg0 -j ACCEPT
PostUp = iptables -t nat -A POSTROUTING -o em1 -j MASQUERADE
PostDown = iptables -D FORWARD -i wg0 -j ACCEPT
PostDown = iptables -t nat -D POSTROUTING -o em1 -j MASQUERADE

''[Peer]''
''# one client which will be setup to use 10.20.10.2 IP''
''PublicKey = 92p5r33HRrEvzlQJIdANcyIKx0JgtNV5VfQOOwLnFwM=''
''AllowedIPs = 10.20.10.2/32''
</pre>
* Tweak the file to match your client configuration:
** <code>PublicKey = 92p5r33HRrEvzlQJIdANcyIKx0JgtNV5VfQOOwLnFwM=</code> - the public key generated for the client.
** <code>AllowedIPs = 10.20.10.2/32</code> - the IP address used for the tunnel, should match the client configuration file.
* Save the file - <kbd>Ctrl</kbd>+<kbd>X</kbd>, <kbd>Y</kbd> then <kbd>Enter</kbd>.

== Reloading the server ==
For our changes to take effect, the WireGuard daemon needs to be reloaded or restarted using:
<pre>systemctl reload wg-quick@wg0</pre>
or
<pre>systemctl restart wg-quick@wg0</pre>

At this point, the WireGuard VPN is ready to go!

== Adding further clients ==
* Generate a public/private key pair as explained under the client section.
* Create a configuration with the new public/private key pair generated.
* Copy the configuration to the respective client.
* Add another <code>[Peer]</code> section to the server configuration.
* Reload the WireGuard server.

== See also ==
Thank you to "Mark Liversedge" at [https://markliversedge.blogspot.com/2023/09/wireguard-setup-for-dummies.html Wireguard setup for dummeies] with his comprehensive guide that made this possible for me

OpenSUSE Leap 16.0 Release Notes

Sam — Wed, 01 Jul 2026 16:40:22 GMT

Recreated lost page through Wayback Machine

Show changes

Obtaining openSUSE 16.0

Sam — Wed, 01 Jul 2026 14:58:34 GMT

Corrected incorrect showing link

← Older revision		Revision as of 14:58, 1 July 2026
Line 1:		Line 1:
	[[openSUSE Leap 16.0]] is available from the following locations:		[[openSUSE Leap 16.0]] is available from the following locations:

	* [https://www.opensuse.org/], click 'Leap' then 'Install Leap'		* https://www.opensuse.org/, click 'Leap' then 'Install Leap'
	** DVD/USB installation - this is the most common download option and needed for conventional installations. (Direct/Torrent)		** DVD/USB installation - this is the most common download option and needed for conventional installations. (Direct/Torrent)
	** Network installation - installs the system from an internet repository or network repository. (Direct/Torrent)		** Network installation - installs the system from an internet repository or network repository. (Direct/Torrent)

Obtaining openSUSE 16.0

Sam — Wed, 01 Jul 2026 14:57:49 GMT

Recreated lost page through Wayback Machine

New page

[[openSUSE Leap 16.0]] is available from the following locations:

* [https://www.opensuse.org/], click 'Leap' then 'Install Leap'
** DVD/USB installation - this is the most common download option and needed for conventional installations. (Direct/Torrent)
** Network installation - installs the system from an internet repository or network repository. (Direct/Torrent)
* If I have already downloaded an ISO, they are currently available at \\thinkserver\Build\CD Images\ via Samba/Windows File share.
* The ISO needs to be put onto a USB Stick and made into a bootable USB drive. This method completely wipes the stick and needs the computer to support booting from USB. However, this method makes the installation a lot faster than optical media. On Windows, the recommended method is to use [https://rufus.ie/ Rufus] in DD writing mode.
* They can also be burned to a DVD. The image itself needs burning, not the image file. For more information, see [[burning a CD/DVD image]].

'''NOTE: 32-bit builds are no longer available, only 64-bit is supported (most modern CPU's support 64-bit, late generation Intel Pentium 4's and all Core processors will support x86_64). If you require 32-bit, you must use the [[openSUSE Tumbleweed]] distribution.'''

'''NOTE: x86_64 builds require an microarchitecture level of at least x86_84 v2 (at least Intel Core i3/5/7 1st generation) to install as of openSUSE 16.0.'''

== Download links ==

'''NOTE: SHA-256 values removed as links download latest build available at the time, which may not match the SHA-256 values if kept here.'''

These should be available during the lifetime of this version:

=== Intel or AMD 64-bit desktops, laptops, and servers (x86_64) ===

==== DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-x86_64.install.iso

Torrent: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-x86_64.install.iso.torrent

==== Network Install DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-x86_64.install.iso

Torrent: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-x86_64.install.iso.torrent

=== UEFI ARM 64-bit servers, desktops, laptops and boards (aarch64) ===

==== DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-aarch64.install.iso

Torrent: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-aarch64.install.iso.torrent

==== Network Install DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-aarch64.install.iso

Torrent: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-aarch64.install.iso.torrent

=== PowerPC servers, not big-endian (ppc64le) ===

==== DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-ppc64le.install.iso

Torrent: Not available at launch

==== Network Install DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-ppc64le.install.iso

Torrent: Not available at launch

=== IBM zSystems and LinuxONE (s390x) ===

==== DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-offline-installer-s390x.install.iso

Torrent: Not available at launch

==== Network Install DVD ====

Direct: https://download.opensuse.org/distribution/leap/16.0/offline/Leap-16.0-online-installer-s390x.install.iso

Torrent: Not available at launch

Template:Current openSUSE

Sam — Wed, 01 Jul 2026 14:49:42 GMT

Changed to openSUSE 16.0

← Older revision		Revision as of 14:49, 1 July 2026
Line 1:		Line 1:
	[[openSUSE Leap 15.6]]		[[openSUSE Leap 16.0]]

File:OpenSUSE Leap 16.0 webpage.webp

Sam — Wed, 01 Jul 2026 14:48:52 GMT

Sam uploaded File:OpenSUSE Leap 16.0 webpage.webp Original summary - "Screenshot taken with scrollbar in correct location at the top of the page".

New page

== Summary ==
Original summary - "Screenshot taken with scrollbar in correct location at the top of the page".

OpenSUSE Leap 16.0

Sam — Wed, 01 Jul 2026 14:48:04 GMT

Added webpage image

← Older revision		Revision as of 14:48, 1 July 2026
Line 36:		Line 36:
	* openSUSE Leap 15.6 (Supported until 30th April 2026)		* openSUSE Leap 15.6 (Supported until 30th April 2026)
	* openSUSE Tumbleweed (Rolling release)		* openSUSE Tumbleweed (Rolling release)
			<br>
			[[File:openSUSE Leap 16.0 webpage.webp\|center\|400px]]

OpenSUSE Leap 16.0

Sam — Wed, 01 Jul 2026 14:45:33 GMT

Recreated lost page through Wayback Machine

New page

This is the Linux distribution my server is based on. More information is available [https://www.opensuse.org/ here].

If you are looking to install openSUSE, there are more details in [[obtaining openSUSE 16.0]].

== Changes to openSUSE ==
=== YaST deprication ===

YaST is no longer being developed by SuSE and therefore is not being developed for openSUSE. Therefore, YaST is not available in openSUSE 16.0. openSUSE 16.0 now uses Myrlyn for package management and Cockpit for most other things YaST used to do.

=== New installer ===

Agama is the new web based installer for openSUSE when installing via ISO image. There is also a migration tool available in previous versions that takes care of the full migration to openSUSE 16.0 automatically and painlessly.

=== Wayland compositor by default ===

openSUSE 16.0 no longer uses X and defaults to using Wayland as the desktop compositor. To use X as before, this must be installed yourself but do note, this is deprecated.

=== AppArmor no longer default ===

AppArmor is no longer the default security solution, SELinux is now the preferred security solution for openSUSE 16.0. AppArmor can, however, still be used if preferred.

== Installation notes/Known Issues ===

* If upgrading, check the "Unneeded Packages" category in Myrlyn once upgraded to remove any lingering unneeded packages from the previous version.

== Release notes ==

[[OpenSUSE Leap 16.0 Release Notes|Release Notes]]

== Information ==

openSUSE Leap 16.0 was released on 1st October 2025. It is an open-source distribution and is free of charge. It is developed by the community and sponsored by [https://www.eqtgroup.com/ EQT Partners] (formally Micro Focus and Novell).

== Previous supported versions (at time of release) ==

* openSUSE Leap 15.6 (Supported until 30th April 2026)
* openSUSE Tumbleweed (Rolling release)