adam/rc.router
SHA256
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix doc format.

Browse Source
This commit is contained in:
ADAM David Alan Martin
2026-05-09 17:22:21 -04:00
parent 936c153c0c
commit aefbf1c936
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/add_net.md
+4 -4
View File
@@ -12,11 +12,11 @@
## Description ## Description
Adds an internal network segment with the specified vlan on the specified Adds an internal network segment with the specified vlan on the specified
card. The created vlan-adaptor is put into the specified group. It is setup card. The created vlan-adaptor is put into the specified group. It is setup
for both IPv4 and (where the ISP provides for it) IPv6. for both IPv4 and (where the ISP provides for it) IPv6.
The IPv4 network will be a `/24` under `${v4_net_xy0}` if `${card}` is The IPv4 network will be a `/24` under `${v4_net_xy0}` if `${card}` is
`xy0`, for example. If `${v4_net_xy0}` is not set, then `${v4_net}` is `xy0`, for example. If `${v4_net_xy0}` is not set, then `${v4_net}` is
used by default. The 3rd octet will be `$(( ${vlan}/10 + ${vlan}%10 ))`. For used by default. The 3rd octet will be `$(( ${vlan}/10 + ${vlan}%10 ))`. For
example, if `${vlan}` is `102` and `${v4_net}` is `172.18`, then the configured example, if `${vlan}` is `102` and `${v4_net}` is `172.18`, then the configured
@@ -24,7 +24,7 @@ v4 network will be `172.18.12.0/24` and the router will hold address
`172.18.12.1`. By default, IPv4 network DHCP configuration is enabled and `172.18.12.1`. By default, IPv4 network DHCP configuration is enabled and
the range `.100` to `.200` will be used as a dynamic allocation pool. the range `.100` to `.200` will be used as a dynamic allocation pool.
The IPv6 network will make `$(( ${vlan}/10 + ${vlan}%10 ))` into hex digits The IPv6 network will make `$(( ${vlan}/10 + ${vlan}%10 ))` into hex digits
to be appended to the ISP's IPv6 prefix. This makes it compatible with the to be appended to the ISP's IPv6 prefix. This makes it compatible with the
most common case of `/56` for most ISPs. If `no_ula` is specified in the most common case of `/56` for most ISPs. If `no_ula` is specified in the
optional arguments, then a ULA for this network segment will not be created. optional arguments, then a ULA for this network segment will not be created.
@@ -34,6 +34,6 @@ network will be appended. The `${rc_router_ula_prefix_size}` can be set to
`/56` to specify a ULA prefix length of 56. (No other lengths are supported `/56` to specify a ULA prefix length of 56. (No other lengths are supported
at this time.) at this time.)
The `isp=...` flag can be used to assign the specified subnet to be part The `isp=...` flag can be used to assign the specified subnet to be part
of the `IA_PD` list for the specified ISP. The `no_isp` flag can be used to of the `IA_PD` list for the specified ISP. The `no_isp` flag can be used to
skip provisioning the specified network with any ISP's DHCPv6 `IA_PD` request. skip provisioning the specified network with any ISP's DHCPv6 `IA_PD` request.