7 Followers
35 Following
28 Posts

๐Ÿง™โ€โ™‚๏ธ Code Whisperer
๐Ÿ‘ทโ€โ™‚๏ธ Software Architect
โžฟ Process Engineer
โ™ป๏ธ Change Architect
๐Ÿ’Ž Quality Advocate

Interests:
๐Ÿ†“ #FOSS #OpenSource projects
๐Ÿ•ธ๏ธ #Decentralized services
๐Ÿ’ช #SelfHosting
๐Ÿ•ถ๏ธ #Privacy
๐Ÿ‘จโ€๐Ÿ’ป #DevSecOps
๐Ÿ•ต๏ธ #CyberSecurity #InfoSec

#LinuxPhone #Tech #Web3 #PHP #NodeJS #Ansible #ESP32 #LoRa

Operation Slabtop: The second life of the workstation as a satellite in the Zero-Trust architecture

The life cycle of IT equipment can be ruthless. The machine that a few years ago compiled powerful monoliths and enabled the design of micro-service systems without a hitch, today, in the era of local LLMs and distributed artificial intelligence clusters, seems to be running out of breath. But in the world of DevOps and private labs, throwing away functional silicon isn't just wasteful - it's a sin against engineering optimization.

Today, a veteran hits the operating table: Dell Precision 5520. However, instead of condemning it to gathering dust in a closet or being disposed of, we will perform a drastic hardware modification and include it in the home, independent ecosystem as a critical satellite node. We break away from the digital feudalism of public clouds by building infrastructure on our own terms.

Silicon under the microscope: Why this model?

Before we get into the cutting, let's look at the specs. This is not an ordinary consumer laptop limited by the thermals of cheap plastic. The heart of this machine is Intel Xeon E3-1505M v6. This is a key detail.

The presence of Xeon architecture in a mobile workstation is a game changer in the server context. This gives us important advantages:

  • Intel vPro / AMT (Active Management Technology): This is an absolute gamechanger for the home lab. It is hardware out-of-band management embedded in the motherboard. Thanks to AMT, we can manage the machine, reset it, diagnose it, and even enter the BIOS over the network (KVM over IP), even if the operating system (Ubuntu/Debian) completely crashes or the machine suffers a kernel panic. This is functionality known from powerful servers, enclosed in a laptop disc.
  • Higher bionized silicon: Xeons are typically systems with higher thermal tolerance and better stability under 24/7 multi-threaded loads compared to standard Core series processors.

The Myth of ECC in Slim Workstations (Hardware Warning)
At this point, it is worth debunking a popular myth that many engineers worry about. Although the Xeon E3-1505M v6 processor itself natively supports error correction (ECC), Dell has not implemented this support on the 5520 motherboard. This is a twin case with the XPS 15, where ECC paths were abandoned in favor of miniaturization (unlike the thicker Precision 7520 series). We stay with the proven, maximum 32 GB of fast non-ECC RAM.

There is also an NVIDIA Quadro M1200 chip inside. And although its architecture (Maxwell) is too old (Compute Capability 5.0) to run modern agent or vLLM engines (we delegate these tasks to dedicated nodes of the Blackwell AI cluster), it is still a powerful coprocessor for hardware decoding of video streams (NVDEC) or running smaller, local computer vision models (Computer Vision).

Cyberpunk Surgery, or the construction of "Slabtop"

A laptop as a server has a phenomenal power to current ratio and a built-in "UPS" in the form of a battery. However, a lithium-ion battery locked in a rack cabinet and connected to the power supply 24/7 is a ticking firebomb (so-called spicy pillow).

So we create Slabtop (flat screenless server). The procedure is simple but brutal:

  • BIOS Config: Set AC Recovery to Power On, ignore keyboard and matrix missing errors during POST.
  • Power amputation: Open the bottom cover and absolutely remove the battery. From now on, the machine relies solely on the external power supply and the main UPS of our laboratory.
  • Decapitation: Unscrew the hinges and unfasten the eDP tape. The 4K screen, which was a power eater, goes to the drawer (or for parts).
  • Thermal optimization: Disassemble the keyboard. The exposed motherboard and processor repasting (e.g. PTM7950) will allow the cooling system to operate almost silently. The hob releases heat directly to the surroundings.
  • In this way, we get a perfectly flat, one-piece computing node in the fractional 1U format, which consumes only a few or a dozen or so watts at idle.

    Architecture: Where to connect Xeon in a modern lab?

    With the main orchestrator and firewall in the network (e.g. an R3930 class machine) and heavy nodes accelerated by modern GPUs, our Slabtop 5520 should not fight for the title of the main server. Its strength lies in its asymmetry and isolation. It becomes a satellite machine.

    Here are two ideal roles for this machine, managed entirely by code (Ansible + Docker Compose):

    Role 1: SecOps and Observability Bastion (Out-of-band Monitoring)

    The golden rule of infrastructure is: never keep monitoring systems on the same machine you are monitoring. When your main cluster fails under load or due to a network configuration error, you need to know why.

    • Xeon E3-1505M will handle log aggregation perfectly.
    • We implement the full observability stack on it: Prometheus, Grafana, Loki.
    • The machine listens for events from the master orchestrator. If the temperatures on the AI โ€‹โ€‹clusters increase, our 5520 sends an alert to the Home Assistant. If a critical agent fails, it sends an encrypted message to the Session messenger.

    Role 2: "Knowledge OS" Engine

    Instead of relying on external cloud services, Slabtop becomes the guardian of your private knowledge management system.

    • This is the perfect place to host a local server with a non-linear note graph (Zettelkasten).
    • We run automated CI/CD processes (e.g. lightweight runner) which, with each git push, compiles a static blog (Hugo) from the latest architectural notes and replicates it securely to an external proxy.

    Summary: Code, Silicon and Control

    This project is proof that in the world of "Infrastructure as Code" hardware never dies - it simply changes its role. The Dell Precision 5520 with a Xeon processor and built-in out-of-band management, reduced to raw silicon and aluminum, is the perfect, silent security node.

    Instead of adding another point of failure in the cloud, we closed the circuit in our own lab. Pure pragmatism, full control over data and an infrastructure that works for us, not us for it. And all this without a subscription.

    #homelab #slabtop #ITUpcycling #HardwareRecycling #HardwareModding

    From Digital Neofeudalism to Sovereignty: How I Built My Own Knowledge Operating System

    Most of us live today in a state of digital neofeudalism. We have become digital sharecroppers: our notes, thoughts, and technical documentation are "leased" from large SaaS corporations. If Notion goes down, your knowledge disappears. If Evernote changes its terms and conditions, your data becomes hostage.

    I decided to say "enough." I built a system that is 100% mine, self-documenting code, and works the way I think: nonlinear.

    ๐Ÿง  Knowledge Architecture: A Network Instead of a List

    A traditional blog is a list. My knowledge base is a graph. I use Markdown and the Zettelkasten approach to create a network of connections. Thanks to Hugo (@gohugoio), each note knows who links to it.

    How does it work?

    One article contains reasons, which are the titles of separate publications. These, in turn, have backlinks like "this motivated me to...".

    graph TD
    A[homelab.md] -->|why?| B[digital-neofeudalism.md]
    A -->|business model| C[digital-sharecroppers.md]
    B -->|solution| A
    C -->|motivation| A

    I use transclusion (include) to inject fragments of technical documentation where they're needed. No more "copy-paste."

    ๐Ÿ—๏ธ Hardware: Division of roles in the ecosystem

    My homelab isn't one big server. It's specialized units:

    | Machine | Role | Characteristics |
    | --- | --- | --- |
    | R3930 | Workhorse | heavy containers, databases. |
    | Wyse 5070 | Guardian | DNS (Pi-hole), Proxy, SSO (Authelia). |
    | DELL GB10 | AI Accelerator Cluster | LLM. |
    | Laptop | Command Center | This is where the code is written, and this is where Ansible runs. |

    Why is the Gateway (Proxy/SSO) on a small Wyse? Because it's quiet, energy-efficient, and supposed to run 24/7, even when the "workhorse" is resting.

    ๐Ÿ› ๏ธ Infrastructure as Code (Ansible)

    I don't configure servers manually. Everything is defined by SSoT (Single Source of Truth) in YAML. One file describes the entire lab:

    services:
    - id: "technical-docs"
    name: "Wiki"
    fqdn: "docs.lab.arpa"
    target_host: "R3930"
    is_private: false
    category: "Knowledge"

    Ansible takes this list and:

  • Deploys the container on the appropriate host.
  • Configures nginx-proxy on the Wyse to route traffic to R3930.
  • Injects authorization rules into Authelia.
  • Updates the Homepage dashboard.
  • ๐Ÿ”’ Security: SSO and Custom CA

    Let's Encrypt has no place on the .arpa network. I built my own Certificate Authority (Own CA) based on Smallstep.

    • Authelia (SSO): One login and password (plus 2FA) to access all private services.
    • Smallstep SSL: Every service in the *.lab.arpa domain has a "green padlock." Ansible ensures that my laptop and all servers trust my Root CA.

    Development Challenge: Automating SSL via the ACME protocol on my own network is pure magic. Nginx automatically requests a certificate from the local CA server. Without accessing the internet.

    ๐Ÿ“Š Result: Dashboard

    The end result is the Homepage โ€“ a dashboard that generates automatically. I can see every service, its status, and information about which physical hardware it currently resides on.

    ๐Ÿšฉ What's next?

    My knowledge operating system is growing, but it has one weak point. If the Wyse DNS server goes down, I'm out. So in the next post, we'll cover DNS2 redundancy and data synchronization using Gravity Sync.

    Homelab isn't a goal, it's a process. And you? Are you still working your tail off in the cloud?

    #DigitalIndependence #OpenSource #SelfHosting #DataPrivacy #TechFreedom #BuildingTheFuture
    #DigitalNeofeudalism #DigitalSharecroppers #KnowledgeOperatingSystem #Ansible #Homelab

    The time for a change had come

    I came across Framework Laptop a long time ago and was very intrigued, but it was missing that special something. When it came time to decide on a new laptop, everything fell into place. I already had my DELL configuration ready, but then I saw the new 13 Pro.

    Why did I finally decide on Framework?

    The introduction of a fingerprint reader, the use of fast, removable LPCAMM2 memory, and that distinctive, retro style that recalls the days when the hardware was "anything" โ€“ that's what finally won me over. It was the answer to my frustrations from the past. I remember laptops where burnt traces on the motherboard would first manifest themselves in failing USB ports, and then end up completely dying after a few minutes of use. Having trouble finding a replacement motherboard or battery after a few years, regardless of the brand.

    I believe that if something gets outdated or worn out, I'll simply replace it. A single component.

    The Big "Small Screen" Test: Is 13.5" Enough?

    Here's my biggest doubt. Going from a comfortable 15.6" to 13.5" is a risky move.
    Will the 3:2 aspect ratio actually compensate for the smaller diagonal? Theoretically, yes โ€“ more lines of code vertically is every back-end developer's dream. However, until the laptop arrives on my desk and I spend my first 10 hours at a coffee shop with it, I'm treating it as an experiment. The arguments about pixel density and brightness convinced me, but the final verdict will be my eyestrain after a shift with Ansible and LLMs.

    Modularity: A Return to the Era of "Fat Books" and a Challenge for the Manufacturer

    My first Dell from 2006 was as thick as an encyclopedia, but in terms of modularity, it was a masterpiece. It had a bay with an HDD that slid out from the side of the case and two palm rest trays for a 1.44" floppy drive, CD or an extra battery. It was the pinnacle of engineering freedom.

    The Framework 13 Pro almost realizes this dream with Expansion Cards. Speaking of professional dreams:

    Challenge for @frameworkcomputer

    If you can fit 1TB on an expansion card, I challenge you: Make a full-fledged card with an NVMe slot that slid out from the side of the case. I want to be able to physically eject my main drive with data in one hand, just like I did at Dell twenty years ago. That would be a real revolution.

    โœ… Pros

    • Modularity
    • Repairability
    • Biometric Reader
    • LPCAMM2 LPDDR5X 96GB
    • PCIe Gen 5.0 NVMe
    • Variable Refresh Rate 30-120Hz
    • 700 NIT Screen Brightness
    • Matte Screen
    • 3K Screen Resolution
    • 3:2 Aspect Ratio
    • Open Source Ecosystem
    • Privacy Switches

    โŒ Cons

    • No FIPS

    โ” Unknown

    • Screen Size 13.5"

    In summary: For me, the Framework 13 Pro is an investment in peace of mind, shared values, and an open community. No more fighting a closed architecture. Will the 13.5-inch be a disappointment? We'll find out soon. For now, I'm excited about the thought of returning to equipment that I can fully control.

    https://frame.work/laptop13pro

    #OpenSource #OpenCommunity #FrameworkLaptop13Pro

    It's been 9 satisfying years with the reliable Dell Precision 5520 Anniversary Edition

    Let's face it โ€“ it's still legendary. For nine years, this machine was practically bulletproof. However, time is inexorable, and the biggest enemy of longevity turned out to be not the processor, but... spare parts logistics and convenience.

    My battery story is classic: I ordered an "original" one that turned out to be a poor counterfeit. It dropped from 70% to zero in a split second, and the computer suddenly shut down in the middle of work. The second battery was already the original. Added to this was the lack of biometrics โ€“ in 2026, entering a password every time I returned to the terminal became simply tedious.

    โœ… Strengths

    • Powerful Intelยฎ Xeon(R) CPU E3-1505M v6 @ 3.00GHz x 8
    • 32GB RAM
    • 4K UHD 3840x2160
    • Thunderbolt
    • Backlit keyboard
    • 6-cell 97 Wh battery
    • Proven reliability for 9 years
    • NVIDIA Quadro M1200 Mobile (for its time)
    • Thin & light

    โŒ What bothered me

    • No fingerprint reader
    • Highly reflective glass screen with 400 NITs brightness is problematic for use on a sunny day
    • Annoying fan noise
    • Finding the original battery was sometimes problematic after such a long time since release.

    #DELLPrecision #LegendaryLaptop #MobileWorkstation

    The project of building my own smart patch panel a la "UniFi Etherlighting" is entering its final phase! ๐Ÿ› ๏ธโšก

    I already have the ESP32 and electronics, I have the 3D printing models... but I'm still missing that unique, personalized finish.

    On the front of the device will be a small, 1.3" LCD touchscreen. This will be the welcome screen when you turn it on. I've created three boot screen concepts, but I can't decide which one best captures the "Smart Rack Pro" vibe.

    Help me choose the final version. Which graphic should be used in the final vlog and on the device's screen?

    ๐Ÿ‘‡ Check out the graphics below and vote in the poll! ๐Ÿ‘‡

    Link to the POLL: https://infosec.exchange/@MaSi/115779858077099185

    #homelab #smarthome #diyproject #unifi #ubiquiti #esp32 #3dprinting #networkengineering #smartrackpro #makercommunity

    Which boot logo do you choose?
    Images in the post: https://infosec.exchange/@MaSi/115779862723109253

    Project "Smart Rack PRO".

    Option A: The Flowing Core ๐ŸŒŒ
    50%
    Option B: Network Pulse ๐Ÿ“ˆ
    37.5%
    OptionC: Cosmic Haze ๐ŸŸฃ
    12.5%
    Poll ended at .
    MaSi (@[email protected])

    Attached: 1 image The project of building my own smart patch panel a la "UniFi Etherlighting" is entering its final phase! ๐Ÿ› ๏ธโšก I already have the ESP32 and electronics, I have the 3D printing models... but I'm still missing that unique, personalized finish. On the front of the device will be a small, 1.3" LCD touchscreen. This will be the welcome screen when you turn it on. I've created three boot screen concepts, but I can't decide which one best captures the "Smart Rack Pro" vibe. Help me choose the final version. Which graphic should be used in the final vlog and on the device's screen? ๐Ÿ‘‡ Check out the graphics below and vote in the poll! ๐Ÿ‘‡ POLL: https://infosec.exchange/@MaSi/115779858077099185

    Infosec Exchange
    What is FOSS? | 7 Steps To Cyber Security And Privacy

    Want to find out about online privacy? Check out our free privacy guide to the best open source privacytools!

    2 of 10 Gbps SFP+ ๐Ÿ™„

    Do you know common issues? Performance limit?

    UDM-SE

    • port 10: 10G SFP+ to server
    • port 11: 10G DAC SFP+ to UNAS-PRO

    #UniFi #UNASPRO #UDMSE #HomeLab #SelfHosting