# netlab Graphs with Multi-Access Links

DevFeed: [netlab Graphs with Multi-Access Links](<https://devfeed.tech/articles/netlab-graphs-with-multi-access-links-11347.md>)

Original publisher: [Read original article](<https://blog.ipspace.net/2026/03/netlab-graphs-multiaccess/>)

Published: 2026-03-16T07:03:00Z

Content type: tutorial

Language: en

Sources: [ipSpace.net blog](<https://devfeed.tech/sources/ipspace-net-blog.md>)

Topics: [Graphs](<https://devfeed.tech/topics/graphs.md>)

Tags: [devices](<https://devfeed.tech/tags/devices.md>), [graph](<https://devfeed.tech/tags/graph.md>), [graphs](<https://devfeed.tech/tags/graphs.md>), [interfaces](<https://devfeed.tech/tags/interfaces.md>), [netlab](<https://devfeed.tech/tags/netlab.md>), [node](<https://devfeed.tech/tags/node.md>), [ordering](<https://devfeed.tech/tags/ordering.md>), [router](<https://devfeed.tech/tags/router.md>)

## AI overview

This tutorial explains how to improve GraphViz topology graphs generated from netlab descriptions of multi-access links. It covers graph.rank and graph.linkorder, including a current limitation that leaves setting graph.linkorder on host interfaces as the practical solution.

## Source excerpt

A netlab user wanted to create a nice-looking topology graph from a simple topology connecting a few devices to a broadcast (multi-access) link. I don't have his exact topology, so we'll use this one (skipping the details like setting device types) nodes: [ r1, r2, h1, h2 ] links: - r1-r2 - interfaces: [ r1, r2, h1, h2 ] This is what GraphViz generates based on netlab's description of the lab topology: Read more ...