Pinoy IT Share

🧩 Part 3: Connecting Your Network to AdGuard Home Configure Your Router or Devices to Use AdGuard Home Why This Step Matters Now that AdGuard Home is installed and running, it’s time to make your network actually  use  it. Right now, your devices are probably still asking Google’s (8.8.8.8), Cloudflare’s (1.1.1.1), or your ISP’s DNS servers for website lookups — which means no ad-blocking, no caching, and no privacy benefits yet. Connecting your network to AdGuard Home means rerouting those DNS lookups through your own local resolver — one you control. This unlocks: Ad-blocking and tracking protection  for every device on your network. Faster lookups  thanks to local caching. Full visibility  into what domains your devices are contacting. And don’t worry — you can test all of this safely, one step at a time. Method 1: Set DNS via Your Router (Whole-Network Filtering) This is the recommended setup because it’s  set-and-forget . Every device that joins your ...

Part 2: Deploying AdGuard Home in Your Lab 1. Introduction — So You’re Ready to Deploy So you’ve learned what AdGuard Home does — how it blocks ads at the DNS level and speeds up your network with caching. Now comes the fun part:  putting it to work in your own home lab . Setting up AdGuard Home isn’t complicated, but there are a few choices to make depending on your environment. You might be running a  Raspberry Pi  that already handles network jobs, a  Docker host  where you prefer to containerise everything, or a  VM on Proxmox or VirtualBox  that you use for network services. The good news? AdGuard Home runs beautifully on all of them. When I first installed AdGuard Home, I started small — just to block ads on my smart TV. Within a week, it became the backbone of my whole network. My Pi turned into a mini DNS powerhouse, handling every request, caching responses, and silently keeping trackers out of my traffic. That’s the magic of this setup: once ...

💻 Ano Ba Talaga ang Server? (Taglish Edition) Maraming beses mo na siguro narinig yung salitang  “server”  — lalo na kapag may nagsasabing  “ay, down yung server!”  Pero ano ba talaga ’yon? Computer ba? Program? O pareho? 🤔 Para mas madali, isipin mo na parang  hospital  ang server. 🏗️ Hardware = Gusali at Kagamitan Ito yung  building, kama, at gamit ng ospital  — parang CPU, RAM, storage, at mga kable sa totoong server. Walang building = walang ospital. 👩‍⚕️ Software = Mga Doktor at Nurse Ito naman yung  tao sa loob  — sila ang gumagalaw, nag-aalaga, at nag-aayos ng pasyente. Sa tech world, sila yung  server software  tulad ng: Apache o Nginx (web server) MySQL o PostgreSQL (database server) File server (pang-share ng files) Walang staff = walang serbisyo. ⚡ Hardware + Software = Buong Ospital Kapag pinagsama mo ’yung gusali at mga tao, doon lang nagiging  tunay na ospital . Ganun din ang  server  — kailanga...

AdGuard Home DNS — Ad Blocking and Caching for Home Lab Enthusiasts (Part 1) Introduction You’ve probably already got a few things running in your home lab — maybe a NAS, a Docker stack, or a Pi-hole instance quietly managing DNS traffic. But there’s a point every home labber reaches: you start wondering if you can push your network just a little further. Fewer ads. Faster page loads. More control over what actually leaves your network. That’s usually when you stumble across  AdGuard Home . On the surface, AdGuard Home looks like another ad blocker. But it’s not your typical browser extension — it’s a  DNS-based network filter  that works at the root of your home network. Instead of blocking ads after they’ve already loaded in your browser, AdGuard Home stops those requests before they even reach your devices. The result? No ads on your smart TV, phone, tablet, or even your fridge that somehow talks to ad servers. But what really makes AdGuard Home interesting for home la...

Servers Explained Like a Hospital 🏥 (For Newbie Tech Readers) - Part 1 If you’re new to tech, you’ve probably heard the word  “server”  a lot. But what is a server really? Is it hardware? Is it software? Or both? 🤔 Don’t worry—let’s break it down in a way anyone can understand. Imagine a  hospital . 🏗️ Hardware = The Hospital Building Think of  hardware  as the actual  hospital building . It’s the walls, rooms, beds, equipment, and power supply. Without the building, doctors and nurses have nowhere to work. In the same way, a  physical server  is the computer hardware—CPU, RAM, hard drives, and network cards. 👩‍⚕️ Software = The Doctors and Nurses Now imagine the  hospital staff : doctors, nurses, and specialists. They don’t own the building, but they run it, organize patients, and deliver the services. This is what  server software  does. Examples: Web server software  (like Apache, Nginx) – serves websites. Database serve...

  Run Your Own Local AI with Ollama + Open WebUI on Proxmox Ever wanted to have your own local AI assistant running right from your homelab? Instead of relying on cloud services, you can set up a lightweight yet powerful AI environment inside Proxmox . In this guide, I’ll show you how I deployed Ollama (for models) and Open WebUI (for the interface) in separate LXC containers . This way, you get a clean modular setup that works even on modest hardware. My Setup Hypervisor: Proxmox VE Container 1 (Ollama): Debian 13, 2 cores, 4GB RAM, 8GB swap Container 2 (Open WebUI): Debian 11, 1 core, 1GB RAM, 2GB swap (optional) Step 1: Deploy Ollama Inside the first LXC container (Debian 13, 4GB RAM, 2 cores, 8GB swap): curl -fsSL https://ollama.com/install.sh | sh Pull some lightweight models to test: ollama pull phi3 ollama pull llama3.2 ollama pull gemma3:270m ollama pull tinyllama Arena comes preinstalled by default in Ollama. Models I Installed Here’s what...