[roll] Roll fuchsia [netstack3] Refactor how routes are added

Lookup the device for gateway routes before calling `add_entry` on the
`ForwardingTable`. Supplying a "complete" `Entry` to the
`ForwardingTable` when adding routes simplifies the API and makes it
easier to support looking up interface routing metrics in a future CL.

Original-Bug: 122489
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/813851
Original-Revision: a219677f17b91add74dc251fb533efef1232a7b0
GitOrigin-RevId: e82abc0214afa1444dba25d7ac253ca6e36d6aaa
Change-Id: Iaaf2947332c5e228433434938568d8c9fe6e74a4
1 file changed
tree: db0a7c50da2e6a9c481ff93bf24d585024ad08aa
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

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.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.