Fix table column widths, some markup fixes

Signed-off-by: Jo-Philipp Wich <jo@mein.io>

diff --git a/docs/uci_dnsmasq.txt b/docs/uci_dnsmasq.txt
index b2d3f444bd125c552c5e0867b0f7032d317f1798..2c3ec00323e4a13cc68860a6009795785765affd 100644 (file)
--- a/docs/uci_dnsmasq.txt
+++ b/docs/uci_dnsmasq.txt
@@ -41,7 +41,7 @@ config 'dnsmasq'
 * Options "enable_tftp" and "tftp_root" turn on the TFTP server and serve files from tftp_root.  You may need to set the server's IP on the client.  On the client,  change it by setting "serverip" (e.g. "setenv serverip 192.168.1.10").
 
 === All Options
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Default | Option | Description 
 | 'add_local_domain' | boolean | '1' | | Add the local domain as search directive in resolv.conf. 
@@ -117,7 +117,7 @@ config 'dhcp' 'lan'
 
 Below is a listing of legal options for 'dhcp' sections.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'dhcp_option' | list of strings | no | _(none)_ | The ID dhcp_option here must be with written with an underscore. OpenWrt will translate this to --dhcp-option, with a hyphen, as ultimately used by dnsmasq. Multiple option values can be given for this _network-id_, with a a space between them and the total string between "". E.g. '26,1470' or 'option:mtu, 1470' that can assign an MTU per DHCP. Your client must accept MTU by DHCP for this to work. Or "3,192.168.1.1 6,192.168.1.1" to give out gateway and dns server addresses. 
@@ -163,7 +163,7 @@ config host
 ----
 This adds the fixed IP address 192.168.1.3 and the name "mylaptop" for a machine with the (Ethernet) hardware address 11:22:33:44:55:66 or aa:bb:cc:dd:ee:ff. Note that this is **unreliable** if more than one of the listed mac addresses is on the network simultaneously. It's useful for cases such as a laptop with both wireless and wired interfaces, provided that only one will be active at a given time.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ip' | string | yes | _(none)_ | 'ignore' or the IP address to be used for this host. 
@@ -212,7 +212,7 @@ config boot linux
        list   dhcp_option      'option:root-path,192.168.1.2:/data/netboot/root'
 ----
 This tells the client to load pxelinux.0 from the server at 192.168.1.2, and mount root from /data/netboot/root on the same server.
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'dhcp_option' | list of strings | no | _(none)_ | Additional options to be added for this network-id. CAUTION: If you specify this, you also need to specify the network-id. 
@@ -239,7 +239,7 @@ config _classifier_
 ----
 
 The placeholder '_classifier_' can be one of these values:
-[options="header"]
+[cols="1,4",options="header"]
 |====
 | Classifier | Description 
 | 'mac'  | Hardware address of the client 

diff --git a/docs/uci_dropbear.txt b/docs/uci_dropbear.txt
index 532828f54214c2cd3d5bb41ecc8ebb279b77bcab..fb6f8441f981930e1bd83a65fa3092d1d35e105e 100644 (file)
--- a/docs/uci_dropbear.txt
+++ b/docs/uci_dropbear.txt
@@ -11,7 +11,7 @@ The 'dropbear' configuration contains settings for the dropbear SSH server in a
 
 The 'dropbear' section contains these settings:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'enable' | boolean | no | 1 | Set to '0' to disable starting dropbear at system boot. 

diff --git a/docs/uci_firewall.txt b/docs/uci_firewall.txt
index 47d7738a845e30dff6355ee98eac18c07f818d1b..30c355ca7dc5a5618a1c134b954c3a00cbf66d9e 100644 (file)
--- a/docs/uci_firewall.txt
+++ b/docs/uci_firewall.txt
@@ -27,7 +27,7 @@ A minimal firewall configuration for a router usually consists of one _defaults_
 The 'defaults' section declares global firewall settings which do not belong to specific zones.
 The following options are defined within this section:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'input' | string | no | 'REJECT' | Set policy for the 'INPUT' chain of the 'filter' table. 
@@ -58,7 +58,7 @@ A 'zone' section groups one or more _interfaces_ and serves as a _source_ or _de
 
 The options below are defined within 'zone' sections:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'name' | zone name | yes | _(none)_ | Unique zone name. 11 characters is the maximum working firewall zone name length. 
@@ -87,7 +87,7 @@ The 'forwarding' sections control the traffic flow between _zones_ and may enabl
 
 Below is a listing of allowed option within _forwardings_:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'src' | zone name | yes | _(none)_ | Specifies the traffic _source zone_. Must refer to one of the defined _zone names_ 
@@ -109,7 +109,7 @@ Port ranges are specified as 'start:stop', for instance '6666:6670'.  This is si
 
 The options below are valid for _redirects_:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'src' | zone name | yes for 'DNAT' target | _(none)_ | Specifies the traffic _source zone_. Must refer to one of the defined _zone names_. For typical port forwards this usually is 'wan' 
@@ -159,7 +159,7 @@ Port ranges are specified as 'start:stop', for instance '6666:6670'. This is sim
 
 Valid options for this section are:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'src' | zone name | yes (CAUTION: optional since Firewall v2, version 58 and above) | _(none)_ | Specifies the traffic _source zone_. Must refer to one of the defined _zone names_. 
@@ -212,7 +212,7 @@ It is possible to include custom firewall scripts by specifying one or more 'inc
 
 There is only one possible parameter for _includes_:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'enabled' | boolean | no | '1' | Allows to disable the corresponding include without having to delete the section 
@@ -234,7 +234,7 @@ huge address or port lists without the need for creating one rule per item to ma
 
 The following options are defined for _ipsets_:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'enabled' | boolean | no | '1' | Allows to disable the declaration fo the ipset without the need to delete the section. 

diff --git a/docs/uci_net.txt b/docs/uci_net.txt
index 11afb4ba8b1153a48f159defc1738bacb9c64a3d..4fc42285f19cd040a38aea875f8ddc61b5c566d8 100644 (file)
--- a/docs/uci_net.txt
+++ b/docs/uci_net.txt
@@ -1,12 +1,12 @@
 Network configuration
 =====================
 
-The central network configuration is located in the file '/etc/config/network'. This configuration file is responsible for defining _switch VLANs_, _interface configurations_ and _network routes_. After editing and saving '/etc/config/network' you need to execute ----
-/etc/init.d/network reload
----- to stop and restart the network before any changes take effect. Rebooting the router is not necessary.
+The central network configuration is located in the file '/etc/config/network'. This configuration file is responsible for defining _switch VLANs_, _interface configurations_ and _network routes_.
 
-* https:_dev.openwrt.org/browser/branches/attitude_adjustment/package/base-files/files/etc/config/network
-* https:_dev.openwrt.org/browser/trunk/package/base-files/files/etc/config/network
+After editing and saving '/etc/config/network' you need to execute '/etc/init.d/network reload' to stop and restart the network before any changes take effect. Rebooting the router is not necessary.
+
+ * https://dev.openwrt.org/browser/branches/attitude_adjustment/package/base-files/files/etc/config/network
+ * https://dev.openwrt.org/browser/trunk/package/base-files/files/etc/config/network
 
 Feel free to inform yourself about [[doc/techref/netifd|netifd]] (Network Interface Daemon).
 
@@ -20,7 +20,7 @@ CAUTION: The globals section is available in Barrier Breaker and later releases.
 
 The 'globals' section contains interface-independent options affecting the network configuration in general.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ula_prefix' | IPv6-prefix | no | _(none)_ | IPv6 [[wp>Unique local address|ULA]]-Prefix for this device 
@@ -95,7 +95,7 @@ CAUTION: The system limits the interface name length to 15 characters including
 
 The _interface protocol_ may be one of the following:
 
-[options="header"]
+[cols="1,4,2",options="header"]
 |====
 | Protocol | Description | Program 
 | 'static' | Static configuration with fixed address and netmask |  'ip'/'ifconfig'  
@@ -131,7 +131,7 @@ CAUTION: In openwrt 12.09, if an interface section has no protocol defined (not
 
 === Options valid for all protocol types ===
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ifname' | interface name(s) | yes(*) | _(none)_ | Physical interface name to assign to this section, list of interfaces if type bridge is set. _(*) This option may be empty or missing if only a wireless interface references this network or if the protocol type is 'pptp', 'pppoa' or '6in4'_ 
@@ -153,7 +153,7 @@ CAUTION: In openwrt 12.09, if an interface section has no protocol defined (not
 
 === Protocol "static" ===
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | ip address | yes, if no 'ip6addr' is set. | _(none)_ | IP address. [openwrt 12.09] It could be a list of ipaddr , that is: several ipaddresses will be assigned to the interface. If, instead of a list, several ipaddr are specified as options, only the last is applied. 
@@ -174,7 +174,7 @@ CAUTION: In openwrt 12.09, if an interface section has no protocol defined (not
 
 === Protocol "dhcp" ===
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | '[line-through]*gateway*' | [line-through]*string* | [line-through]*no* | [line-through]*_(none)_* | [line-through]*Suppresses DHCP-assigned default gateway if set to 0.0.0.0* 
@@ -237,7 +237,7 @@ Both default routes set up by wan and wan2 will appear in the routing table.
 
 CAUTION: The package 'odhcp6c' must be installed to use dhcpv6.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'reqaddress' | [try,force,none] | no | try | Behaviour for requesting addresses 
@@ -260,7 +260,7 @@ CAUTION: The package 'odhcp6c' must be installed to use dhcpv6.
 
 CAUTION: The package 'ppp' must be installed to use PPP.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'device' | file path | yes | _(none)_ | Modem device node 
@@ -286,7 +286,7 @@ opkg update
 opkg install ppp kmod-pppoe ppp-mod-pppoe
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'username' | string | no(?) | _(none)_ | Username for PAP/CHAP authentication 
@@ -308,7 +308,7 @@ opkg install ppp kmod-pppoe ppp-mod-pppoe
 
 CAUTION: The package 'ppp-mod-pppoa' must be installed to use PPPoA.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'vci' | number | no | '35' | PPPoA VCI 
@@ -334,7 +334,7 @@ CAUTION: The package 'ppp-mod-pppoa' must be installed to use PPPoA.
 CAUTION: The package 'comgt' must be installed to use 3G. Check [[doc:recipes:3gdongle]] for further help with that.
 
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'device' | file path | yes | _(none)_ | Modem device node 
@@ -358,7 +358,7 @@ CAUTION: The package 'comgt' must be installed to use 3G. Check [[doc:recipes:3g
 
 CAUTION: The package 'uqmi' must be installed to use QMI.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'device' | file path | yes | _(none)_ | QMI device node, typically /dev/cdc-wdm0 
@@ -375,7 +375,7 @@ CAUTION: The package 'uqmi' must be installed to use QMI.
 
 CAUTION: The package 'comgt-ncm' + modem specific driver must be installed to use NCM.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'device' | file path | yes | _(none)_ | NCM device node, typically /dev/cdc-wdm0 or /dev/ttyUSB# 
@@ -393,7 +393,7 @@ CAUTION: The package 'comgt-ncm' + modem specific driver must be installed to us
 
 CAUTION: The package 'wwan' must be installed to use this feature. The "wwan" protocol detects the right protocol (3G/QMI/NCM/MBIM) for the USB Modem model and passes the configuration to the protocol.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'apn' | string | yes | _(none)_ | Used APN 
@@ -410,7 +410,7 @@ CAUTION: The package 'wwan' must be installed to use this feature. The "wwan" pr
 CAUTION: The package 'hnet-full' must be installed to use hnet.
 CAUTION: See http:_tools.ietf.org/html/draft-ietf-homenet-hncp for details.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'mode' | string | no | auto | Interface mode. One of external, guest, adhoc or hybrid. 
@@ -423,7 +423,7 @@ CAUTION: See http:_tools.ietf.org/html/draft-ietf-homenet-hncp for details.
 
 CAUTION: The package 'pptp' must be installed to use PPtP. There is a separate Howto for this: [[doc:howto:vpn.client.pptp]]. You need to have another section to configure the "parent" device, and you might need to add "<vpn>" to your "wan" zone in the firewall (<vpn> being the "logical interface name" of this section).
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'server' | ip address | yes | _(none)_ | Remote PPtP server 
@@ -441,7 +441,7 @@ CAUTION: The package 'pptp' must be installed to use PPtP. There is a separate H
 
 CAUTION: The package '6in4' must be installed to use this protocol.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | IPv4 address | no | Current WAN IPv4 address | Local IPv4 endpoint address 
@@ -474,7 +474,7 @@ CAUTION: The package 'aiccu' must be installed to use this protocol. This utilit
 
 CAUTION: This protocol is available for Barrier Breaker and newer versions only.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'username' | string | yes | _(none)_ | Server username 
@@ -500,7 +500,7 @@ CAUTION: This protocol is available for Barrier Breaker and newer versions only.
 
 CAUTION: The package '6to4' must be installed to use this protocol.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | IPv4 address | no | Current WAN IPv4 address | Local IPv4 endpoint address 
@@ -525,7 +525,7 @@ CAUTION: The package '6rd' must be installed to use this protocol.
 
 CAUTION: The needed tunnel values are usually obtained via the DHCPv4 request for the WAN interface. Try that [[doc/uci/network6#rd_tunnel_isp-provided_ipv6_transition|first]]. Below is only needed for hardcoding the tunnel.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'peeraddr' | IPv4 address | yes | no | 6rd - Gateway  
@@ -548,7 +548,7 @@ CAUTION: The needed tunnel values are usually obtained via the DHCPv4 request fo
 
 CAUTION: The package 'ds-lite' must be installed to use this protocol.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'peeraddr' | IPv6 address | yes | no | DS-Lite AFTR address  
@@ -570,7 +570,7 @@ CAUTION: The package 'xl2tpd' must be installed to use this protocol.
 
 Most options are similar to protocol "ppp".
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'server' | string | yes | _(none)_ | L2TP server to connect to.  Acceptable datatypes are hostname or IP address, with optional port separated by colon ':'.  Note that specifying port is only supported recently and should appear in DD release 
@@ -589,7 +589,7 @@ The name of the physical interface will be "l2tp-<logical interface name>".
 
 CAUTION: The package 'relayd' must be installed to use this protocol.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'network' | list of _logical interface names_ | yes | _(none)_ | Specifies the networks between which traffic is relayed 
@@ -611,7 +611,7 @@ The name of the GRE interface will be 'gre-<logical interface name>' for "gre" a
 
 All four protocols accept the following common options:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'mtu' | integer | no | 1280 | MTU 
@@ -631,7 +631,7 @@ All four protocols accept the following common options:
 
 The following options are supported, in addition to all common options above:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | IPv4 address | no | WAN IP | Local endpoint 
@@ -643,7 +643,7 @@ The following options are supported, in addition to all common options above:
 
 The following options are supported, in addition to all common options above:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | IPv4 address | no | WAN IP | Local endpoint 
@@ -656,7 +656,7 @@ The following options are supported, in addition to all common options above:
 
 The following options are supported, in addition to all common options above:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ip6addr' | IPv6 address | no | WAN IP | Local endpoint 
@@ -668,7 +668,7 @@ The following options are supported, in addition to all common options above:
 
 The following options are supported, in addition to all common options above:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ip6addr' | IPv6 address | no | WAN IP | Local endpoint 
@@ -683,7 +683,7 @@ The following options are supported, in addition to all common options above:
 
 VTI Tunnels are IPsec policies with a fwmark set. The traffic is redirected to the matching VTI interface.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ipaddr' | IPv4 address | no | WAN IP | Local endpoint 
@@ -699,7 +699,7 @@ VTI Tunnels are IPsec policies with a fwmark set. The traffic is redirected to t
 
 The following options are supported, in addition to all common options above:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'ip6addr' | IPv6 address | no | WAN IP | Local endpoint 
@@ -725,7 +725,7 @@ config device 'eth0.106'
 VLAN Interfaces may be configured also. If not, they are created on the fly by netifd. Defining VLANs gives more options.
 The following options are supported:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'type' | VLAN Type | no | 802.1q | VLAN type, possible values: 8021q or 8021ad 
@@ -757,7 +757,7 @@ config atm-bridge
 
 The 'atm-bridge' section allows the following options:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'unit' | number | yes | '0' | Specifies the br2684 interface number. If ommitted, '0' is assumed which would result in a 'nas0' pseudo interface. 
@@ -783,7 +783,7 @@ config vdsl 'dsl'
 
 The 'dsl' section allows the following options:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'annex' | string | yes | 'b' | Specifies the Annex setting (ISP/line dependent). Supported values on lantiq AMAZON and DANUBE devices: b, bdmt, b2, b2p, a, at1, alite, admt, a2, a2p, l, m, m2, m2p. Supported values on lantiq ARX100 "AR9" and VRX200 "VR9" devices: a, b, j
@@ -879,7 +879,7 @@ config 'route' 'name_your_route'
 
 Legal options for _IPv4 routes_ are:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'interface' | string | yes | _(none)_ | Specifies the _logical interface name_ of the parent (or master) interface this route belongs to; must refer to one of the defined 'interface' sections 
@@ -921,7 +921,7 @@ config 'route6'
 
 Legal options for _IPv6 routes_ are:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'interface' | string | yes | _(none)_ | Specifies the _logical interface name_ of the parent (or master) interface this route belongs to; must refer to one of the defined 'interface' sections 
@@ -937,7 +937,7 @@ Legal options for _IPv6 routes_ are:
 
 === Routing Types ===
 
-[options="header"]
+[cols="1,4",options="header"]
 |====
 | Type | Description 
 | 'unicast' | the route entry describes real paths to the destinations covered by the route prefix. 
@@ -986,7 +986,7 @@ config rule6
 
 The options below are defined for _IP rule_ ('rule' and 'rule6') sections:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'in' | string | no | _(none)_ | Specifies the incoming _logical interface name_ 
@@ -1004,7 +1004,7 @@ The options below are defined for _IP rule_ ('rule' and 'rule6') sections:
 
 === Routing Actions ===
 
-[options="header"]
+[cols="1,4",options="header"]
 |====
 | Action | Description 
 | 'prohibit' | When reaching the rule, respond with _ICMP prohibited_ messages and abort route lookup 

diff --git a/docs/uci_system.txt b/docs/uci_system.txt
index d0aaf1309bd572cc21e8fa413b6d64fa70476ad5..a829b4d52e0f64cec2edd92032d5f6600ea3c0c7 100644 (file)
--- a/docs/uci_system.txt
+++ b/docs/uci_system.txt
@@ -17,7 +17,7 @@ config 'system'
 
 These options can be set in the system section:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'hostname' | string | no | 'OpenWrt' | The hostname for this system. Avoid points, even if they are within single7double quotes. For example ' 'my.hostname' ' will show only the ' 'my' ' part 
@@ -60,7 +60,7 @@ config 'timeserver' 'ntp'
 
 There are at least two valid option defined for the 'timeserver' 'ntp' section:
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'server'        | list of hostnames | no | _(none)_ | Defines the pool of NTP servers to poll the time from. If the list is empty, the builtin NTP daemon is not started. 
@@ -108,7 +108,7 @@ opkg install kmod-ledtrig-morse --force-depends
 
 The LED is always in default state. Unlisted LED are default OFF, so this is only useful to declare a LED to be always ON.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -123,7 +123,7 @@ The LED blinks with the configured on/off frequency.
 opkg install kmod-ledtrig-timer
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -140,7 +140,7 @@ The LED is ON. Deprecated, use default=1 trigger=none instead.
 opkg install kmod-ledtrig-default-on
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -154,7 +154,7 @@ The LED flashes to simulate actual heart beat _thump-thump-pause_. The frequency
 ----
 opkg install kmod-ledtrig-heartbeat
 ----
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -168,7 +168,7 @@ Note:_to test the heartbeat take a look at [[doc:howto:snippets#generate.100.cpu
 
 The LED flashes as data is written to flash memory.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -183,7 +183,7 @@ The LED flashes with link status and/or send and receive activity on the configu
 opkg install kmod-ledtrig-netdev
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -202,7 +202,7 @@ triggers have more events, it also provides possibility of static LED setup in c
 radio ('phy0' usually) and 5 GHz radio ('phy1' usually) separately. 'netdev' can't guarantee this distinguishing
 since 'wlan0' may be referring to 2.4 GHz or 5 GHz radio based on current network setup.
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -223,7 +223,7 @@ The LED turns ON if USB device is connected.
 opkg install kmod-ledtrig-usbdev
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -244,7 +244,7 @@ Requires the kmod-ledtrig-morse package. UCI configuration was added in revision
 opkg install kmod-ledtrig-morse
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -264,7 +264,7 @@ Allows LEDs to be controlled by gpio events.
 opkg install kmod-ledtrig-gpio
 ----
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON 
@@ -289,7 +289,7 @@ opkg install kmod-ledtrig-netfilter
 ----
 
 
-[options="header"]
+[cols="4*1,4",options="header"]
 |====
 | Name | Type | Required | Default | Description 
 | 'default' | integer | no | 0 | LED state before trigger: '0' means OFF and '1' means ON