--- title: netlab: Multi-Site VLANs « ipSpace.net blog | daily.dev description: A walkthrough of modeling multi-site VLANs in netlab, a network lab automation tool. The post demonstrates three approaches: using a single shared VLAN (which... canonical: https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: netlab: Multi-Site VLANs « ipSpace.net blog | daily.dev og:description: A walkthrough of modeling multi-site VLANs in netlab, a network lab automation tool. The post demonstrates three approaches: using a single shared VLAN (which... og:url: https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076 og:image: https://api.daily.dev/og/posts/7me1cC076.png og:image:alt: netlab: Multi-Site VLANs « ipSpace.net blog og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # netlab: Multi-Site VLANs « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary A walkthrough of modeling multi-site VLANs in netlab, a network lab automation tool. The post demonstrates three approaches: using a single shared VLAN (which incorrectly assigns the same IP prefix to both sites), defining separate per-site VLANs with auto-assigned IDs (which gives correct addressing but different VLAN IDs), and finally using static VLAN IDs to achieve both independent IP prefixes and the same VLAN ID (100) on each site. Addressing reports are shown for each approach to illustrate the differences. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I assign the same VLAN ID to different sites with separate IP prefixes in netlab? Define two separate VLANs (one per site) and set the same static `id` value on both using the `vlan.id` field. Netlab does not check for overlapping VLAN IDs when they are statically assigned, so both VLANs can share VLAN ID 100 while receiving independent IP prefixes — for example, 172.16.0.0/24 and 172.16.1.0/24 — and independent access links per site. _Network engineers building multi-site lab topologies find the edge cases around VLAN ID assignment on daily.dev._ ### What happens if I define a single VLAN used across multiple sites in netlab? Netlab assigns a single IP prefix to the entire VLAN, meaning all hosts across all sites share the same subnet. For example, hosts on both site A and site B would receive addresses from 172.16.0.0/24, making proper layer-3 site separation impossible without defining separate per-site VLANs. _Teams designing isolated multi-site lab networks track netlab behavior like this on daily.dev._ ## Similar posts on daily.dev - [5 rules I use for sane VLAN design at home \(without overcomplicating it\)](https://daily.dev/posts/5-rules-i-use-for-sane-vlan-design-at-home-without-overcomplicating-it--3wvgbumjq) · XDA Developers · 0 upvotes · 1 comments - [Configuring Management IP Addresses to Virtual Network Devices « ipSpace.net blog](https://daily.dev/posts/configuring-management-ip-addresses-to-virtual-network-devices-ipspace-net-blog-ffffzfuyz) · ipSpace.net Blog · 0 upvotes · 0 comments --- [View this post on daily.dev](https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"netlab: Multi-Site VLANs « ipSpace.net blog","url":"https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076"},"datePublished":"2026-08-11T08:52:17.387Z","dateModified":"2026-08-11T08:54:27.955Z","description":"A walkthrough of modeling multi-site VLANs in netlab, a network lab automation tool. The post demonstrates three approaches: using a single shared VLAN (which...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ee759d9fe48d714f7d70eb17a3b3563b?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/ee759d9fe48d714f7d70eb17a3b3563b?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"ipSpace.net Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"ipSpace.net Blog","logo":"https://media.daily.dev/image/upload/s--xS7E82MT--/f_auto,q_auto/v1786438303/logos/ipspace?_a=BAMAMicg0","url":"https://daily.dev/sources/ipspace"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"","timeRequired":"PT4M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"ipSpace.net Blog","item":"https://daily.dev/sources/ipspace"},{"@type":"ListItem","position":3,"name":"netlab: Multi-Site VLANs « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/netlab-multi-site-vlans-ipspace-net-blog-7me1cc076#faq","mainEntity":[{"@type":"Question","name":"How do I assign the same VLAN ID to different sites with separate IP prefixes in netlab?","acceptedAnswer":{"@type":"Answer","text":"Define two separate VLANs (one per site) and set the same static `id` value on both using the `vlan.id` field. Netlab does not check for overlapping VLAN IDs when they are statically assigned, so both VLANs can share VLAN ID 100 while receiving independent IP prefixes — for example, 172.16.0.0/24 and 172.16.1.0/24 — and independent access links per site. Network engineers building multi-site lab topologies find the edge cases around VLAN ID assignment on daily.dev."}},{"@type":"Question","name":"What happens if I define a single VLAN used across multiple sites in netlab?","acceptedAnswer":{"@type":"Answer","text":"Netlab assigns a single IP prefix to the entire VLAN, meaning all hosts across all sites share the same subnet. For example, hosts on both site A and site B would receive addresses from 172.16.0.0/24, making proper layer-3 site separation impossible without defining separate per-site VLANs. Teams designing isolated multi-site lab networks track netlab behavior like this on daily.dev."}}]} ```