[roll] Roll fuchsia [netcfg] Add bridge-specific upstream device class

Add a configuration option for device classes that can provide upstream
to bridged networks specifically.

Change the set of device classes allowed to provide upstream for
bridges from ethernet and WLAN to just ethernet, since wireless
bridging is unsupported (and unknown whether it can ever be properly
supported due to variations in AP implementations).

Test: fx test netcfg-test netstack-management-integration-test
Original-Fixed: 99318
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/717562
Original-Revision: 814216b7bdf2ec121a364030b34a4b3b3d3f510d
GitOrigin-RevId: dec8fb0018eba28db078a12b1b96639639de1aac
Change-Id: I573afae5b6e04ceaacb763de3ac6f7cddb44339c
1 file changed
tree: 693fee97fa7b31339db38279864d88adf2069134
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.