OpsLinuxSec

OpsLinuxSec / Infrastructure engineering

Where systems are built, broken, and understood.

OpsLinuxSec is an independent infrastructure engineering initiative from Indonesia, building and exploring networking systems, router operating systems, and practical infrastructure tools.

Explore Projects Read Engineering Notes

01 / Projects

Three repositories. Three honest maturity levels.

Each project carries the status its maintainer gives it. Technical details come from the repository itself.

IPv8

Experimental

A C11 userspace Ethernet stack for Linux that sends real frames over AF_PACKET. It includes the ip8, ping8, and traceroute8 tools, which talk to the ipv8d daemon over a UNIX socket.

An implementation of an IPv8 protocol draft, not an established Internet standard. It is not a kernel module and does not implement a complete standard.

Problem: a hands-on lab for testing how a 64-bit address space, routing, ARP-style resolution, and error messages behave when implemented from a draft.

  • C11
  • Linux
  • AF_PACKET
  • systemd
  • Make
Explore IPv8 on GitHub ↗

NeveraOS Network

In Development

An independently developed network operating system for router-oriented deployments. It is in active development and is not a stable production release.

The repository currently holds the README and license. The README marks four workstreams as in progress: Buildroot, a Linux 6.x LTS kernel, a routing engine, and a netlink engine.

Problem: building a small, purpose-made router OS on a reproducible Linux base instead of assembling one by hand.

  • Buildroot
  • Linux kernel
  • Routing
  • Netlink
Explore NeveraOS on GitHub ↗

Cloud-Init Proxmox Script

Ready to Use

An interactive Bash installer that creates a Cloud-Init VM template on a Proxmox VE host from a cloud image. It offers built-in Ubuntu, Debian, and Arch images or a custom image URL, then imports the disk and adds a Cloud-Init drive.

Run as root directly on the Proxmox VE host. The script resizes the image, so keep a copy of the original. Network and other Cloud-Init options are still set in Proxmox.

Problem: creating a template VM from a cloud image takes many qm commands. This script walks through the same steps interactively.

  • Bash
  • Proxmox VE
  • Cloud-Init
  • qm
  • libguestfs
View Script on GitHub ↗

02 / Approach

Built to be understood, not just deployed.

We explore infrastructure from the system level upward. That means examining how components interact, testing assumptions in controlled environments, documenting failures, and understanding why a system behaves the way it does.

  1. 01

    Understand the underlying system.

    Read the protocol, the kernel interface, and the packet format before relying on a higher-level tool.

  2. 02

    Test in reproducible environments.

    Use lab VMs and bridges so results can be repeated, and record which checks could not run.

  3. 03

    Document implementation details and limitations.

    State what is implemented, what is experimental, and what is not verified yet.

  4. 04

    Share practical engineering knowledge.

    Publish the steps, the failures, and the reasoning behind them on the engineering blog.

03 / Status

Development Priorities

The current priorities and known limits for each project, taken from the repositories. No formal roadmap has been published, and no dates are committed.

IPv8

Experimental
Implemented
64-bit addresses, subnet calculation, connected, static and default routes, longest-prefix match, ARP8, forwarding, Echo, Unreachable and Time Exceeded messages, and a daemon with a singleton lock.
Known limits
  • Userspace only. Addresses do not appear in ip addr.
  • No TCP/UDP, DNS, DHCP8, dynamic routing, encryption, or fragmentation.
  • Integration tests, including routed traceroute, were blocked in the most recent build environment and still need a run on lab VMs.
Next milestone
Run make test, make sanitize, and tests/ethernet.sh on the lab VMs, then confirm the ARP behavior on the Proxmox bridge.

NeveraOS Network

In Development
Current state
The repository holds a README and license. Kernel, Buildroot, routing, and CLI work is in progress and is not yet in the repository.
In progress
  • Buildroot-based system build
  • Linux 6.x LTS kernel
  • Routing engine
  • Netlink engine
Not started
FRRouting integration, CLI modes, and ISO, IMG, or QCOW2 image generation are not yet part of the project.

Cloud-Init Proxmox Script

Ready to Use
Prerequisites
Root access on a Proxmox VE host, internet access if an image is not already present, enough space in /var/lib/vz/images/, and libguestfs-tools (installed by the script if missing).
Limits
Interactive only. It does not configure networking, and it does not convert the VM to a template (use qm template <VMID>).

04 / Open source

Open infrastructure. Transparent engineering.

OpsLinuxSec shares its engineering work: the code, the build and test steps, the limits, and the write-ups behind them. Each repository is published under the MIT License, and each license is in the repository itself.

All repositories on GitHub ↗

05 / About

About OpsLinuxSec

OpsLinuxSec is an independent infrastructure engineering initiative founded by Ryan Achmad in Indonesia. It focuses on open-source networking, operating-system experiments, and practical engineering projects built through hands-on development and testing.

Ryan Achmad develops the projects above and writes about them on the engineering blog. OpsLinuxSec is not a registered company.

  • FounderRyan Achmad
  • Based inIndonesia
  • FocusNetworking, router OS, infrastructure tooling
  • Writingblog.opslinuxsec.com ↗

06 / Engineering notes

Recent writing

Notes on implementation, configuration, and debugging from the engineering blog.

All engineering notes on the blog ↗