forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
IPv4 to IPv6 address synthesis described in RFC6052.
Implement IPv4 to IPv6 address synthesis (RFC6052) to utilize the NAT64 on an IPv6 only network to connect to an IPv4 address literal. Currently, Chrome cannot access an IPv4 literal when the network is IPv6 only (such as when an IPv4 address is directly written in the Omnibox) because DNS64 cannot be used for IP literals. In order for the packets to use NAT64 in the network, Chrome will now append the IPv4 to IPv6 translation prefix (Pref64::/n) to the IPv4 address. Also add feature kUseNAT64ForIPv4Literal (default: enabled) in order to be able to disable this feature for debugging purposes. Bug: 915087 Change-Id: I7fc4324c6d5ac245dfa88e326cd6cedcf3296c64 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3691238 Commit-Queue: Momoka Yamamoto <momoka.my6@gmail.com> Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> Reviewed-by: Tsuyoshi Horo <horo@chromium.org> Reviewed-by: Adam Rice <ricea@chromium.org> Cr-Commit-Position: refs/heads/main@{#1058599}
- Loading branch information
1 parent
f313c28
commit f1accfc
Showing
16 changed files
with
839 additions
and
17 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.