CompleteNoobs - User contributions [en]

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T21:31:37Z

Test1:

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>
* [[Raspberry_Pi_2_as_a_Tailscale_Exit_Node_for_Home_Network#Install_Tailscale| Use same method as PI to install to laptop]]

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

===Simple Script===

* Create file name you will remember - or at least know what it is when you see it
<code>sudo $EDITOR /usr/local/bin/tailscale_home_pi_connect</code>
<div class="toccolours mw-collapsible mw-collapsed">
'''Why /usr/local/bin/?'''
<div class="mw-collapsible-content">
Putting your script in <code>/usr/local/bin/</code> is smart because:<br>
* '''System-Wide Access:''' It’s in the system’s PATH by default on Ubuntu and Raspberry Pi OS, so you can run <code>tailscale_home_pi_connect</code> from anywhere in the terminal without typing the full path.<br>
* '''Standard Location:''' It’s the conventional spot for user-added scripts or binaries, keeping your system organized and separate from OS-provided tools (like <code>/usr/bin/</code>).<br>
* '''Root Privileges Match:''' Since your script uses <code>sudo</code>, placing it in a system directory like <code>/usr/local/bin/</code> (with <code>sudo chmod +x</code>) aligns with needing elevated permissions, making it feel like a proper system command.<br>
* '''Avoid Clutter:''' Unlike your home directory (e.g., <code>/home/$USER/</code>), it won’t get lost among personal files, and it’s accessible to all users if needed.<br>
Other places like <code>/bin/</code> or <code>/usr/bin/</code> are reserved for OS packages, and random directories might require extra PATH setup—<code>/usr/local/bin/</code> is the sweet spot for custom scripts like this!
</div>
</div>
<pre>
#!/bin/bash
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
# NOTE: To disconnect: sudo tailscale down
</pre>

* Make script excutable
<code>sudo chmod +x /usr/local/bin/tailscale_home_pi_connect</code>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== SEO: Find This Guide Easily ==

Looking to '''SSH tunnel into your home network safely''' or set up a '''Raspberry Pi 2 as a Tailscale exit node'''? This guide covers everything you need for secure remote access to your '''home network''' using a '''headless Raspberry Pi 2'''. Key terms to find this page again: '''Raspberry Pi 2 Tailscale setup''', '''Tailscale exit node tutorial''', '''headless SSH home VPN''', '''nmap IP discovery for Pi''', '''DIY VPN with Raspberry Pi''', '''secure home server access''', '''Tailscale remote access'''. Whether you’re editing a '''local wiki''' or managing devices on your '''home LAN''', this '''RPi2 Tailscale guide''' has you covered.

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T21:27:47Z

Test1: /* Step 4: Connect from Your Laptop */

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>
* [[Raspberry_Pi_2_as_a_Tailscale_Exit_Node_for_Home_Network#Install_Tailscale| Use same method as PI to install to laptop]]

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

===Simple Script===

* Create file name you will remember - or at least know what it is when you see it
<code>sudo $EDITOR /usr/local/bin/tailscale_home_pi_connect</code>

<pre>
#!/bin/bash
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
# NOTE: To disconnect: sudo tailscale down
</pre>

* Make script excutable
<code>sudo chmod +x /usr/local/bin/tailscale_home_pi_connect</code>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== SEO: Find This Guide Easily ==

Looking to '''SSH tunnel into your home network safely''' or set up a '''Raspberry Pi 2 as a Tailscale exit node'''? This guide covers everything you need for secure remote access to your '''home network''' using a '''headless Raspberry Pi 2'''. Key terms to find this page again: '''Raspberry Pi 2 Tailscale setup''', '''Tailscale exit node tutorial''', '''headless SSH home VPN''', '''nmap IP discovery for Pi''', '''DIY VPN with Raspberry Pi''', '''secure home server access''', '''Tailscale remote access'''. Whether you’re editing a '''local wiki''' or managing devices on your '''home LAN''', this '''RPi2 Tailscale guide''' has you covered.

Ubuntu 24.04 Terminal CLI Processes and Services

2025-03-19T20:37:54Z

Test1: Created page with "== Ubuntu 24.04 Processes and Services == Ubuntu 24.04 introduces updated tools and enhancements for managing processes and services. This guide covers how to monitor, control, and optimize processes and services on your Ubuntu 24.04 system, including practical examples like running applications in the background and managing system services with <code>systemd</code>. == Introduction == Processes and services are fundamental to the operation of any Linux system, inclu..."

== Ubuntu 24.04 Processes and Services ==

Ubuntu 24.04 introduces updated tools and enhancements for managing processes and services. This guide covers how to monitor, control, and optimize processes and services on your Ubuntu 24.04 system, including practical examples like running applications in the background and managing system services with <code>systemd</code>.

== Introduction ==

Processes and services are fundamental to the operation of any Linux system, including Ubuntu 24.04. A '''process''' is an instance of a running program, while a '''service''' is a background process that provides system functionality, often starting at boot. This page will guide you through understanding, managing, and troubleshooting processes and services in Ubuntu 24.04, with a focus on tools and features specific to this release.

== Understanding Processes in Ubuntu 24.04 ==

=== Process Basics ===
In Ubuntu 24.04, each process has a unique '''Process ID (PID)''' and exists in one of several states:
* '''Running''': The process is executing or waiting to execute.
* '''Sleeping''': The process is waiting for an event (e.g., user input).
* '''Stopped''': The process is paused, often by user action.
* '''Zombie''': The process has terminated but remains in the process table.

Processes are hierarchical, with parent processes creating child processes. The root of this hierarchy is the '''init''' process (PID 1), managed by <code>systemd</code> in Ubuntu 24.04.

=== Tools for Process Management ===
Ubuntu 24.04 provides several tools to monitor and manage processes:
* <code>ps</code>: Lists processes. Use <code>ps aux</code> for a detailed view.
* <code>top</code>: Displays real-time process information, sorted by CPU usage.
* <code>htop</code>: An enhanced version of <code>top</code> with a user-friendly interface. Install it with <code>sudo apt install htop</code>.
* <code>pgrep</code>: Finds processes by name or other attributes. For example, <code>pgrep -f keepassxc</code> finds processes matching "keepassxc".

Ubuntu 24.04 also includes improvements in process scheduling and resource management, optimizing performance for both desktop and server environments.

== Background and Foreground Processes ==

Processes in Ubuntu 24.04 can run in the '''foreground''' or '''background'''. Understanding how to manage them is key to efficient multitasking in the terminal.

=== Foreground Processes ===
Foreground processes run interactively in the terminal, blocking further commands until they complete or are paused. For example, launching <code>nano</code> to edit a file ties up the terminal until you exit the editor.

=== Background Processes ===
Background processes run independently of the terminal, allowing you to continue using it for other tasks. This is ideal for long-running applications like downloads or running a KeePassXC AppImage.

=== Managing Background and Foreground Processes ===

* '''Starting a Process in the Background''': Add an ampersand (<code>&</code>) to the command. For example:
<pre>./keepassxc.appimage &</pre>
This launches KeePassXC in the background, displaying a job number (e.g., <code>[1]</code>) and PID (e.g., <code>12345</code>).

* '''Moving a Foreground Process to the Background''': If a process is already running in the foreground:
** Pause it with <code>Ctrl + Z</code> (e.g., <code>[1]+ Stopped ./keepassxc.appimage</code>).
** Resume it in the background with:
<pre>bg</pre>

* '''Checking Background Processes''': List all background jobs in the current terminal session:
<pre>jobs</pre>
Output might look like:
<pre>[1]+ Running ./keepassxc.appimage &</pre>
To see all processes (including those not tied to the terminal), use:
<pre>ps aux | grep keepassxc</pre>

* '''Bringing a Background Process to the Foreground''': Use the <code>fg</code> command with the job number:
<pre>fg %1</pre>
Replace <code>%1</code> with the job number from the <code>jobs</code> output.

* '''Closing a Background Process''': To terminate a specific background process:
** Find its PID:
<pre>pgrep -f keepassxc.appimage</pre>
This might return <code>12345</code>.
** Kill it:
<pre>kill 12345</pre>
Use <code>kill -9 12345</code> if it doesn’t close gracefully.

* '''Persistent Background Processes''': Closing the terminal ends background jobs. To keep them running, use <code>nohup</code>:
<pre>nohup ./keepassxc.appimage &</pre>
Or run them in a <code>tmux</code> or <code>screen</code> session.

=== Example: Running KeePassXC in the Background ===
Let’s run a KeePassXC AppImage in the background, check it, and close it:

* '''Start KeePassXC''':
<pre>./keepassxc.appimage &</pre>
Output: <code>[1] 12345</code>. KeePassXC runs, and the terminal is free.

* '''Check Background Jobs''':
<pre>jobs</pre>
Output: <code>[1]+ Running ./keepassxc.appimage &</code>.

* '''Verify with PID''':
<pre>pgrep -f keepassxc.appimage</pre>
Output: <code>12345</code>.

* '''Close KeePassXC''':
<pre>kill 12345</pre>
Verify it’s gone with <code>jobs</code> (empty output) or <code>ps aux | grep keepassxc</code>.

This approach lets you run KeePassXC without tying up your terminal, check its status, and stop it when needed.

== System Services in Ubuntu 24.04 ==

=== Systemd Overview ===
Ubuntu 24.04 uses <code>systemd</code> as its default init system, managing system services and boot processes. <code>systemd</code> provides better performance and advanced features compared to older init systems.

=== Managing Services with systemctl ===
The <code>systemctl</code> command is used to manage services. Common commands include:

* '''Start a service''':
<pre>sudo systemctl start service_name</pre>
* '''Stop a service''':
<pre>sudo systemctl stop service_name</pre>
* '''Enable a service''' (start at boot):
<pre>sudo systemctl enable service_name</pre>
* '''Disable a service''' (don’t start at boot):
<pre>sudo systemctl disable service_name</pre>
* '''Check service status''':
<pre>systemctl status service_name</pre>

=== Common Services in Ubuntu 24.04 ===
Some essential services include:
* <code>ssh</code>: Allows secure remote access.
* <code>apache2</code>: Serves web pages.
* <code>snapd</code>: Manages Snap packages, a key feature in Ubuntu.

=== Creating Custom Services ===
You can create your own services with <code>systemd</code>. For example, to start the IPFS daemon at boot:

* '''Create a service file''':
<pre>sudo nano /etc/systemd/system/ipfs.service</pre>

* '''Add the following content''':
<pre>
[Unit]
Description=Start IPFS daemon

[Service]
Type=simple
ExecStart=/usr/local/bin/ipfs daemon

[Install]
WantedBy=multi-user.target
</pre>

# '''Enable and start the service''':
<pre>sudo systemctl enable ipfs.service</pre>
<pre>sudo systemctl start ipfs</pre>

== Monitoring and Troubleshooting ==

=== Real-Time Monitoring ===
Use <code>top</code> or <code>htop</code> to monitor processes in real-time:
* <code>top</code>: Default tool, press <code>q</code> to quit.
* <code>htop</code>: More interactive, with color-coding and easier navigation.

=== Viewing Logs ===
Use <code>journalctl</code> to access service logs:
* '''View logs for a service''':
<pre>journalctl -u service_name</pre>
* '''Follow live logs''':
<pre>journalctl -f</pre>

=== Finding Process Issues ===
To identify resource-heavy processes:
* Use <code>top</code> or <code>htop</code> and sort by CPU or memory usage.
* Alternatively, use <code>ps aux | sort -nk 3</code> to sort by CPU usage.

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T20:06:16Z

Test1: /* Conclusion */

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>
* [[Raspberry_Pi_2_as_a_Tailscale_Exit_Node_for_Home_Network#Install_Tailscale| Use same method as PI to install to laptop]]

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== SEO: Find This Guide Easily ==

Looking to '''SSH tunnel into your home network safely''' or set up a '''Raspberry Pi 2 as a Tailscale exit node'''? This guide covers everything you need for secure remote access to your '''home network''' using a '''headless Raspberry Pi 2'''. Key terms to find this page again: '''Raspberry Pi 2 Tailscale setup''', '''Tailscale exit node tutorial''', '''headless SSH home VPN''', '''nmap IP discovery for Pi''', '''DIY VPN with Raspberry Pi''', '''secure home server access''', '''Tailscale remote access'''. Whether you’re editing a '''local wiki''' or managing devices on your '''home LAN''', this '''RPi2 Tailscale guide''' has you covered.

Ubuntu Package Management

2025-03-19T17:31:29Z

Test1: /* AppImage */

A package management system, also known as a package manager, is a set of tools and processes that automate the installation, upgrading, configuration, and removal of software packages on a computer system. Package management systems simplify the process of managing software by handling package dependencies, versioning, and distribution in a consistent and organized manner.

In the context of operating systems like Linux and Unix, software packages are bundles of files, libraries, executables, and metadata that together comprise a complete application or software component. Package managers are designed to manage these packages by tracking and resolving their dependencies, which are other software components that a package requires to function properly.

Key functions of package management systems include:

:* Maintaining repositories: Package managers connect to repositories, which are remote servers that store packages and their metadata. Repositories provide a centralized location for users to find, download, and install software packages.

:* Managing dependencies: When installing or upgrading a package, the package manager ensures that all required dependencies are also installed, updated, or removed as necessary. This helps maintain system stability and prevents conflicts or broken software.

:* Versioning: Package managers track and manage different versions of software packages, allowing users to install, upgrade, or downgrade specific versions as needed.

:* Handling package conflicts: Package managers can detect and resolve conflicts between packages, ensuring that the system remains in a consistent state even when multiple packages have overlapping or conflicting requirements.

:* Streamlining software installation and removal: Package managers automate the process of installing, upgrading, or removing software, making it easy for users to manage software on their systems without manual intervention.

Popular package managers include APT (used in Debian-based distributions), YUM and DNF (used in Red Hat-based distributions), and pacman (used in Arch Linux-based distributions). Each package manager is designed to work with specific package formats (such as .deb or .rpm) and may have its unique commands and features, but their overall purpose remains the same: to simplify and automate the process of managing software on a computer system.

== Package managers ==
Ubuntu is a popular Linux-based operating system that offers a wide range of applications for users. To install these applications, Ubuntu provides several package managers such as APT, Snap, AppImage, and Flatpak. Each package manager has its own advantages and disadvantages, and it's important to understand how they work and what they offer in order to choose the best one for your needs.

'''APT''' (Advanced Package Tool) is the default package manager for Ubuntu, and it uses a command-line interface to manage packages. APT offers a large selection of packages, and it's designed to be stable and reliable. '''Snap''', on the other hand, is a newer package manager that offers a more user-friendly interface and sandboxed apps. It also offers automatic updates and rollbacks, making it easy to manage and maintain applications.

'''AppImage''' and '''Flatpak''' are containerized formats that allow applications to run on multiple Linux distributions without needing to install dependencies. AppImage is a self-contained format that includes all dependencies, making it easy to run on any Linux distribution without needing to install anything. Flatpak, on the other hand, allows for more fine-grained control over dependencies and offers sandboxing and automatic updates.

By understanding the differences between these package managers, you can choose the best one for your needs and enjoy a wide range of applications on Ubuntu.

== Installing and updating software ==

===APT===

==== Update the package index:====

Before installing or updating software, it's essential to update the package index to ensure you have the latest information about available packages and their versions. Run the following command:

<code>sudo apt update</code>

This command will download package information from your configured repositories and update the local package index.

==== Search APT for packages====

To search for packages in the Ubuntu repository using APT, you can use the apt-cache search command followed by a keyword. For example:

<code>sudo apt-cache search <package-name></code>

Replace <package-name> with the name or keyword related to the package you are looking for.

Once you have found the package you want to install, you can install it using the apt-get install or apt install command.

==== Install a new package:====

To install a new package, use the apt install command followed by the package name:

<code>sudo apt install <package-name></code>

Replace <package-name> with the name of the package you want to install. APT will automatically handle the package's dependencies, installing them if necessary.

==== Update installed packages:====

To update all the installed packages to their latest available versions, run:

<code>sudo apt upgrade</code>

This command will upgrade packages based on the updated package index. It's a good practice to run this command regularly to keep your system up to date and secure.

==== Update a specific package:====

If you want to update a specific package, use the apt install command again:

<code>sudo apt install --only-upgrade <package-name></code>

Replace <package-name> with the name of the package you want to update. This command will only upgrade the specified package if a newer version is available.

==== Remove a package:====

If you want to remove a package, use the apt remove command followed by the package name:

<code>sudo apt remove <package-name></code>

Replace <package-name> with the name of the package you want to remove. Note that this command does not remove the package's configuration files. If you want to remove the package along with its configuration files, use the apt purge command instead:

<code>sudo apt purge <package-name></code>

===== '''dpkg''' remove=====

<code>dpkg -l | grep steam</code>
* returns/output
<pre>
rc steam:i386 1:1.0.0.74-1ubuntu2 i386 Valve's Steam digital software delivery system
rc steam-launcher 1:1.0.0.76 all Launcher for the Steam software distribution service
</pre>

<code>apt remove steam:i386</code>
* return output
<pre>Package 'steam:i386' is not installed, so not removed</pre>

The '''dpkg -l | grep steam''' command shows that the '''steam:i386''' and '''steam-launcher''' packages are installed on your system, but when you try to remove them using the '''apt remove''' command, you get a message that the packages are not installed.

This can happen if the packages were installed manually using a different method than the standard apt package manager. In this case, the packages were likely installed manually by downloading and installing the Steam installer from the Steam website.

To remove the Steam packages that are installed manually, you can run the following commands:

<code>sudo dpkg -r steam:i386</code>

<code>sudo dpkg -r steam-launcher</code>

Use '''--purge''' to remove '''config files'''

<code>sudo dpkg --purge steam:i386</code>

==== Clean up unused dependencies:====

Over time, your system may accumulate unused dependency packages. You can clean up these packages using the apt autoremove command:

<code>sudo apt autoremove</code>

This command will remove any packages that were installed as dependencies but are no longer needed by any installed software.

==== Install from a <b>.deb</b> file====

To install a .deb file that you have downloaded or obtained from an external source, you can use the dpkg command. First, navigate to the directory containing the .deb file using the cd command:

<code>cd /path/to/directory</code>

Then, install the .deb file using the dpkg -i command:

<code>sudo dpkg -i <filename.deb></code>

Replace <filename.deb> with the exact name of the .deb file you want to install.

Note that you can also use <b>path</b> if you do not want to <b>cd</b>:<code>sudo dpkg -i /path/to/program.deb</code>

Note that if the .deb package has any unmet dependencies, the installation may fail. To resolve this issue and automatically install any missing dependencies, you can run the following command:

<code>sudo apt-get install -f</code>

or

<code>sudo apt install -f</code>

This will install any missing dependencies and complete the installation of the .deb package.

===Managing Package Repositories===

:* Introduction to Package Repositories
: Package repositories are online servers that store software packages for installation and updates on Ubuntu systems. Ubuntu uses the Advanced Package Tool (APT) to manage these repositories. The default repositories include Main, Universe, Restricted, and Multiverse. You can also add third-party repositories (PPAs) for additional software.

Default Repositories

:* Main: Officially supported, open-source software maintained by Canonical.
:* Universe: Community-maintained open-source software.
:* Restricted: Proprietary drivers and software required for hardware compatibility.
:* Multiverse: Software not compliant with the Ubuntu licensing policies.

:* Updating Package List
: Before installing new packages, you should update the package list to fetch the latest information from the repositories.

:* Open a terminal (Ctrl+Alt+T)
:* Run the following command:

<code>sudo apt update</code>

: Adding a Personal Package Archive (PPA)
: PPAs are third-party repositories that contain software not available in the default repositories.

:* To add a PPA, open a terminal and type:

<code>sudo add-apt-repository ppa:user/ppa-name</code>

Replace "user" and "ppa-name" with the appropriate values.

Update the package list:

<code>sudo apt update</code>

====Removing a PPA====

:* To remove a PPA, open a terminal and type:

<code>sudo add-apt-repository --remove ppa:user/ppa-name</code>

Replace "user" and "ppa-name" with the appropriate values.

Update the package list:

<code>sudo apt update</code>

<div class="toccolours mw-collapsible mw-collapsed">
Example: Finding the '''ppa:user/ppa-name''' to remove:
<div class="mw-collapsible-content">
* when i try an '''apt update'''
<pre>
The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F24AEA9FB05498B7
Reading package lists... Done
W: GPG error: https://repo.steampowered.com/steam stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F24AEA9FB05498B7
E: The repository 'https://repo.steampowered.com/steam stable InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
</pre>

* Finding the '''package's''' and the '''repository'''

: Check which packages are installed from the repository with the following command:

<code>dpkg --list | grep steam</code>

: Remove any packages that are installed from the repository with the following command:

<code>sudo apt-get remove --purge <package-name></code>

: Find repository's

<code>ls -l /etc/apt/sources.list.d/</code>
* Returns:
<pre>
-rw-r--r-- 1 root root 296 Mar 1 18:55 steam-beta.list
-rw-r--r-- 1 root root 228 Mar 1 18:55 steam-stable.list
</pre>

<code>cat /etc/apt/sources.list.d/steam-stable.list</code>
* returns:
<pre>
deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ stable steam
</pre>

<code>cat /etc/apt/sources.list.d/steam-beta.list</code>
* returns:
<pre>
# Uncomment these lines to try the beta version of the Steam launcher
#deb [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ beta steam
#deb-src [arch=amd64,i386 signed-by=/usr/share/keyrings/steam.gpg] https://repo.steampowered.com/steam/ beta steam
</pre>

* Note: In '''steam-beta.list''' the lines are commented out with '''#''' at the beginning of the line.
* You can comment out the lines in '''steam-stable.list''' and '''sudo apt update'''
* Or you can delete the file '''steam-stable.list''' and '''sudo apt update'''

</div>
</div>

====Editing Repository Configuration Files====

The repository configuration files are stored in the '''/etc/apt/sources.list''' file and the files inside '''/etc/apt/sources.list.d/''' directory.
:* To edit the sources.list file, open a terminal and type:

<code>sudo nano /etc/apt/sources.list</code>

Make the necessary changes, save (Ctrl+O), and exit (Ctrl+X).
Update the package list:

<code>sudo apt update</code>

====Managing Repositories with Software & Updates====

:* You can also manage repositories using the Software & Updates application.
:* Open the application by searching "Software & Updates" in the applications menu.
:* In the "Ubuntu Software" tab, you can enable or disable the default repositories.
:* In the "Other Software" tab, you can add, edit, or remove third-party repositories.
:* After making changes, click "Close" and then click "Reload" to update the package list.

By following this tutorial, you'll be able to manage package repositories on your Ubuntu system, adding or removing PPAs as needed to install or update software.

====Dependency Management====

In Ubuntu, software packages often rely on other packages to function properly. These required packages are called dependencies. The Advanced Package Tool (APT) automatically handles dependency management, ensuring that all required packages are installed or updated when you install, update, or remove a package.

===== Installing a Package and Its Dependencies=====
: When you install a package using APT, it automatically resolves and installs the dependencies.

:* Open a terminal (Ctrl+Alt+T)
:* Install a package and its dependencies using the following command:

<code>sudo apt install package-name</code>

: Replace "package-name" with the appropriate package name.

:* Updating Packages and Dependencies
: APT also manages the dependencies while updating packages.

:* To update all installed packages and their dependencies, run the following command:

<code>sudo apt update && sudo apt upgrade</code>

===== Removing a Package and Unused Dependencies=====
: When you remove a package, APT will not automatically remove its dependencies if they are no longer required. To remove unused dependencies, use the 'autoremove' command.

:* To remove a package and its unused dependencies, run:

<code>sudo apt remove package-name && sudo apt autoremove</code>

:* Replace "package-name" with the appropriate package name.

:* Fixing Broken Dependencies
: Sometimes, you may encounter broken dependencies due to various reasons, such as interrupted installations or package conflicts. You can use APT to fix these issues.

:* To fix broken dependencies, run the following commands:
<pre>
sudo apt update
sudo apt install -f
</pre>

===== Listing Dependencies of a Package =====
: You can use the '''apt-cache''' command to list the dependencies of a specific package without installing it.

:* To list the dependencies, run:

<code>apt-cache depends package-name</code>

:* Replace "package-name" with the appropriate package name.

===== Listing Reverse Dependencies=====
: Reverse dependencies are packages that depend on a specific package. You can list them using the 'apt-cache' command.

:* To list reverse dependencies, run:

<code>apt-cache rdepends package-name</code>

Replace "package-name" with the appropriate package name.

====Create a deb package====

====Create deb repository====

===Snaps===

Ubuntu Snap packages are a universal packaging format designed to work across different Linux distributions. Snap packages are self-contained and automatically updated, which makes them a convenient choice for both sysadmins and new users. Here's an in-depth guide to help you understand and use Snap packages in Ubuntu:

==== Installation of Snapd:====

Before you can manage Snap packages, you need to have the snapd service installed on your Ubuntu system. It usually comes pre-installed on recent versions of Ubuntu.

Check <b>snapd</b> is installed on your system with:<br>
<code>snap --version</code>

However, if it's not installed, you can install it using the following command:

<pre>
sudo apt update
sudo apt install snapd
</pre>

==== Searching for Snap packages:====

To search for available Snap packages, use the snap find command followed by a keyword:

<code>snap find <keyword></code>

Replace <keyword> with the name or keyword related to the package you are looking for.

==== Installing Snap packages:====

To install a Snap package, use the snap install command:

<code>sudo snap install <snap-package-name></code>

Replace <snap-package-name> with the exact name of the Snap package you want to install.

==== Listing installed Snap packages:====

To see a list of installed Snap packages on your system, use the snap list command:

<code>snap list</code>

==== Updating Snap packages====

Snap packages are updated automatically by default. However, if you want to manually update a specific Snap package, you can use the snap refresh command:

<code>sudo snap refresh <snap-package-name></code>

To update all Snap packages on your system, simply run:

<code>sudo snap refresh</code>

==== Removing Snap packages====

To remove an installed Snap package, use the snap remove command:

<code>sudo snap remove <snap-package-name></code>

Replace <snap-package-name> with the exact name of the Snap package you want to remove.

==== Removing Snap and also delete the package's data and configuration files====

<code>snap remove --purge example_package</code>

: The --purge option is used to specify that you not only want to remove the snap package, but also to delete its associated data and configuration files. This option helps ensure that all remnants of the package are removed from your system, providing a clean uninstall.

====Managing Snap package services====

Some Snap packages provide system services. You can manage these services using the snap services command:

<code>snap services</code>

This will list all services provided by installed Snap packages.

To start, stop, restart, or check the status of a Snap service, use the following commands:

<pre>
sudo snap start <snap-package-name>
sudo snap stop <snap-package-name>
sudo snap restart <snap-package-name>
sudo snap status <snap-package-name>
</pre>

Replace <snap-package-name> with the exact name of the Snap package containing the service you want to manage.

====Snap package channels====

Snap packages are distributed through different channels, such as stable, candidate, beta, and edge. By default, the stable channel is used. To install a Snap package from a specific channel, use the --channel option:

<code>sudo snap install <snap-package-name> --channel=<channel-name></code>

Replace <snap-package-name> with the name of the Snap package and <channel-name> with the desired channel (e.g., stable, candidate, beta, or edge).

For more information and advanced options, you can refer to the official Snapcraft documentation: https://snapcraft.io/docs

====Create a snap package====

===AppImage===

====Using Terminal====
* Make executable
<code>chmod +x program.AppImage</code>
* Run
<code>./program.AppImage</code>

===Flatpak===

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T12:51:24Z

Test1: /* Step 4: Connect from Your Laptop */

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>
* [[Raspberry_Pi_2_as_a_Tailscale_Exit_Node_for_Home_Network#Install_Tailscale| Use same method as PI to install to laptop]]

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== Conclusion ==

Your Raspberry Pi 2 is now a '''Tailscale exit node''', providing secure remote access to your home network. This '''RPi2 Tailscale tutorial''' is perfect for DIY VPN enthusiasts wanting to access home servers or wikis from anywhere.

Keywords: '''Raspberry Pi 2 VPN''', '''Tailscale home network''', '''headless Pi setup''', '''remote access tutorial'''.

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T12:48:27Z

Test1: /* Install Tailscale */

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
* <code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== Conclusion ==

Your Raspberry Pi 2 is now a '''Tailscale exit node''', providing secure remote access to your home network. This '''RPi2 Tailscale tutorial''' is perfect for DIY VPN enthusiasts wanting to access home servers or wikis from anywhere.

Keywords: '''Raspberry Pi 2 VPN''', '''Tailscale home network''', '''headless Pi setup''', '''remote access tutorial'''.

Raspberry Pi 2 as a Tailscale Exit Node for Home Network

2025-03-19T12:10:09Z

Test1: /* Step 4: Connect from Your Laptop */

= Raspberry Pi 2 as a Tailscale Exit Node for Home Network =

This tutorial guides you through turning a '''Raspberry Pi 2''' (RPi2) into a '''Tailscale exit node''' for secure remote access to your '''home network'''. With this setup, you can log into your home servers, edit your local wiki, or access devices from anywhere using a headless Raspberry Pi 2. Keywords: '''Raspberry Pi 2 Tailscale setup''', '''headless SSH''', '''home VPN''', '''nmap IP discovery'''.

== Overview ==

Transform your Raspberry Pi 2 into a Tailscale node to create a DIY VPN for your home network. This guide covers enabling SSH at boot for headless login, finding the Pi’s IP with <code>nmap</code>, and configuring Tailscale as an exit node for remote access to home servers and wikis.

== Prerequisites ==

* Raspberry Pi 2 with power supply and microSD card
* Ubuntu laptop (for SSH and scanning)
* Internet connection
* [https://www.raspberrypi.com/software/ Raspberry Pi Imager] installed on your computer

== Step 1: Enable SSH on Boot (Headless Setup) ==

Set up your Raspberry Pi 2 for '''headless login''' with SSH enabled at boot using the Raspberry Pi Imager.

# Download and open the '''Raspberry Pi Imager''' from [https://www.raspberrypi.com/software/ raspberrypi.com/software/].
# Select your OS (e.g., Raspberry Pi OS Lite) and storage (microSD card).
# Click the "Edit Settings" button (gear icon or three dots).
# In the "General" tab, set a '''username''' and '''password'''.
# In the "Services" tab, check '''Enable SSH'''.
# Choose "Use password authentication" (or "public-key" if preferred).
# Click "Save" and write the image to the SD card.

This ensures your RPi2 is SSH-ready without a monitor—perfect for a '''headless Raspberry Pi setup'''.

== Step 2: Find the Raspberry Pi IP with nmap ==

Locate your Raspberry Pi 2’s IP address on your home network using <code>nmap</code> from an Ubuntu laptop.

=== Install nmap ===

<pre>
sudo apt install nmap
</pre>

=== Identify Your Router IP ===

<pre>
ip route | grep default
</pre>

Example output:
<pre>
default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.40 metric 600
</pre>

* Router IP: <code>192.168.0.1</code>
* Laptop IP: <code>192.168.0.40</code>

=== Scan the Network ===

Scan your network before booting the Pi:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

Example output:
<pre>
Starting Nmap 7.94SVN ( https://nmap.org ) at 2025-03-03 10:07 GMT
Nmap scan report for _gateway (192.168.0.1)
Host is up (0.0038s latency).
MAC Address: AC:F8:CC:DD:EE:FF (Arris Group)
Nmap scan report for 192.168.0.40
Host is up.
Nmap done: 256 IP addresses (12 hosts up) scanned in 2.68 seconds
</pre>

Boot your Raspberry Pi 2, wait 2-3 minutes, and scan again:
<pre>
sudo nmap -sn 192.168.0.1/24
</pre>

New device appears:
<pre>
Nmap scan report for 192.168.0.69
Host is up (0.015s latency).
MAC Address: B8:17:CC:DD:CC:BB (Raspberry Pi Foundation)
</pre>

* RPi2 IP: <code>192.168.0.69</code> (note this for SSH).

This '''nmap IP discovery''' method is ideal for headless Raspberry Pi projects.

== Step 3: Set Up Tailscale on the Raspberry Pi 2 ==

Log into your RPi2 and configure it as a '''Tailscale exit node''' for your home network.

=== SSH into the Pi ===

<pre>
ssh $USER@192.168.0.69
</pre>

Replace <code>$USER</code> with the username set in Step 1.

=== Install Tailscale ===

Add Tailscale’s repository with these commands (run each line separately):
<code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.noarmor.gpg | sudo tee /usr/share/keyrings/tailscale-archive-keyring.gpg >/dev/null</code><br>
<code>curl -fsSL https://pkgs.tailscale.com/stable/debian/bookworm.tailscale-keyring.list | sudo tee /etc/apt/sources.list.d/tailscale.list</code>

Update and install:
<pre>
sudo apt update
</pre>
<pre>
sudo apt install tailscale
</pre>

=== Enable IP Forwarding ===

Enable IP forwarding for the exit node (run each line):
<code>echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.conf</code><br>
<code>sudo sysctl -p /etc/sysctl.conf</code>

=== Start Tailscale as an Exit Node ===

Run Tailscale and advertise your home network:
<pre>
sudo tailscale up --accept-routes --advertise-routes=192.168.0.0/24 --advertise-exit-node
</pre>

Copy the authentication URL output, paste it into a browser, and log in with your Tailscale account.

Get the Tailscale IP:
<pre>
tailscale ip -4
</pre>

Example output: <code>100.115.103.24</code> (yours will differ).

== Step 4: Connect from Your Laptop ==
NOTE: you can find your device IP's from <code>https://login.tailscale.com/admin/machines</code>

Use your laptop as a Tailscale client to access your home network via the RPi2 exit node.

<pre>
sudo tailscale up --exit-node=100.115.103.24 --exit-node-allow-lan-access
</pre>

* Replace <code>100.115.103.24</code> with your Pi’s Tailscale IP.

To disconnect:
<pre>
sudo tailscale down
</pre>

== Step 5: Test the Setup ==

Verify the exit node works:
<pre>
curl ifconfig.me
</pre>

Compare the IP when connected via your home Wi-Fi vs. a mobile hotspot. You should see your home public IP when using the exit node. Now, you can browse your '''local wiki''', log into '''home servers''', or access devices on <code>192.168.0.0/24</code>.

== Troubleshooting ==

* '''SSH fails:''' Ensure the username/password match Step 1 settings.
* '''Tailscale not connecting:''' Check your Tailscale account and re-authenticate.
* '''IP not found:''' Re-run <code>nmap</code> or check your router’s DHCP list.

== Conclusion ==

Your Raspberry Pi 2 is now a '''Tailscale exit node''', providing secure remote access to your home network. This '''RPi2 Tailscale tutorial''' is perfect for DIY VPN enthusiasts wanting to access home servers or wikis from anywhere.

Keywords: '''Raspberry Pi 2 VPN''', '''Tailscale home network''', '''headless Pi setup''', '''remote access tutorial'''.

Request signup open

2024-04-25T10:03:41Z

Test1: Created page with "Greetings Fellow Noobs I been about a year since signups where disabled due to bots. Just re-enabled and somethings seem to have changed and have small bug i have to solve. Currently signups can be done using '''''request account''''', in bios section just say something like 'hey there i am not a bot fellow noob' and i will approve your sign up. when you receive an email to verify email it will come with bug i have not had time to fix/solve (at current time) <pre>..."

Greetings Fellow Noobs

I been about a year since signups where disabled due to bots. Just re-enabled and somethings seem to have changed and have small bug i have to solve.

Currently signups can be done using '''''request account''''', in bios section just say something like 'hey there i am not a bot fellow noob' and i will approve your sign up.

when you receive an email to verify email it will come with bug i have not had time to fix/solve (at current time)

<pre>
http:///noobs/index.php?title=Special:RequestAccount&action=confirmemail&wpEmailToken=3867840feafj04357255f21d5f8a7fa1
</pre>

append <code>completenoobs.com</code> and click link

<pre>
http://completenoobs.com/noobs/index.php?title=Special:RequestAccount&action=confirmemail&wpEmailToken=3867840feafj04357255f21d5f8a7fa1
</pre>

Main Page

2024-04-25T08:44:35Z

Test1: /* In Concept Mode */

=In Concept Mode=

'''Site is Currently under going some changes'''<br>
Page links might be broken while we restructure page titles and content, before carrying on with content creation.

<div class="toccolours mw-collapsible mw-collapsed">
'''''DISCLAIMER:'''''
<div class="mw-collapsible-content">
he content provided on completenoobs.com is for general informational and educational purposes only. The website owner and authors make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

In no event will the website owner or authors be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website.

Through this website you are able to link to other websites which are not under the control of completenoobs.com. We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.

Every effort is made to keep the website up and running smoothly. However, completenoobs.com takes no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control.

</div>
</div>

=Welcome to CompleteNoobs=
''A community-driven resource for computer science enthusiasts''

'''Note''': At present, direct signups are disabled due to bot activity. To create an account on the wiki, please request an account and message user CompleteNoobs on Reddit. Your patience is appreciated as we may not be online all the time.

==We All Start as Noobs==

''Greetings, fellow Noobs.''

CompleteNoobs is currently in its concept stage, and we are learning as we go. Use the resources provided at your own risk.

Our mission is to make computer science free, open, and reproducible for hobbyists, sysadmins, teachers, students, and anyone interested in the field. CompleteNoobs is a platform to share tutorials, documentation, walkthroughs, computer science courses, notes, and tips acquired along the way, under a Libre License that ensures the following freedoms:

:* Read
:* Edit/Modify
:* Copy
:* Share freely

'''Note''': Content licensed under '''CC BY-NC-SA''' can be hosted on the non-commercial fork: https://www.completenoobz.com

The only proprietary aspects of this site are the domain and the trademark 'CompleteNoobs'. All content is available for download as an XML file at https://xml.completenoobs.com and is Libre licensed for everyone to use.

https://ipfs.io/ipfs/QmPyUVTQa7gk8kueAnjNDtEReKZ8NnwvFLWv66aCVrq4dy

==Get Involved==

We encourage users to fork this project, download it, and keep a copy on their desktop and/or server.

:* [[Host_Your_Own_Mediawiki_Online|Host Your Own Mediawiki Online]]

:* [[Local_CompleteNoobs_Wiki|Download CompleteNoobs Wiki to your personal computer]]

===Feed Back Received===

* Clearly indicate the terminal where commands should be entered
* Break down content into smaller sections or modules
* Provide timestamps in videos for each executed command or step
* Organize steps/modules using numbers, and sub-steps within modules using letters (a, b, c, etc.)
* Create shorter, focused videos for each step to avoid excessive scrolling
* Clarify the use of terminal editors and how to set the $EDITOR variable
* Place the EDITOR section at the top of the page and link to nano and vi guide pages
* Include instructions on how to verify the completion of each step correctly
<div class="toccolours mw-collapsible mw-collapsed">
Title Syntax: Title Re-structuring for Enhanced Clarity
<div class="mw-collapsible-content">

Title Re-structuring for Enhanced Clarity

Due to varying configurations and builds of apps/programs across different OS versions, step-by-step tutorials can be challenging to follow. To improve navigation, adjust page titles to include both the OS version/name and the software used. This will account for changes across different versions.

Example of a re-structured title: "Windows 10 Pro - Adobe Photoshop CC 2021 Tutorial"

If its a small change from each version, fork page to version and make small change.<br>
If no change, still fork page to new title!
</div>
</div>

==Essential Links==
:* [[Ubuntu_Cert_Draft|Ubuntu Cert Course '''DRAFTING''']]
:* [[Command_Line_Editors#Set_$EDITOR|Set $EDITOR]]
:* [[Main_Index | Main Index Page]]
:* [[Special:AllPages | All Pages]]
:* [[Wiki_Basic_Syntax|Basic Wiki Syntax]]
:* [[COMPLETENOOBS_FUNDING | Support us by using affiliate links or by giving us donations.]]

==Data-Heavy Content==
To maintain a lightweight XML file, data-heavy content such as pictures, audio, and video can be linked using IPFS and/or Zeronet hashes.

[[IPFS_Basics|IPFS Basics]]

'''IPFS Browser Extensions''':

'''Firefox''': https://addons.mozilla.org/en-GB/firefox/addon/ipfs-companion/<br>
'''Brave''': brave://settings/ipfs and toggle on "IPFS Companion"

[[Wiki_Basic_Syntax#Youtube_extension_-_Embed_Video|Youtube Embedded Videos also work.]]

==Licenses==

[[LICENCE_HEADERS | Add a license to each page, as long as it adheres to the principles of free copying, modification, and distribution.]]
<pre>{{:LICENCE_HEADER_CC0}}</pre>
{{:LICENCE_HEADER_CC0}}

{{Special:ContributionScores/10/5}}

Main Page

2024-04-25T08:44:24Z

Test1: /* In Concept Mode */

=In Concept Mode=
test
'''Site is Currently under going some changes'''<br>
Page links might be broken while we restructure page titles and content, before carrying on with content creation.

<div class="toccolours mw-collapsible mw-collapsed">
'''''DISCLAIMER:'''''
<div class="mw-collapsible-content">
he content provided on completenoobs.com is for general informational and educational purposes only. The website owner and authors make no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability, suitability or availability with respect to the website or the information, products, services, or related graphics contained on the website for any purpose. Any reliance you place on such information is therefore strictly at your own risk.

In no event will the website owner or authors be liable for any loss or damage including without limitation, indirect or consequential loss or damage, or any loss or damage whatsoever arising from loss of data or profits arising out of, or in connection with, the use of this website.

Through this website you are able to link to other websites which are not under the control of completenoobs.com. We have no control over the nature, content and availability of those sites. The inclusion of any links does not necessarily imply a recommendation or endorse the views expressed within them.

Every effort is made to keep the website up and running smoothly. However, completenoobs.com takes no responsibility for, and will not be liable for, the website being temporarily unavailable due to technical issues beyond our control.

</div>
</div>

=Welcome to CompleteNoobs=
''A community-driven resource for computer science enthusiasts''

'''Note''': At present, direct signups are disabled due to bot activity. To create an account on the wiki, please request an account and message user CompleteNoobs on Reddit. Your patience is appreciated as we may not be online all the time.

==We All Start as Noobs==

''Greetings, fellow Noobs.''

CompleteNoobs is currently in its concept stage, and we are learning as we go. Use the resources provided at your own risk.

Our mission is to make computer science free, open, and reproducible for hobbyists, sysadmins, teachers, students, and anyone interested in the field. CompleteNoobs is a platform to share tutorials, documentation, walkthroughs, computer science courses, notes, and tips acquired along the way, under a Libre License that ensures the following freedoms:

:* Read
:* Edit/Modify
:* Copy
:* Share freely

'''Note''': Content licensed under '''CC BY-NC-SA''' can be hosted on the non-commercial fork: https://www.completenoobz.com

The only proprietary aspects of this site are the domain and the trademark 'CompleteNoobs'. All content is available for download as an XML file at https://xml.completenoobs.com and is Libre licensed for everyone to use.

https://ipfs.io/ipfs/QmPyUVTQa7gk8kueAnjNDtEReKZ8NnwvFLWv66aCVrq4dy

==Get Involved==

We encourage users to fork this project, download it, and keep a copy on their desktop and/or server.

:* [[Host_Your_Own_Mediawiki_Online|Host Your Own Mediawiki Online]]

:* [[Local_CompleteNoobs_Wiki|Download CompleteNoobs Wiki to your personal computer]]

===Feed Back Received===

* Clearly indicate the terminal where commands should be entered
* Break down content into smaller sections or modules
* Provide timestamps in videos for each executed command or step
* Organize steps/modules using numbers, and sub-steps within modules using letters (a, b, c, etc.)
* Create shorter, focused videos for each step to avoid excessive scrolling
* Clarify the use of terminal editors and how to set the $EDITOR variable
* Place the EDITOR section at the top of the page and link to nano and vi guide pages
* Include instructions on how to verify the completion of each step correctly
<div class="toccolours mw-collapsible mw-collapsed">
Title Syntax: Title Re-structuring for Enhanced Clarity
<div class="mw-collapsible-content">

Title Re-structuring for Enhanced Clarity

Due to varying configurations and builds of apps/programs across different OS versions, step-by-step tutorials can be challenging to follow. To improve navigation, adjust page titles to include both the OS version/name and the software used. This will account for changes across different versions.

Example of a re-structured title: "Windows 10 Pro - Adobe Photoshop CC 2021 Tutorial"

If its a small change from each version, fork page to version and make small change.<br>
If no change, still fork page to new title!
</div>
</div>

==Essential Links==
:* [[Ubuntu_Cert_Draft|Ubuntu Cert Course '''DRAFTING''']]
:* [[Command_Line_Editors#Set_$EDITOR|Set $EDITOR]]
:* [[Main_Index | Main Index Page]]
:* [[Special:AllPages | All Pages]]
:* [[Wiki_Basic_Syntax|Basic Wiki Syntax]]
:* [[COMPLETENOOBS_FUNDING | Support us by using affiliate links or by giving us donations.]]

==Data-Heavy Content==
To maintain a lightweight XML file, data-heavy content such as pictures, audio, and video can be linked using IPFS and/or Zeronet hashes.

[[IPFS_Basics|IPFS Basics]]

'''IPFS Browser Extensions''':

'''Firefox''': https://addons.mozilla.org/en-GB/firefox/addon/ipfs-companion/<br>
'''Brave''': brave://settings/ipfs and toggle on "IPFS Companion"

[[Wiki_Basic_Syntax#Youtube_extension_-_Embed_Video|Youtube Embedded Videos also work.]]

==Licenses==

[[LICENCE_HEADERS | Add a license to each page, as long as it adheres to the principles of free copying, modification, and distribution.]]
<pre>{{:LICENCE_HEADER_CC0}}</pre>
{{:LICENCE_HEADER_CC0}}

{{Special:ContributionScores/10/5}}