os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use correct syntax markup for shell

Browse source 
Approved by:	carlavilla
This commit is contained in:
Li-Wen Hsu 2021-03-14 20:08:55 +08:00
parent 55c95407aa
commit a9a9e66105
No known key found for this signature in database
GPG key ID: 8D7BCC7D012FD37E
666 changed files with 17924 additions and 17924 deletions
Download patch file Download diff file Expand all files Collapse all files

16
documentation/content/en/books/developers-handbook/ipv6/chapter.adoc
View file

@ -164,7 +164,7 @@ Ordinary userland applications should use advanced API (RFC2292) to specify scop
In the kernel, an interface index for link-local scoped address is embedded into 2nd 16bit-word (3rd and 4th byte) in IPv6 address. For example, you may see something like:
[source,bash]
[source,shell]
....
fe80:1::200:f8ff:fe01:6317
....
@ -190,7 +190,7 @@ IPv6 link-local address is generated from IEEE802 address (Ethernet MAC address)
Here is an output of netstat command:
[source,bash]
[source,shell]
....
Internet6:
Destination Gateway Flags Netif Expire
@ -221,7 +221,7 @@ Therefore, this is unwise to enable net.inet6.ip6.accept_rtadv on routers, or mu
To summarize the sysctl knob:
[source,bash]
[source,shell]
....
accept_rtadv forwarding role of the node
--- --- ---
@ -288,7 +288,7 @@ and recompile the new kernel.
Then you can test jumbo payloads by the man:ping6[8] command with -b and -s options. The -b option must be specified to enlarge the size of the socket buffer and the -s option specifies the length of the packet, which should be more than 65,535. For example, type as follows:
[source,bash]
[source,shell]
....
% ping6 -b 70000 -s 68000 ::1
....
@ -297,7 +297,7 @@ The IPv6 specification requires that the Jumbo Payload option must not be used i
When an IPv6 packet is received, the frame length is checked and compared to the length specified in the payload length field of the IPv6 header or in the value of the Jumbo Payload option, if any. If the former is shorter than the latter, the packet is discarded and statistics are incremented. You can see the statistics as output of man:netstat[8] command with `-s -p ip6' option:
[source,bash]
[source,shell]
....
% netstat -s -p ip6
ip6:
@ -345,7 +345,7 @@ To process IP6 header, extension headers and transport headers easily, network d
`netstat -s -p ip6` tells you whether or not your driver conforms such requirement. In the following example, "cce0" violates the requirement. (For more information, refer to Section 2.)
[source,bash]
[source,shell]
....
Mbuf statistics:
317 one mbuf
@ -374,7 +374,7 @@ You can perform wildcard bind on both of the address families, on the same port.
The following table show the behavior of FreeBSD 4.x.
[source,bash]
[source,shell]
....
listening side initiating side
(AF_INET6 wildcard (connection to ::ffff:10.1.1.1)
@ -627,7 +627,7 @@ Note that the behavior is configurable in per-node manner, not per-SA manner (dr
The behavior is summarized as follows (see source code for more detail):
[source,bash]
[source,shell]
....
encapsulate decapsulate
--- ---