Introduction

In the age of increasing cyber threats and privacy concerns, it has become crucial for individuals to secure their home networks. While most people rely on default routers provided by their Internet Service Providers (ISPs), these devices often lack essential features and may not receive timely updates. In this blog post, we will explore two powerful open-source firewall solutions, pfSense and OPNsense, and the compelling reasons to use them to fortify your home network’s security.

1. Comprehensive Security Features

Unlike default routers, pfSense and OPNsense are specialized firewall distributions based on FreeBSD. They offer a plethora of advanced security features that go beyond the capabilities of regular consumer-grade routers. These include stateful packet filtering, intrusion detection/prevention, Virtual Private Network (VPN) support, DNS filtering, and more. By employing these robust features, users can effectively protect their networks from malicious activities and unauthorized access.

2. Regular Updates and Security Patches

One of the most significant drawbacks of using default routers is the infrequent or non-existent software updates. Cyber threats evolve rapidly, and without timely updates, your router becomes vulnerable to new exploits and vulnerabilities. Both pfSense and OPNsense have active communities that continuously work on improving the security and stability of their platforms. Regular updates ensure that your firewall remains up-to-date with the latest security patches, safeguarding your home network from potential threats.

3. Flexibility and Customization

One of the key advantages of open-source solutions like pfSense and OPNsense is their high level of flexibility and customization options. Users can tailor their firewall settings and rules according to their specific needs, creating a personalized security infrastructure. Whether it’s setting up VLANs for segmented networks, creating access controls, or integrating third-party plugins, the ability to customize your firewall enhances the overall security posture of your home network.

4. Enhanced VPN Capabilities

In today’s interconnected world, the need for secure remote access is more prominent than ever. Both pfSense and OPNsense offer powerful VPN capabilities, allowing users to establish secure connections between remote devices and the home network. Whether you need to access your home resources while traveling or want to encrypt your online activities, these firewall solutions provide a reliable and straightforward VPN setup.

5. Community Support and Documentation

pfSense and OPNsense boast vibrant communities that actively contribute to user forums, offer advice, and share their expertise. If you encounter any issues or need guidance on setting up specific features, chances are you’ll find a wealth of information through their community support channels. Furthermore, both projects maintain extensive documentation, making it easier for users to understand and utilize the vast array of features these firewalls offer.

6. Transparency and Open-Source Assurance

Default routers typically run on closed-source firmware, making it challenging for users to scrutinize the code for potential security flaws or backdoors. In contrast, pfSense and OPNsense are open-source projects, which means their source code is publicly available for review by anyone. This level of transparency fosters trust among users, ensuring that there are no hidden vulnerabilities or privacy concerns within the firewall software.

Conclusion

In conclusion, upgrading from a default router to a robust and feature-rich firewall like pfSense or OPNsense can significantly enhance your home network’s security. By leveraging their comprehensive security features, receiving regular updates, and enjoying the flexibility of customization, you can better protect your network and data from potential cyber threats. Additionally, the strong community support, extensive documentation, and open-source assurance offer an added layer of confidence in the security of these firewall solutions. So, why settle for an outdated and vulnerable router when you can empower your home network with the cutting-edge protection of pfSense or OPNsense?

Introduction:
Searxng is a privacy-friendly and open-source metasearch engine that aggregates search results from various sources. In this guide, we’ll walk you through the process of installing Searxng on an ARM64 architecture using Docker, allowing you to set up your own search engine.

Step 1: Install Searxng with Docker

To install Searxng and run it in Docker on ARM64, execute the following command:

docker run -d -p 8888:8080 \
  --name=searxng \
  -v "searxng_data:/etc/searx" \
  -v "searxng_data:/etc/searxng" \
  -e "BASE_URL=http://192.168.0.224:8888" \
  -e "INSTANCE_NAME=searxng" \
  searxng/searxng:latest

Explanation of options used:

• -d: Run the container in the background (detached mode).
• -p 8888:8080: Map port 8080 from the container to port 8888 on the host system. This allows you to access Searxng’s web interface at http://localhost:8888.
• --name=searxng: Assign the name “searxng” to the container for easy management.
• -v "searxng_data:/etc/searx": Create a Docker volume named “searxng_data” and mount it to the “/etc/searx” directory inside the container. This volume allows you to persist Searxng’s data and configurations.
• -e "BASE_URL=http://192.168.0.224:8888": Set the base URL for the Searxng instance. Replace “192.168.0.224” with the IP address or domain name of your server.
• -e "INSTANCE_NAME=searxng": Specify a custom name for the Searxng instance.

Step 2: Access Searxng Web Interface

Once the Searxng container is up and running, open a web browser and navigate to http://localhost:8888. You will be directed to Searxng’s web interface, where you can perform searches and explore the search engine’s features.

Conclusion:
By following these steps and using Docker, you have successfully installed Searxng on an ARM64 architecture. You now have your own private search engine, Searxng, up and running, allowing you to search the web with enhanced privacy and control.

Enjoy the benefits of Searxng and have fun searching! Happy exploring!

Introduction:
Pi-hole is a popular network-level ad blocker that helps you block advertisements at the DNS level. With Docker, you can easily deploy Pi-hole on your network for ad-free browsing on all your connected devices. In this guide, we’ll walk you through the process of setting up Pi-hole using Docker.

Step 1: Install Pi-hole with Docker

To install Pi-hole and run it in Docker, execute the following command:

docker run -d --name=pihole \
  -e TZ=Europe/Copenhagen \
  -e WEBPASSWORD=xxxxxxx \
  -e SERVERIP=192.168.0.224 \
  -e FTLCONF_LOCAL_IPV4=192.168.0.227 \
  -v pihole_data:/etc/pihole \
  -v pihole_dnsmasq:/etc/dnsmasq.d \
  -p 81:80 \
  -p 53:53/tcp \
  -p 53:53/udp \
  --net=host \
  --restart=unless-stopped \
  pihole/pihole:latest

Explanation of options used:

• -d: Run the container in the background (detached mode).
• --name=pihole: Assign the name “pihole” to the container for easy management.
• -e TZ=Europe/Copenhagen: Set the timezone to “Europe/Copenhagen” inside the container.
• -e WEBPASSWORD=xxxxxxx: Set a custom web admin password for Pi-hole. Replace “xxxxxxx” with your desired password.
• -e SERVERIP=192.168.0.224: Set the IP address of the Docker host (Raspberry Pi) where Pi-hole will run. Replace “192.168.0.224” with your Raspberry Pi’s IP address.
• -v pihole_data:/etc/pihole: Create a Docker volume named “pihole_data” and mount it to the “/etc/pihole” directory inside the container. This volume allows you to persist Pi-hole’s data and configurations.
• -v pihole_dnsmasq:/etc/dnsmasq.d: Create a Docker volume named “pihole_dnsmasq” and mount it to the “/etc/dnsmasq.d” directory inside the container. This volume is used to customize DNS settings and blocklists.
• -p 81:80: Map port 80 from the container to port 81 on the host system. This allows you to access Pi-hole’s web interface at http://localhost:81.
• -p 53:53/tcp -p 53:53/udp: Map port 53 from the container to both TCP and UDP port 53 on the host system. This enables Pi-hole to handle DNS requests. Or “–net=host \” for local network install.
• --restart=unless-stopped: Configure the container to automatically restart if it stops unexpectedly.
• pihole/pihole:v5.6: Specifies the Docker image to use for running Pi-hole (version 5.6).

Step 2: Access Pi-hole Web Interface

Once the Pi-hole container is up and running, open a web browser and navigate to http://localhost:81. You will be directed to Pi-hole’s web interface. Use the custom web admin password you set in the Docker command to log in.

Congratulations! You have successfully deployed Pi-hole on your network using Docker. Your network devices will now benefit from network-wide ad blocking, providing a seamless and ad-free browsing experience.

Remember to configure your devices to use your Raspberry Pi’s IP address (192.168.0.224) as the DNS server to take advantage of Pi-hole’s ad-blocking capabilities.

Enjoy ad-free browsing and network-level ad blocking with Pi-hole and Docker! Happy browsing!

Introduction:
Pi.Alert is a powerful application for Raspberry Pi that enables you to monitor and control your network devices. In this guide, we’ll walk you through the process of setting up Pi.Alert using Docker. We’ll cover two deployment options, each with its own configuration.

Step 1: Deploy Pi.Alert with Docker and Persistent Data

To deploy Pi.Alert with persistent data, use the following Docker command:

docker run --name pialert -d \
  -v pialert_data:/home/pi/pialert/db \
  -v pialert_config:/home/pi/pialert/config \
  --net=host \
  jokobsk/pi.alert:latest

Explanation of options used:

• --name pialert: Assigns the name “pialert” to the container for easy management.
• -d: Runs the container in the background (detached mode).
• -v pialert_data:/home/pi/pialert/db: Creates a Docker volume named “pialert_data” and mounts it to the “/home/pi/pialert/db” directory inside the container to persist data.
• -v pialert_config:/home/pi/pialert/config: Creates a Docker volume named “pialert_config” and mounts it to the “/home/pi/pialert/config” directory inside the container to provide configuration data.
• --net=host: Utilizes the host’s network stack for efficient communication with other services on the Raspberry Pi.
• jokobsk/pi.alert:latest: Specifies the Docker image to use for running the Pi.Alert application.

Step 2: Deploy Pi.Alert with Docker and Environment Variables

To deploy Pi.Alert with environment variables, use the following Docker command:

docker run --name pialert -d --network=host \
  -v pialert_config:/home/pi/pialert/config \
  -v pialert_data:/home/pi/pialert/db \
  -e TZ=Europe/Berlin \
  -e PORT=20211 \
  jokobsk/pi.alert:latest

Explanation of options used:

• --name pialert: Assigns the name “pialert” to the container for easy management.
• -d: Runs the container in the background (detached mode).
• --network=host: Uses the host network stack for efficient communication with other services on the Raspberry Pi.
• -v pialert_config:/home/pi/pialert/config: Creates a Docker volume named “pialert_config” and mounts it to the “/home/pi/pialert/config” directory inside the container to provide configuration data.
• -v pialert_data:/home/pi/pialert/db: Creates a Docker volume named “pialert_data” and mounts it to the “/home/pi/pialert/db” directory inside the container to persist data.
• -e TZ=Europe/Berlin: Sets the timezone to “Europe/Berlin” inside the container.
• -e PORT=20211: Sets the environment variable “PORT” to the value “20211” inside the container.
• jokobsk/pi.alert:latest: Specifies the Docker image to use for running the Pi.Alert application.

Remember to configure your network settings by adding “192.168.0.1/24” under settings and saving the changes before running the container.

Conclusion:
You have successfully deployed Pi.Alert on your Raspberry Pi using Docker. Whether you chose the option with persistent data or environment variables, Pi.Alert is now ready to help you monitor and manage your network devices.

Explore Pi.Alert’s features and start enhancing your network management capabilities today! Happy monitoring!

Introduction:
ntopng is a network traffic analysis tool that provides detailed real-time insights into your network’s traffic. By using Docker, you can easily deploy ntopng with its required configurations. In this guide, we’ll show you how to set up ntopng using Docker with the necessary parameters for network monitoring.

Step 1: Install Docker
Before proceeding, ensure you have Docker installed on your system. If you haven’t installed Docker yet, follow the official Docker installation instructions for your operating system.

Step 2: Run ntopng Docker Container
Run the following command to create and start the ntopng Docker container:

docker run -it \
--name ntopng \
-p 3000:3000/tcp \
-p 2055:2055/udp \
-e ACCOUNTID="xxxxx" \
-e LICENSEKEY="xxxxxxxxx" \
-e LOCALNET="192.168.0.0/24" \
-v ntopng_data:/var/lib/ntopng \
--restart unless-stopped \
--net=host \
phantomski/ntopng

Explanation of options used:

• -it: Allocate a pseudo-TTY and keep STDIN open, allowing you to interact with the ntopng console if needed.
• --name ntopng: Assign the name “ntopng” to the container for easy management.
• -p 3000:3000/tcp: Map port 3000 from the container to the host system. This allows you to access the ntopng web interface at http://localhost:3000.
• -p 2055:2055/udp: Map port 2055 from the container to the host system. This is used for ntopng to receive NetFlow/sFlow data from devices on the network.
• -e ACCOUNTID="xxxxxx": Set the ntopng Account ID. Replace “xxxxx” with your ntopng account ID obtained from the ntopng website.
• -e LICENSEKEY="xxxxxxxxxx": Set the ntopng License Key. Replace “xxxxxxxxx” with your ntopng license key obtained from the ntopng website.
• -e LOCALNET="192.168.0.0/24": Specify the local network to be monitored. Replace “192.168.0.0/24” with your network’s subnet.
• -v ntopng_data:/var/lib/ntopng: Create a Docker volume named “ntopng_data” and mount it to the /var/lib/ntopng directory inside the container. This volume allows you to persist ntopng data and configurations.
• --restart unless-stopped: Configure the container to automatically restart if it stops unexpectedly.
• --net=host: Use the host’s network stack to simplify network configuration and improve performance.

Step 3: Access ntopng Web Interface
Once the ntopng container is running, you can access the ntopng web interface by opening a web browser and navigating to http://localhost:3000. From here, you can explore the real-time network traffic data and analytics provided by ntopng.

Conclusion:
You’ve successfully set up ntopng with Docker, allowing you to monitor and analyze network traffic in real-time. ntopng’s web interface provides comprehensive insights into your network, helping you identify and troubleshoot potential issues. With Docker, managing ntopng becomes easier, and you can quickly deploy it in your network environment.

Happy network monitoring!

Introduction:
Kali Linux is a popular penetration testing and ethical hacking distribution. With Docker, you can run Kali Linux in a containerized environment, making it easy to experiment and perform security assessments. In this guide, we’ll show you how to run Kali Linux as a Docker container and access it interactively.

Step 1: Install Docker
Before proceeding, make sure you have Docker installed on your system. If you haven’t installed Docker yet, follow the official Docker installation instructions for your operating system.

Step 2: Pull Kali Linux Docker Image
To run Kali Linux, pull the latest Kali Linux Docker image from Docker Hub using the following command:

docker pull kalilinux/kali-rolling

Step 3: Create and Start Kali Linux Container
Run the following command to create and start a Kali Linux container:

docker run -d --name=kalilinux -v kalilinux_data:/data --tty --interactive kalilinux/kali-rolling

Explanation of options used:

• -d: Run the container in the background (detached mode).
• --name=kalilinux: Assign the name “kalilinux” to the container for easy management.
• -v kalilinux_data:/data: Create a Docker volume named “kalilinux_data” and mount it to the /data directory inside the container. This volume allows you to persist data and configuration between container restarts.
• --tty: Allocate a pseudo-TTY, which enables interactive access to the container’s terminal.
• --interactive: Keep STDIN open even if not attached. This allows you to interact with the container’s terminal.

Step 4: Access the Kali Linux Container
To access the Kali Linux container interactively, use the following command:

docker exec -it kalilinux bash

This command will attach your current terminal to the running Kali Linux container, providing you with an interactive shell inside the container.

Step 5: Clean Up
If you want to stop and remove the Kali Linux container and the associated volume, use the following commands:

docker stop kalilinux
docker rm kalilinux
docker volume rm kalilinux_data

Conclusion:
You’ve successfully run Kali Linux in a Docker container, allowing you to perform security assessments and penetration testing in an isolated environment. Docker enables easy management and deployment of Kali Linux, making it an excellent choice for testing and experimenting with various tools and configurations.

Happy hacking!