e63db5e7bb
This change allows the netstack to do NDP's Router Discovery as outlined by RFC 4861 section 6.3.4. Note, this change will not break existing uses of netstack as the default configuration for the stack options is set in such a way that Router Discovery will not be performed. See `stack.Options` and `stack.NDPConfigurations` for more details. This change introduces 2 options required to take advantage of Router Discovery, all available under NDPConfigurations: - HandleRAs: Whether or not NDP RAs are processes - DiscoverDefaultRouters: Whether or not Router Discovery is performed Another note: for a NIC to process Router Advertisements, it must not be a router itself. Currently the netstack does not have per-interface routing configuration; the routing/forwarding configuration is controlled stack-wide. Therefore, if the stack is configured to enable forwarding/routing, no Router Advertisements will be processed. Tests: Unittest to make sure that Router Discovery and updates to the routing table only occur if explicitly configured to do so. Unittest to make sure at max stack.MaxDiscoveredDefaultRouters discovered default routers are remembered. PiperOrigin-RevId: 278965143 |
||
|---|---|---|
| .. | ||
| BUILD | ||
| arp.go | ||
| checksum.go | ||
| checksum_test.go | ||
| eth.go | ||
| eth_test.go | ||
| gue.go | ||
| icmpv4.go | ||
| icmpv6.go | ||
| interfaces.go | ||
| ipv4.go | ||
| ipv6.go | ||
| ipv6_fragment.go | ||
| ipversion_test.go | ||
| ndp_neighbor_advert.go | ||
| ndp_neighbor_solicit.go | ||
| ndp_options.go | ||
| ndp_router_advert.go | ||
| ndp_test.go | ||
| tcp.go | ||
| tcp_test.go | ||
| udp.go | ||