diff options
| -rw-r--r-- | docs/_include/interface-dhcpv6-options.txt | 13 | ||||
| -rw-r--r-- | docs/configuration/interfaces/ethernet.rst | 34 |
2 files changed, 47 insertions, 0 deletions
diff --git a/docs/_include/interface-dhcpv6-options.txt b/docs/_include/interface-dhcpv6-options.txt index e7eaffb1..e047e92a 100644 --- a/docs/_include/interface-dhcpv6-options.txt +++ b/docs/_include/interface-dhcpv6-options.txt @@ -1,4 +1,17 @@ .. cfgcmd:: set interfaces {{ var0 }} <interface> {{ var2 }} {{ var3 }} + {{ var5 }} {{ var6 }} dhcpv6-options duid <duid> + + The DHCP unique identifier (DUID) is used by a client to get an IP address + from a DHCPv6 server. It has a 2-byte DUID type field, and a variable-length + identifier field up to 128 bytes. Its actual length depends on its type. The + server compares the DUID with its database and delivers configuration data + (address, lease times, DNS servers, etc.) to the client. + + .. code-block:: none + + set interfaces {{ var0 }} {{ var1 }} {{ var2 }} {{ var4 }} {{ var5 }} {{ var7 }} duid '0e:00:00:01:00:01:27:71:db:f0:00:50:56:bf:c5:6d' + +.. cfgcmd:: set interfaces {{ var0 }} <interface> {{ var2 }} {{ var3 }} {{ var5 }} {{ var6 }} dhcpv6-options parameters-only This statement specifies dhcp6c to only exchange informational configuration diff --git a/docs/configuration/interfaces/ethernet.rst b/docs/configuration/interfaces/ethernet.rst index c1ee724b..25eebf25 100644 --- a/docs/configuration/interfaces/ethernet.rst +++ b/docs/configuration/interfaces/ethernet.rst @@ -66,6 +66,40 @@ Ethernet options set interfaces ethernet eth0 mirror eth1 +Offloading +---------- + +.. cfgcmd:: set interfaces ethernet <interface> offload <gro | gso | sg | + tso | ufo> + + Enable different types of hardware offloading on the given NIC. + + Generic segmentation offload is a pure software offload that is meant to deal + with cases where device drivers cannot perform the offloads described above. + What occurs in GSO is that a given skbuff will have its data broken out over + multiple skbuffs that have been resized to match the MSS provided via + skb_shinfo()->gso_size. + + Before enabling any hardware segmentation offload a corresponding software + offload is required in GSO. Otherwise it becomes possible for a frame to be + re-routed between devices and end up being unable to be transmitted. + + Generic receive offload is the complement to GSO. Ideally any frame assembled + by GRO should be segmented to create an identical sequence of frames using + GSO, and any sequence of frames segmented by GSO should be able to be + reassembled back to the original by GRO. The only exception to this is IPv4 + ID in the case that the DF bit is set for a given IP header. If the value of + the IPv4 ID is not sequentially incrementing it will be altered so that it is + when a frame assembled via GRO is segmented via GSO. + + .. warning:: Recent 1.3 rolling images also support XDP offloading which + stands for eXpress Data Path in the Linux Kernel. You must enable it for + every interface which should participate in the XDP forwarding. + + Enabling this feature will break any form of NAT or Firewalling on this + interface, as XDP is handled way earlier in the driver then NfTables. + + VLAN ==== |