server

subscribe via RSS

Some things I found interesting from 2025-11-23 to 2025-11-30

Internet Discoveries between 23 and 30 November

  • DNS LOC Record (2014)
  • The CRDT Dictionary: A Field Guide to Conflict-Free Replicated Data Types
  • Be Like Clippy
  • AI CEO – Replace your boss before they replace you
  • Voyager 1 is about to reach one light-day from Earth
  • The engineer–manager pendulum is breaking
  • Penpot: The Open-Source Figma
  • DIY NAS: 2026 Edition - briancmoses.com
  • www.abc.net.au
  • Gemini CLI Tips and Tricks for Agentic Coding
  • Announcing n8n version 2.0 - coming soon! - Announcements - n8n Community
  • Making Crash Bandicoot (2011)
  • Copyparty, the FOSS file server [video]
  • Space Truckin’ – The Nostromo (2012)
  • Stridspiloten förevisar JAS Gripen: "Här sitter atombomben" - YouTube
  • infisical.com
  • Mozilla SSL Configuration Generator
  • thenounproject.com
  • Claude Opus 4.5
  • Claude Advanced Tool Use
  • ericmigi.com
  • The Letter — Stop Hacklore!
  • Years-old bugs in open source took out major clouds at risk • The Register
  • Shai-Hulud Returns: Over 300 NPM Packages Infected
  • We stopped roadmap work for a week and fixed bugs
  • Disney Lost Roger Rabbit
  • The Cloudflare outage was a good thing
  • Native Secure Enclave backed SSH keys on macOS
  • One of the Best Mecha Anime of All Time Finally Gets New First-Look Reveal After 45 Years

Windows Server Virtual Interface with a configured VLAN with a custom MAC

I’m not a Windows server kinda guy, but do you think I could find a nice, easy to follow, walk-through on how to create a Windows Server Virtual Interface on a given VLAN and using a custom MAC?

No, no I couldn’t. Perhaps I wasn’t searching with the correct search terms. Perhaps this is assumed knowledged on a Windows Server. I don’t know.

Here is how I ended up solving my problem.


The problem

We have a Windows Server. It’s going to be our internal, non-production, database server. But, it’s going to host multiple databases for multiple environments (dev, sit, uat, etc, etc). We split and protect each of our environments using VLAN’s.

The requirements

  • The server needs to have multiple VLAN’s attached to it.
  • The server has 2x 10GB NIC’s.
  • These 2 NIC’s must be configured for automatic failover, to protect us in the event of failure of cable/switch/port/etc. We’ll be using “NIC Teaming” for this.
  • The VLAN Virtual Interfaces need to have their own, individual, MAC. NIC teaming still uses the base, physical/teamed, card’s MAC for the VLAN Virtual Interface(s).

The solution