--- title: Start Multiple netlab Labs on the Same Server «... description: netlab release 1.5 introduces a multilab plugin that solves resource conflicts when running multiple network labs in parallel on the same server. The plugin... canonical: https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Start Multiple netlab Labs on the Same Server « ipSpace.net blog | daily.dev og:description: netlab release 1.5 introduces a multilab plugin that solves resource conflicts when running multiple network labs in parallel on the same server. The plugin... og:url: https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g og:image: https://api.daily.dev/og/posts/t215YH85G.png og:image:alt: Start Multiple netlab Labs on the Same Server « 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. # Start Multiple netlab Labs on the Same Server « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 4 min read · 0 upvotes · 0 comments ## Summary netlab release 1.5 introduces a multilab plugin that solves resource conflicts when running multiple network labs in parallel on the same server. The plugin assigns a unique lab ID to each instance, which is used to differentiate management subnets, network names, VM/container prefixes, VIF interface names, and libvirt tunnel endpoints. Three use cases are supported: multiple labs per single user (set defaults.multilab.id in topology or CLI), multiple users each with one lab (set multilab.id in ~/.netlab.yml), and flexible on-demand allocation via an external wrapper. The plugin is optional and can be made default by adding 'plugin: [ multilab ]' to ~/.netlab.yml. Upgrade via pip3 install --upgrade networklab. ## 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 run multiple netlab labs on the same server without IP address conflicts? Use the multilab plugin introduced in netlab release 1.5. Each lab instance must be assigned a unique lab ID via the defaults.multilab.id parameter (in the topology file, as a CLI argument, or in ~/.netlab.yml). The plugin uses this ID to make management subnets, network names, VM/container prefixes, VIF interface names, and libvirt tunnel endpoints unique across all running instances. _Network engineers managing shared lab servers track tools like netlab on daily.dev._ ### How do I set a default plugin for all netlab lab topologies without specifying it in every topology file? Add a plugin entry to the ~/.netlab.yml defaults file. For example, adding 'plugin: [ multilab ]' to that file causes the multilab plugin to be applied automatically to every lab topology without requiring per-topology configuration. This was introduced alongside the multilab plugin in netlab release 1.5. _Keeping up with netlab configuration patterns is easier when relevant posts surface where you already read about networking tools._ --- Tags: [#networking](https://daily.dev/tags/networking) [View this post on daily.dev](https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g) ```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":"Start Multiple netlab Labs on the Same Server « ipSpace.net blog","url":"https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g"},"datePublished":"2026-08-11T08:53:10.866Z","dateModified":"2026-08-11T09:10:23.952Z","description":"netlab release 1.5 introduces a multilab plugin that solves resource conflicts when running multiple network labs in parallel on the same server. The plugin...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","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/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking","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":"Start Multiple netlab Labs on the Same Server « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/start-multiple-netlab-labs-on-the-same-server-ipspace-net-blog-t215yh85g#faq","mainEntity":[{"@type":"Question","name":"How do I run multiple netlab labs on the same server without IP address conflicts?","acceptedAnswer":{"@type":"Answer","text":"Use the multilab plugin introduced in netlab release 1.5. Each lab instance must be assigned a unique lab ID via the defaults.multilab.id parameter (in the topology file, as a CLI argument, or in ~/.netlab.yml). The plugin uses this ID to make management subnets, network names, VM/container prefixes, VIF interface names, and libvirt tunnel endpoints unique across all running instances. Network engineers managing shared lab servers track tools like netlab on daily.dev."}},{"@type":"Question","name":"How do I set a default plugin for all netlab lab topologies without specifying it in every topology file?","acceptedAnswer":{"@type":"Answer","text":"Add a plugin entry to the ~/.netlab.yml defaults file. For example, adding 'plugin: [ multilab ]' to that file causes the multilab plugin to be applied automatically to every lab topology without requiring per-topology configuration. This was introduced alongside the multilab plugin in netlab release 1.5. Keeping up with netlab configuration patterns is easier when relevant posts surface where you already read about networking tools."}}]} ```