Ir al contenido principal

When “Pre-Installed OpenWrt” Isn’t Plug-and-Play

  Lessons Learned After Finally Configuring a Raspberry Pi CM4 Mini Router (Bought in 2022) Product Mini Router built with Raspberry Pi Compute Module 4 Dual Gigabit Ethernet NICs 4GB RAM / 32GB eMMC Pre-installed OpenWrt Compact form factor, fanless, low power Background: A Device That Waited Its Turn I bought this device back in 2022 . At the time, it looked like the perfect small router: Raspberry Pi Compute Module 4 Dual Ethernet ports OpenWrt already installed No SD card required thanks to eMMC But like many homelab projects, it ended up sitting on a shelf . Fast forward to today — with more networking experience, a clearer home network plan, and a real need for a flexible router — I finally decided to configure it properly. That’s when the real journey started. What I Expected (Even in 2025) Even knowing this wasn’t a consumer router, I still expected: Plug WAN into my upstream router Plug LAN into my laptop Access 192.168.1.1 Hav...

Somos soñadores y no ganadores



Este 13 de Agosto del 2016 de mala suerte no ha tenido nada. Después de llevar una clase toda una mañana sobre manejar los conflictos en proyectos ágiles, sentarme y pasar a papel una idea que ya días estaba en la cabeza, la clasificación a semifinales de la selección olímpica me puse a pensar que nosotros los hondureños no somos personas ganadoras. Son pocos o nulos los triunfos a nivel internacional que tenemos, en deporte, ciencia, arte, etc. Pero hay algo que todo catracho tiene. Es un soñador.  Siempre tiene una sueño que seguir, y si se propone lo logra. El problema es trabajarlo, luchar por el, pero si logra superar eso, nadie nos detiene.

Les comparto este pelicula: La Meta de Eliyahu Goldratt
Una pequeña pelicula como muestra los procesos de mejora continua, como una persona lucha por un sueño, que es evitar que cierren la fabrica que el administra,


Comentarios

Entradas populares de este blog

Modern Architecture for Native Apps with AWS Backend: A Practical Guide

Introduction Designing a mobile app today goes far beyond building a beautiful interface. Native apps — whether for iOS or Android — need secure authentication, user role management, real-time communication with the backend, and scalable infrastructure to support growth. In this post, I’ll walk you through a clean and modern architecture to connect native mobile apps to a robust backend on AWS. The architecture is modular, scalable, and aligned with best practices for security and performance — without relying on overly complex tools. Why it matters: apps today are more than just UI A production-grade mobile app often includes: User login (email, Google, or others), Differentiated access for multiple roles (e.g., user vs admin), Secure token-based communication, A backend capable of handling business logic and data, Data storage, asset management, and scalable APIs, Compliance with Google Play and App Store requirements. All of these require a backend architecture ...

Understanding Liveness, Readiness and Startup Probes in Kubernetes

 This is a small article about understanding the liveness, readiness and startup in kubernetes.  There's good explanation in the kubernetes documentation: https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/ This video also explains well the process: https://www.youtube.com/watch?v=aTlQBofihJQ But I wanted to understand it in a practical way. So I have this demo: https://github.com/DiegoTc/guest-book-js-docker/tree/Running-App-Version-1 It's a simple application running on a kubernetes cluster. https://github.com/DiegoTc/guest-book-js-docker/blob/Running-App-Version-1/argo/deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: chat-ui spec: replicas: 1 revisionHistoryLimit: 3 selector: matchLabels: app: chat-ui template: metadata: labels: app: chat-ui spec: containers: - image: diegotc/guestbook:20230803-064434 imagePullPolicy: Alwa...

How I miss you Synaptic!

Several years  have passed since we saw the Synaptic included in Ubuntu. You can found reasons here  . So in a clear english the reason was to have a better add/remove program for users. A friendly application. The explanation sounds good, I didn't complain about that, until right now. Ubuntu has change a lot, it's really a friendly user OS. I have use CLI when necessary, but today I couldn't believe it. I'm a Google Chrome user, I know you will tell me it's not open source or I should use Chromium or FF. But no. I'm a user of Google Chrome, and many people also prefer Chrome over Chromium, so why it should be quite complex remove it? If Ubuntu wants to be more friendly user why you should use the terminal for removing one of the most popular web browsers? I could understand if is a browser few people use, a good reason. But not a popular browser, Chrome is one of the most popular browsers on the world! A screen shot of the Ubuntu Software Center, trying t...