Fix cross linking to Getting Started and GNS3 HowTo

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>

Author: troglobit

_posts/2024-01-30-ospf-unnumbered-infix.md

@@ -16,8 +16,8 @@ network setup and maintenance in [Infix][1].
 > The topology in this post was built and tested in [GNS3][3], using
 > the Infix appliance from the [GNS3 Marketplace][4].  If you want to
 > follow along without any physical hardware, that is the quickest way
-> to get started — see the [virtual environments][5] documentation for
-> more details.
+> to get started — see our [Infix in GNS3][5] post for a step-by-step
+> setup guide.
 {: .prompt-tip }
 
 ## Introduction
@@ -409,4 +409,4 @@ Done!
 [2]: https://github.com/kernelkit/infix/tree/main/doc/cli
 [3]: https://gns3.com/infix
 [4]: https://gns3.com/marketplace/appliances/infix
-[5]: https://www.kernelkit.org/infix/latest/virtual/
+[5]: /posts/infix-in-gns3/

_posts/2024-08-13-router-boards.md

@@ -281,7 +281,7 @@ run on any Linux PC with Qemu installed ([instructions][10]).
 [8]: https://doc-en.rvspace.org/VisionFive2/Landing_Page/VisionFive_2/introduction.html
 [9]: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R2S
 [0]: https://www.qemu.org/
-[10]: https://kernelkit.org/infix/latest/virtual/
+[10]: /posts/getting-started/
 [11]: https://www.friendlyelec.com/index.php?route=product/product&product_id=284
 [12]: https://www.friendlyelec.com/index.php?route=product/product&product_id=287&search=r5s&description=true&category_id=0&sub_category=true
 [13]: https://www.friendlyelec.com/index.php?route=product/product&product_id=289

_posts/2024-09-14-getting-started.md

@@ -15,8 +15,8 @@ recommend [Debian][] based systems, like [Ubuntu][] and [Linux Mint][].
 >
 > Infix is available in the [GNS3 Marketplace][GNS3] — install the
 > appliance and you can drag, drop, and cable up entire networks without
-> touching the command line.  See the [virtual environments][virt]
-> documentation to get started.
+> touching the command line.  See our [Infix in GNS3][gns3post] post to
+> get started.
 {: .prompt-tip }
 
 ### Installing Qemu
@@ -89,9 +89,14 @@ $ ./qemu/run.sh
 > stuck with that single interface from before.
 {: .prompt-info }
 
+For more advanced Qemu options — networking bridges, shared folders, and
+multi-node setups — see the [virtual environments][virt] section of the
+full documentation.
+
 [sudo]:       https://troglobit.com/2016/12/11/a-life-without-sudo/
 [Debian]:     https://www.debian.org/
 [Ubuntu]:     https://ubuntu.com/
 [Linux Mint]: https://linuxmint.com/
 [GNS3]:       https://gns3.com/marketplace/appliances/infix
+[gns3post]:   /posts/infix-in-gns3/
 [virt]:       https://www.kernelkit.org/infix/latest/virtual/

_posts/2024-10-15-basic-container.md

@@ -199,6 +199,6 @@ Take care! 🧡
 [3]: https://en.wikipedia.org/wiki/Network_address_translation
 [4]: https://kernelkit.org/infix/latest/cli/text-editor/
 [5]: https://wiki.nftables.org/wiki-nftables/index.php/Main_Page
-[6]: https://kernelkit.org/infix/latest/virtual/
+[6]: /posts/getting-started/
 [7]: https://github.com/kernelkit/infix/releases/tag/latest
 [8]: /posts/zone-based-firewall/

_posts/2026-03-11-inside-infix.md

@@ -44,7 +44,7 @@ boards and compact dual-port routers like the NanoPi R2S, through
 general-purpose ARM and RISC-V end devices such as the NXP i.MX8MP EVK
 and StarFive VisionFive2, all the way up to enterprise switch platforms
 like the Microchip SparX-5i.  It also runs on x86_64, making it easy to
-spin up instances in Qemu or GNS3 for development and testing without
+spin up instances in [Qemu][6] or [GNS3][5] for development and testing without
 any dedicated hardware.  The same OS, the same tooling, the same
 management interfaces throughout.
 
@@ -204,7 +204,7 @@ device under test (DUT), verify the resulting operational state via
 RESTCONF, and reset it to a known-good baseline — all without touching
 the filesystem directly and without any CLI scraping.
 
-The test suite, *Infamy*, runs against both virtual topologies in Qemu
+The test suite, *Infamy*, runs against both virtual topologies in [Qemu][6]
 and real physical hardware using identical test cases.  Virtual
 topologies make it cheap to catch regressions early in development;
 physical runs ensure that hardware-specific paths — DSA offloads, WiFi,
@@ -239,3 +239,5 @@ feature in detail.  Questions and feedback are always welcome in the
 [2]: https://discord.gg/6bHJWQNVxN
 [3]: /posts/router-boards/
 [4]: https://www.kernelkit.org/infix/
+[5]: /posts/infix-in-gns3/
+[6]: /posts/getting-started/

_tabs/platforms.md

@@ -50,12 +50,12 @@ boot sequence and testing:
 [^1]: The [Qemu][2] x86_64 support is primarily intended for development
     and testing, but can also be used for evaluation and demo purposes
     using the [Infix appliance][11] in [GNS3][3]. For more information,
-    see: [Infix in Virtual Environments][4].
+    see: [Infix in GNS3][4].
 
 [1]: https://github.com/kernelkit/infix/tree/main/board
 [2]: https://www.qemu.org/
 [3]: https://www.gns3.com/
-[4]: https://github.com/kernelkit/infix/blob/main/doc/virtual.md
+[4]: /posts/infix-in-gns3/
 [5]: https://www.marvell.com/content/dam/marvell/en/public-collateral/embedded-processors/marvell-infrastructure-processors-octeon-tx2-cn913x-product-brief.pdf
 [6]: https://doc-en.rvspace.org/VisionFive2/Landing_Page/VisionFive_2/introduction.html
 [7]: https://wiki.friendlyelec.com/wiki/index.php/NanoPi_R2S