--- title: Concise Link Descriptions in netlab Topologies «... description: netlab supports multiple concise formats for defining links between lab devices in topology files. The simplest is a hyphen-separated string of node names... canonical: https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Concise Link Descriptions in netlab Topologies « ipSpace.net blog | daily.dev og:description: netlab supports multiple concise formats for defining links between lab devices in topology files. The simplest is a hyphen-separated string of node names... og:url: https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz og:image: https://api.daily.dev/og/posts/8EX3YppXz.png og:image:alt: Concise Link Descriptions in netlab Topologies « 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. # Concise Link Descriptions in netlab Topologies « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary netlab supports multiple concise formats for defining links between lab devices in topology files. The simplest is a hyphen-separated string of node names (e.g., r1-r2), or a YAML inline list for nodes with hyphens in their names. When link attributes are needed, you can use dictionary keys with node names or an explicit interfaces list. Interface-level parameters like OSPF DR priority can be set under node keys in the dictionary format. Regardless of input format, netlab normalizes everything into a canonical interfaces-list data model internally. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What are the different ways to define links between nodes in a netlab topology file? netlab supports four link definition formats. The simplest is a hyphen-separated string like r1-r2 or r1-r2-r3. For node names containing hyphens, use a YAML list such as [r-1, r-2]. When link attributes are needed, use a dictionary with node names as keys alongside attribute keys like ospf.area. Alternatively, use an explicit interfaces list. All formats normalize internally to the interfaces-list data model. _Network engineers building netlab labs track topology syntax patterns like these on daily.dev._ ### How do I set OSPF interface parameters like DR priority per link in a netlab topology? Use the dictionary-based link format and nest interface parameters under the node key. For example, set ospf.priority: 1 under r-1 within a link dictionary, while ospf.area is set at the link level. This lets you mix link-level and interface-level OSPF attributes in the same link definition without switching to the verbose interfaces list format. _Engineers tuning OSPF lab scenarios in netlab find configuration patterns like this on daily.dev._ ## Similar posts on daily.dev - [Compress netlab Lab Topologies with Dot Notation « ipSpace.net blog](https://daily.dev/posts/compress-netlab-lab-topologies-with-dot-notation-ipspace-net-blog-johomwxka) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#networking](https://daily.dev/tags/networking) [View this post on daily.dev](https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz) ```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":"Concise Link Descriptions in netlab Topologies « ipSpace.net blog","url":"https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz"},"datePublished":"2026-08-11T08:51:54.933Z","dateModified":"2026-08-11T08:57:42.892Z","description":"netlab supports multiple concise formats for defining links between lab devices in topology files. The simplest is a hyphen-separated string of node names...","image":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","thumbnailUrl":"https://media.daily.dev/image/upload/s--1KxV4ohY--/f_auto/v1722860400/public/Placeholder%2007","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/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"networking","timeRequired":"PT3M"} {"@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":"Concise Link Descriptions in netlab Topologies « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/concise-link-descriptions-in-netlab-topologies-ipspace-net-blog-8ex3yppxz#faq","mainEntity":[{"@type":"Question","name":"What are the different ways to define links between nodes in a netlab topology file?","acceptedAnswer":{"@type":"Answer","text":"netlab supports four link definition formats. The simplest is a hyphen-separated string like r1-r2 or r1-r2-r3. For node names containing hyphens, use a YAML list such as [r-1, r-2]. When link attributes are needed, use a dictionary with node names as keys alongside attribute keys like ospf.area. Alternatively, use an explicit interfaces list. All formats normalize internally to the interfaces-list data model. Network engineers building netlab labs track topology syntax patterns like these on daily.dev."}},{"@type":"Question","name":"How do I set OSPF interface parameters like DR priority per link in a netlab topology?","acceptedAnswer":{"@type":"Answer","text":"Use the dictionary-based link format and nest interface parameters under the node key. For example, set ospf.priority: 1 under r-1 within a link dictionary, while ospf.area is set at the link level. This lets you mix link-level and interface-level OSPF attributes in the same link definition without switching to the verbose interfaces list format. Engineers tuning OSPF lab scenarios in netlab find configuration patterns like this on daily.dev."}}]} ```