--- title: netlab 2.0: Use Custom Bridges on Multi-Access Links «... description: netlab 2.0 introduces a 'bridge node' role that simplifies using custom network devices (like Arista EOS) as bridges on multi-access links. Previously,... canonical: https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: netlab 2.0: Use Custom Bridges on Multi-Access Links « ipSpace.net blog | daily.dev og:description: netlab 2.0 introduces a 'bridge node' role that simplifies using custom network devices (like Arista EOS) as bridges on multi-access links. Previously,... og:url: https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8 og:image: https://api.daily.dev/og/posts/1cH4ZBFY8.png og:image:alt: netlab 2.0: Use Custom Bridges on Multi-Access Links « 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 2.0: Use Custom Bridges on Multi-Access Links « ipSpace.net blog **[ipSpace.net Blog](https://daily.dev/sources/ipspace)** · 3 min read · 0 upvotes · 0 comments ## Summary netlab 2.0 introduces a 'bridge node' role that simplifies using custom network devices (like Arista EOS) as bridges on multi-access links. Previously, implementing a custom bridge required manually defining VLANs, bridge modes, and multiple access links. With the new bridge node feature, you simply set a node's role to 'bridge' and reference it in the link's bridge attribute. netlab automatically creates isolated VLANs per link, configures VLAN access ports, and ensures the bridge node has no IP address or loopback — functioning as a transparent Layer 2 bridge. The post includes a before/after topology comparison and the generated Arista EOS configuration. ## 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 use a custom device as a bridge on a multi-access link in netlab 2.0? In netlab 2.0, set the node's role to 'bridge' and reference it in the link's bridge attribute. You don't need to manually define VLANs or the vlan module — netlab automatically creates an isolated VLAN per link, configures VLAN access ports on the bridge device, and ensures no IP address is assigned to the VLAN interface, making it a transparent Layer 2 bridge. _Network engineers building virtual labs with netlab track feature releases like this on daily.dev._ ### What Arista EOS configuration does netlab 2.0 generate for a bridge node? netlab generates MSTP spanning-tree mode, a dedicated VLAN per multi-access link (e.g. VLAN 100), switchport access VLAN assignments on each Ethernet interface connecting to edge nodes, a stub VLAN interface with no IP address, and 'no ip routing' — ensuring the EOS node acts as a pure transparent bridge with no Layer 3 forwarding. _Engineers validating netlab-generated configs for EOS bridge nodes find related discussions on daily.dev._ ## Similar posts on daily.dev - [EVPN with SR-MPLS Core « ipSpace.net blog](https://daily.dev/posts/evpn-with-sr-mpls-core-ipspace-net-blog-taobtibzc) · ipSpace.net Blog · 0 upvotes · 0 comments --- Tags: [#networking](https://daily.dev/tags/networking) [View this post on daily.dev](https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8) ```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 2.0: Use Custom Bridges on Multi-Access Links « ipSpace.net blog","url":"https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8"},"datePublished":"2026-08-11T08:52:19.176Z","dateModified":"2026-08-24T07:02:17.399Z","description":"netlab 2.0 introduces a 'bridge node' role that simplifies using custom network devices (like Arista EOS) as bridges on multi-access links. Previously,...","image":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","thumbnailUrl":"https://media.daily.dev/image/upload/s--0_ODbtD2--/f_auto/v1722860399/public/Placeholder%2008","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-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8","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":"netlab 2.0: Use Custom Bridges on Multi-Access Links « ipSpace.net blog"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/netlab-2-0-use-custom-bridges-on-multi-access-links-ipspace-net-blog-1ch4zbfy8#faq","mainEntity":[{"@type":"Question","name":"How do I use a custom device as a bridge on a multi-access link in netlab 2.0?","acceptedAnswer":{"@type":"Answer","text":"In netlab 2.0, set the node's role to 'bridge' and reference it in the link's bridge attribute. You don't need to manually define VLANs or the vlan module — netlab automatically creates an isolated VLAN per link, configures VLAN access ports on the bridge device, and ensures no IP address is assigned to the VLAN interface, making it a transparent Layer 2 bridge. Network engineers building virtual labs with netlab track feature releases like this on daily.dev."}},{"@type":"Question","name":"What Arista EOS configuration does netlab 2.0 generate for a bridge node?","acceptedAnswer":{"@type":"Answer","text":"netlab generates MSTP spanning-tree mode, a dedicated VLAN per multi-access link (e.g. VLAN 100), switchport access VLAN assignments on each Ethernet interface connecting to edge nodes, a stub VLAN interface with no IP address, and 'no ip routing' — ensuring the EOS node acts as a pure transparent bridge with no Layer 3 forwarding. Engineers validating netlab-generated configs for EOS bridge nodes find related discussions on daily.dev."}}]} ```