{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifitpwdjyuvuzniuvbpk37kka7hkcphmtaxpaesduoc6sxv26ajka",
    "uri": "at://did:plc:ax37ypwwfpozwkc552d7scv5/app.bsky.feed.post/3mj2abatztss2"
  },
  "path": "/threads/4%C3%972-5g-lan-4%C3%97nvme-mini-pc-setup-for-nas-router-%E2%80%93-anyone-running-similar.2634355/",
  "publishedAt": "2026-04-09T06:06:28.000Z",
  "site": "https://forums.anandtech.com",
  "tags": [
    "Networking"
  ],
  "textContent": "I’ve been testing a compact setup combining NAS + routing on a single system.\n\n\nMain idea was to simplify my setup and avoid running separate devices.\n\n\n\n\n* * *\n\n\nHardware layout:\n\n\n\n\n  * 4 × 2.5G LAN (Intel I226-V)\n  * 4 × M.2 NVMe\n  * low-power x86 CPU\n\n\n\n\n* * *\n\n\nNetwork setup:\n\n\n\n\n  * WAN → internet\n  * LAN → client devices\n  * dedicated interface for storage traffic\n\n\nSeparating NAS traffic from LAN actually made a noticeable difference during large transfers.\n\n\n\n\n* * *\n\n\nStorage layout:\n\n\n\n\n  * 1 NVMe for OS\n  * 2 NVMe for data\n  * 1 NVMe as cache\n\n\nThis reduced I/O contention compared to a single pool setup.\n\n\n\n\n* * *\n\n\nRunning:\n\n\n\n\n  * pfSense (routing)\n  * NAS services\n  * Docker containers\n\n\non the same system.\nusing a Qotom Q31100G4-type system\n\n\n\n* * *\n\n\nCurious if anyone here is doing something similar:\n\n\n\n\n  * multi-LAN NAS setups\n  * NVMe-based storage instead of SATA\n\n\nHow are you handling network separation?",
  "title": "4×2.5G LAN + 4×NVMe mini PC setup for NAS + router – anyone running similar?"
}