Merge pull request #3259 from AkihiroSuda/docs

docs/config/network: follow-up

Author: jandubois

website/content/en/docs/config/network/_index.md

@@ -13,4 +13,4 @@ connect_to_vm_via{"Connect to the VM via"} -- "localhost" --> default["Default"]
   vm -- "qemu" --> shared["socket_vmnet (shared)"]
   connect_from -- "Other VMs" --> userV2["user-v2"]
   connect_from -- "Other hosts" --> bridged["socket_vmnet (bridged)"]
-```
+```

website/content/en/docs/config/network/user-v2.md

@@ -1,10 +1,8 @@
 ---
-title: Lima user-v2 network
+title: user-v2 network
 weight: 32
 ---
 
-## Lima user-v2 network
-
 | ⚡ Requirement | Lima >= 0.16.0 |
 |-------------------|----------------|
 
@@ -44,4 +42,4 @@ An instance's IP address is resolvable from another instance as `lima-<NAME>.int
 
 _Note_
 
-- Enabling this network will disable the [default user-mode network](#user-mode-network--1921685024-)
+- Enabling this network will disable the [default user-mode network]({{< ref "/docs/config/network/user" >}})

website/content/en/docs/config/network/user.md

@@ -4,23 +4,24 @@ weight: 30
 
 ---
 
-## Default user-mode network (192.168.5.0/24)
-
 By default Lima only enables the user-mode networking aka "slirp".
 
-### Guest IP (192.168.5.15)
+The subnet is hard-coded to `192.168.5.0/24`.
+Use [`user-v2`]]({{< ref "/docs/config/network/user-v2" >}}) network to customize the subnet.
+
+## Guest IP (192.168.5.15)
 
 The guest IP address is set to `192.168.5.15`.
 
 This IP address is not accessible from the host by design.
 
-Use VMNet (see below) to allow accessing the guest IP from the host and other guests.
+Use [VMNet]]({{< ref "/docs/config/network/vmnet" >}}) to allow accessing the guest IP from the host and other guests.
 
-### Host IP (192.168.5.2)
+## Host IP (192.168.5.2)
 
 The loopback addresses of the host is `192.168.5.2` and is accessible from the guest as `host.lima.internal`.
 
-### DNS (192.168.5.3)
+## DNS (192.168.5.3)
 
 If `hostResolver.enabled` in `lima.yaml` is true, then the hostagent is going to run a DNS server over tcp and udp - each on a separate randomly selected free port. This server does a local lookup using the native host resolver, so it will deal correctly with VPN configurations and split-DNS setups, as well as mDNS, local `/etc/hosts` etc. For this the hostagent has to be compiled with `CGO_ENABLED=1` as default Go resolver is [broken](https://github.com/golang/go/issues/12524).
 

website/content/en/docs/config/network/vmnet.md

@@ -4,20 +4,21 @@ weight: 33
 
 ---
 
-## VMNet networks
+| ⚡ Requirement    | macOS |
+|-------------------|-------|
 
 VMNet assigns a "real" IP address that is reachable from the host.
 
 The configuration steps are different for each network type:
 - [vzNAT](#vzNAT)
 - [socket_vmnet](#socket_vmnet)
 
-### vzNAT
+## vzNAT
 
 | ⚡ Requirement | Lima >= 0.14, macOS >= 13.0 |
 |-------------------|-----------------------------|
 
-For [VZ](../vmtype/#vz) instances, the "vzNAT" network can be configured as follows:
+For [VZ]({{< ref "/docs/config/vmtype#vz" >}}) instances, the "vzNAT" network can be configured as follows:
 {{< tabpane text=true >}}
 {{% tab header="CLI" %}}
 ```bash
@@ -36,8 +37,8 @@ The range of the IP address is not specifiable.
 
 The "vzNAT" network does not need the `socket_vmnet` binary and the `sudoers` file.
 
-### socket_vmnet
-#### Managed (192.168.105.0/24)
+## socket_vmnet
+### Managed (192.168.105.0/24)
 
 [`socket_vmnet`](https://github.com/lima-vm/socket_vmnet) can be used for adding another guest IP that is accessible from the host and other guests,
 without depending on vz.
@@ -168,7 +169,7 @@ sudo /usr/libexec/ApplicationFirewall/socketfilterfw --add /usr/libexec/bootpd
 sudo /usr/libexec/ApplicationFirewall/socketfilterfw --unblock /usr/libexec/bootpd
 ```
 
-#### Unmanaged
+### Unmanaged
 Lima can also connect to "unmanaged" networks addressed by "socket". This
 means that the daemons will not be controlled by Lima, but must be started
 before the instance.  The interface type (host, shared, or bridged) is
@@ -177,4 +178,4 @@ configured in `socket_vmnet` and not in lima.
 ```yaml
 networks:
   - socket: "/var/run/socket_vmnet"
-```
+```