doc fixes

This commit is contained in:
tschettervictor
2025-06-16 07:49:50 -06:00
committed by GitHub
parent 1aa056d211
commit f90484043f

View File

@@ -81,9 +81,9 @@ Note that jails support specifying an IP without the subnet (/24 or whatever
yours is) but we highly recommend setting it, especially on VNET jails. Not
doing so can cause issues in some rare cases.
Bastille also supports IPv6. Instead of an IPv4 address, you can specify and
Bastille also supports IPv6. Instead of an IPv4 address, you can specify an
IPv6 address when creating a jail to use IPv6. It is also possible to use both
by quoting and IPv4 and IPv6 address together as seen in the following example.
by quoting an IPv4 and IPv6 address together as seen in the following example.
.. code-block:: shell
@@ -311,8 +311,8 @@ VLAN Configuration
Bastille supports VLANs to some extent when creating jails. When creating a jail, use
the ``--vlan ID`` options to specify a VLAN ID for your jail. This will set the proper
variables inside the jails `rc.conf` to add the jail to the specified VLAN. Using this method
the bridge for the jail must carry tagged VLAN packets, e.g. you can bridge a VLAN trunk to
variables inside the jails `rc.conf` to add the jail to the specified VLAN. When using this method,
the interface being assigned must carry tagged VLAN packets, e.g. you can bridge a VLAN trunk to
the jail and in the jail you then can access all VLANs. But be careful: This may have
security implications.
@@ -321,8 +321,8 @@ standard way of naming a VLAN interface. This is due to the limitations
of the JIB script that Bastille uses to manage VNET jails.
You can however use ``-B|--bridge`` with VLAN interfaces (even with dots in the name).
Using this method you create bridge interfaces in ``rc.conf`` and only add VLANs, that are needed
for the jail. The jail only has access to this VLAN then and not to the whole trunk.
Using this method you create bridge interfaces in ``rc.conf`` and only add VLANs that are needed
for the jail. The jail only has access to these VLANs and not to the whole trunk.
Below is an ``rc.conf`` snippet that was provided by a user who has such a configuration.
.. code-block:: shell