mirror of
https://github.com/golang/go
synced 2024-11-22 21:40:03 -07:00
net: fix (*ipStackCapabilities).probe godoc
Change-Id: I2e5db6e7e9a7b3c84449d16b6bc32afe1d0ffee9 Reviewed-on: https://go-review.googlesource.com/c/go/+/308991 Trust: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com> Reviewed-by: Ian Lance Taylor <iant@golang.org>
This commit is contained in:
parent
7beb988a3b
commit
e12abe4bd6
@ -13,7 +13,7 @@ import (
|
||||
"syscall"
|
||||
)
|
||||
|
||||
// Probe probes IPv4, IPv6 and IPv4-mapped IPv6 communication
|
||||
// probe probes IPv4, IPv6 and IPv4-mapped IPv6 communication
|
||||
// capabilities.
|
||||
//
|
||||
// Plan 9 uses IPv6 natively, see ip(3).
|
||||
|
@ -14,13 +14,13 @@ import (
|
||||
"syscall"
|
||||
)
|
||||
|
||||
// Probe probes IPv4, IPv6 and IPv4-mapped IPv6 communication
|
||||
// probe probes IPv4, IPv6 and IPv4-mapped IPv6 communication
|
||||
// capabilities which are controlled by the IPV6_V6ONLY socket option
|
||||
// and kernel configuration.
|
||||
//
|
||||
// Should we try to use the IPv4 socket interface if we're only
|
||||
// dealing with IPv4 sockets? As long as the host system understands
|
||||
// IPv4-mapped IPv6, it's okay to pass IPv4-mapeed IPv6 addresses to
|
||||
// IPv4-mapped IPv6, it's okay to pass IPv4-mapped IPv6 addresses to
|
||||
// the IPv6 interface. That simplifies our code and is most
|
||||
// general. Unfortunately, we need to run on kernels built without
|
||||
// IPv6 support too. So probe the kernel to figure it out.
|
||||
|
Loading…
Reference in New Issue
Block a user