| commit | 4965bf9f3d5c856c953b4d192f39c9a9216fef85 | [log] [tgz] |
|---|---|---|
| author | Tony Gong <gongt@fuchsia.infra.roller.google.com> | Tue Jan 30 19:51:21 2024 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 30 11:54:25 2024 -0800 |
| tree | 892fda140e8735d9fb62e3a2498bf991e2a46615 | |
| parent | 844b744b5c4da21d2c57d1d5b6232d9233c2bd2a [diff] |
[roll] Roll fuchsia [netstack3] Map ICMPv6 AddrUnreachable to host
...unreachable as opposed to network unreachable. RFC 4443 Section 3.1
states:
If the reason for the failure to deliver is lack of a matching entry
in the forwarding node's routing table, the Code field is set to 0.
and later:
If the reason for the failure to deliver cannot be mapped to any of
other codes, the Code field is set to 3. Example of such cases are
an inability to resolve the IPv6 destination address into a
corresponding link address, or a link-specific problem of some sort.
Contrast the above with the equivalent behavior for IPv4 in RFC 1812
Section 5.2.7.1:
0 = Network Unreachable - generated by a router if a forwarding path
(route) to the destination network is not available;
1 = Host Unreachable - generated by a router if a forwarding path
(route) to the destination host on a directly connected network
is not available (does not respond to ARP);
In total, ICMPv4's host unreachable code and ICMPv6's address
unreachable code are essentially equivalent, and the latter should map
to host unreachable.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/982052
Original-Revision: 5b61ff9c10c77e2b997569726b60df19c8563d13
GitOrigin-RevId: df53d5059ba29893700747ac5c8271af651d769b
Change-Id: Ibdd0b111335f71db59dd0b9806ffcf776effd797
This repository contains Fuchsia's Global Integration manifest files.
All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.
Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.