Fix Routing Traffic to Multiple IP Resources

src/pages/how-to/routing-multiple-ip-resources.mdx

@@ -192,4 +192,64 @@ Your `Remote Network` should now resemble this setup:
 
 ![Remote Network](/docs-static/img/how-to-guides/routing-multiple-ip-resources/21-multiple-networks.png)
 
-By completing these steps, you’ve created resources allowing varied access levels for different user groups within a hybrid organization network.
+Now, you can review, select, or deselect available networks using NetBird's CLI.
+
+Here's the output of the `netbird networks list` command from a DevOps team client:
+
+```bash
+$ netbird networks list
+Available Networks:
+
+  - ID: Berlin LAN
+    Network: 172.16.0.0/15
+    Status: Selected
+
+  - ID: Production environment
+    Network: 10.108.0.0/16
+    Status: Selected
+
+  - ID: DNS-1
+    Network: 172.17.100.2/32
+    Status: Selected
+
+  - ID: DNS-2
+    Network: 172.17.100.3/32
+    Status: Selected
+```
+
+Here's the output of the same command from a developer machine:
+
+
+```bash
+$ netbird networks list
+Available Networks:
+
+  - ID: Development Environment
+    Network: 172.16.50.1/32
+    Status: Selected
+
+  - ID: DNS-1
+    Network: 172.17.100.2/32
+    Status: Selected
+
+  - ID: DNS-2
+    Network: 172.17.100.3/32
+    Status: Selected
+```
+
+And here's the output from a regular user workstation:
+
+```bash
+$ netbird networks list
+Available Networks:
+
+  - ID: DNS-1
+    Network: 172.17.100.2/32
+    Status: Selected
+
+  - ID: DNS-2
+    Network: 172.17.100.3/32
+    Status: Selected
+```
+
+By completing these steps, you’ve created resources allowing varied access levels for different user groups within a hybrid organization network.