[roll] Roll fuchsia [netcfg] Allow forwarding based on device class

This change adds a configuration section to allow forwarding on a device
based on its device class.

A new integration test checks both the positive and negative cases of
interfaces having a configuration installed based on the class. The
previous API implied that extensions to `KnownServiceProvider::Manager`
tests would require additional arguments, but this didn't appear to
scale well in the actual implementation. That's modified to now check
the used config, with the assumption that tests target specific
configurations. This can be improved if netcfg later is able to receive
a configuration as a FIDL message.

Original-Fixed: 94461
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/682947
Original-Revision: 180d6b0d3b5be9d697bbf57f0222bbd823fe3971
GitOrigin-RevId: e6ef649cfe974e4421d8db9b95d7ffe025b6e9ab
Change-Id: I237509d640cc7f64b849f09124f8f00c34a4d6af
1 file changed
tree: 9972e12b569333982b93881fbe1815915f2f0da3
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.