iproute2: Fix some manpage typos
This patch fixes some of the typos found in iproute2 documentation. Signed-off-by: Petr Šabata <contyk@redhat.com>
This commit is contained in:
parent
a6d55bf0a0
commit
6274b0b759
|
|
@ -26,7 +26,7 @@ Read and load an arpd database from FILE in a text format similar to that dumped
|
||||||
the location of the database file. The default location is /var/lib/arpd/arpd.db
|
the location of the database file. The default location is /var/lib/arpd/arpd.db
|
||||||
.TP
|
.TP
|
||||||
-a <NUMBER>
|
-a <NUMBER>
|
||||||
With this option, arpd not only passively listens for ARP packets on the interface, but also sends brodcast queries itself. NUMBER is the number of such queries to make before a destination is considered dead. When arpd is started as kernel helper (i.e. with app_solicit enabled in sysctl or even with option -k) without this option and still did not learn enough information, you can observe 1 second gaps in service. Not fatal, but not good.
|
With this option, arpd not only passively listens for ARP packets on the interface, but also sends broadcast queries itself. NUMBER is the number of such queries to make before a destination is considered dead. When arpd is started as kernel helper (i.e. with app_solicit enabled in sysctl or even with option -k) without this option and still did not learn enough information, you can observe 1 second gaps in service. Not fatal, but not good.
|
||||||
.TP
|
.TP
|
||||||
-k
|
-k
|
||||||
Suppress sending broadcast queries by the kernel. This option only makes sense together with option -a.
|
Suppress sending broadcast queries by the kernel. This option only makes sense together with option -a.
|
||||||
|
|
|
||||||
|
|
@ -178,7 +178,7 @@ adress tables.
|
||||||
.sp
|
.sp
|
||||||
|
|
||||||
.B 4
|
.B 4
|
||||||
- STP BLOCKING state. Only valid if STP is eanbled on the bridge. This state
|
- STP BLOCKING state. Only valid if STP is enabled on the bridge. This state
|
||||||
is used during the STP election process. In this state, port will only process
|
is used during the STP election process. In this state, port will only process
|
||||||
STP BPDUs.
|
STP BPDUs.
|
||||||
.sp
|
.sp
|
||||||
|
|
@ -198,7 +198,7 @@ traffic back out of the receiving port.
|
||||||
.TP
|
.TP
|
||||||
.BR "fastleave on " or " fastleave off "
|
.BR "fastleave on " or " fastleave off "
|
||||||
This flag allows the bridge to immediately stop multicast traffic on a port
|
This flag allows the bridge to immediately stop multicast traffic on a port
|
||||||
that recieves IGMP Leave message. It is only used with IGMP snooping is
|
that receives IGMP Leave message. It is only used with IGMP snooping is
|
||||||
enabled on the bridge. By default the flag is off.
|
enabled on the bridge. By default the flag is off.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
|
@ -307,7 +307,7 @@ device is the bridge device.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
.BI master
|
.BI master
|
||||||
the vlan is configured on the sofware bridge (default).
|
the vlan is configured on the software bridge (default).
|
||||||
|
|
||||||
.SS bridge vlan delete - delete a forwarding database entry
|
.SS bridge vlan delete - delete a forwarding database entry
|
||||||
This command removes an existing fdb entry.
|
This command removes an existing fdb entry.
|
||||||
|
|
@ -361,7 +361,7 @@ the bridge device is not part of the syntax. This is a limitation of the
|
||||||
underlying netlink neighbour message protocol. When displaying the
|
underlying netlink neighbour message protocol. When displaying the
|
||||||
forwarding table, entries for all bridges are displayed.
|
forwarding table, entries for all bridges are displayed.
|
||||||
Add/delete/modify commands determine the underlying bridge device
|
Add/delete/modify commands determine the underlying bridge device
|
||||||
based on the bridge to which the coresponding ethernet device is attached.
|
based on the bridge to which the corresponding ethernet device is attached.
|
||||||
|
|
||||||
|
|
||||||
.SH SEE ALSO
|
.SH SEE ALSO
|
||||||
|
|
|
||||||
|
|
@ -108,7 +108,7 @@ control protocol so no userspace daemon is required - tunnels are
|
||||||
manually created by issuing commands at a local system and at a remote
|
manually created by issuing commands at a local system and at a remote
|
||||||
peer.
|
peer.
|
||||||
.PP
|
.PP
|
||||||
L2TPv3 is suitable for Layer-2 tunnelling. Static tunnels are useful
|
L2TPv3 is suitable for Layer-2 tunneling. Static tunnels are useful
|
||||||
to establish network links across IP networks when the tunnels are
|
to establish network links across IP networks when the tunnels are
|
||||||
fixed. L2TPv3 tunnels can carry data of more than one session. Each
|
fixed. L2TPv3 tunnels can carry data of more than one session. Each
|
||||||
session is identified by a session_id and its parent tunnel's
|
session is identified by a session_id and its parent tunnel's
|
||||||
|
|
@ -366,7 +366,7 @@ site-B:# modprobe nf_degrag_ipv4
|
||||||
.fi
|
.fi
|
||||||
.PP
|
.PP
|
||||||
If L2TP is being used over IPv6, use the IPv6 degrag module.
|
If L2TP is being used over IPv6, use the IPv6 degrag module.
|
||||||
.SH INTEROPABILITY
|
.SH INTEROPERABILITY
|
||||||
.PP
|
.PP
|
||||||
Unmanaged (static) L2TPv3 tunnels are supported by some network
|
Unmanaged (static) L2TPv3 tunnels are supported by some network
|
||||||
equipment equipment vendors such as Cisco.
|
equipment equipment vendors such as Cisco.
|
||||||
|
|
|
||||||
|
|
@ -212,7 +212,7 @@ specifies the physical device to act operate on.
|
||||||
.TP
|
.TP
|
||||||
.BI dev " DEVICE "
|
.BI dev " DEVICE "
|
||||||
.I DEVICE
|
.I DEVICE
|
||||||
specifies network device to operate on. When configuring SR-IOV Virtual Fuction
|
specifies network device to operate on. When configuring SR-IOV Virtual Function
|
||||||
(VF) devices, this keyword should specify the associated Physical Function (PF)
|
(VF) devices, this keyword should specify the associated Physical Function (PF)
|
||||||
device.
|
device.
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -84,7 +84,7 @@ ip-tunnel - tunnel configuration
|
||||||
.B tunnel
|
.B tunnel
|
||||||
objects are tunnels, encapsulating packets in IP packets and then
|
objects are tunnels, encapsulating packets in IP packets and then
|
||||||
sending them over the IP infrastructure.
|
sending them over the IP infrastructure.
|
||||||
The encapulating (or outer) address family is specified by the
|
The encapsulating (or outer) address family is specified by the
|
||||||
.B -f
|
.B -f
|
||||||
option. The default is IPv4.
|
option. The default is IPv4.
|
||||||
|
|
||||||
|
|
@ -163,7 +163,7 @@ changes.
|
||||||
.B nopmtudisc
|
.B nopmtudisc
|
||||||
disable Path MTU Discovery on this tunnel.
|
disable Path MTU Discovery on this tunnel.
|
||||||
It is enabled by default. Note that a fixed ttl is incompatible
|
It is enabled by default. Note that a fixed ttl is incompatible
|
||||||
with this option: tunnelling with a fixed ttl always makes pmtu
|
with this option: tunneling with a fixed ttl always makes pmtu
|
||||||
discovery.
|
discovery.
|
||||||
|
|
||||||
.TP
|
.TP
|
||||||
|
|
|
||||||
|
|
@ -273,7 +273,7 @@ are still deemed to have this size. Defaults to zero.
|
||||||
.TP
|
.TP
|
||||||
ewma log
|
ewma log
|
||||||
When CBQ needs to measure the average idle time, it does so using an
|
When CBQ needs to measure the average idle time, it does so using an
|
||||||
Exponentially Weighted Moving Average which smoothes out measurements into
|
Exponentially Weighted Moving Average which smooths out measurements into
|
||||||
a moving average. The EWMA LOG determines how much smoothing occurs. Defaults
|
a moving average. The EWMA LOG determines how much smoothing occurs. Defaults
|
||||||
to 5. Lower values imply greater sensitivity. Must be between 0 and 31.
|
to 5. Lower values imply greater sensitivity. Must be between 0 and 31.
|
||||||
.P
|
.P
|
||||||
|
|
|
||||||
|
|
@ -184,7 +184,7 @@ are still deemed to have this size. Defaults to zero.
|
||||||
.TP
|
.TP
|
||||||
ewma log
|
ewma log
|
||||||
When CBQ needs to measure the average idle time, it does so using an
|
When CBQ needs to measure the average idle time, it does so using an
|
||||||
Exponentially Weighted Moving Average which smoothes out measurements into
|
Exponentially Weighted Moving Average which smooths out measurements into
|
||||||
a moving average. The EWMA LOG determines how much smoothing occurs. Lower
|
a moving average. The EWMA LOG determines how much smoothing occurs. Lower
|
||||||
values imply greater sensitivity. Must be between 0 and 31. Defaults
|
values imply greater sensitivity. Must be between 0 and 31. Defaults
|
||||||
to 5.
|
to 5.
|
||||||
|
|
|
||||||
|
|
@ -99,7 +99,7 @@ u32 ematch
|
||||||
.IR ALIGN " := { " u8 " | " u16 " | " u32 " }
|
.IR ALIGN " := { " u8 " | " u16 " | " u32 " }
|
||||||
|
|
||||||
.SS ipset
|
.SS ipset
|
||||||
test packet agains ipset membership
|
test packet against ipset membership
|
||||||
.ti
|
.ti
|
||||||
.IR ipset "( " SETNAME " " FLAGS " )
|
.IR ipset "( " SETNAME " " FLAGS " )
|
||||||
|
|
||||||
|
|
|
||||||
|
|
@ -20,7 +20,7 @@ BYTES ] [
|
||||||
]
|
]
|
||||||
|
|
||||||
.SH DESCRIPTION
|
.SH DESCRIPTION
|
||||||
FQ_Codel (Fair Queuing Controled Delay) is queuing discipline that combines Fair
|
FQ_Codel (Fair Queuing Controlled Delay) is queuing discipline that combines Fair
|
||||||
Queuing with the CoDel AQM scheme. FQ_Codel uses a stochastic model to classify
|
Queuing with the CoDel AQM scheme. FQ_Codel uses a stochastic model to classify
|
||||||
incoming packets into different flows and is used to provide a fair share of the
|
incoming packets into different flows and is used to provide a fair share of the
|
||||||
bandwidth to all the flows using the queue. Each such flow is managed by the
|
bandwidth to all the flows using the queue. Each such flow is managed by the
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue