[roll] Roll fuchsia [overnet] Update circuit routes when new connections occur In order for a circuit node to connect to another node, it needs to receive a routing update identifying that node and how it can be reached. In order for a circuit node to *be connected to* by another node, it doesn't need anything; a connection comes in, identifies the node it came from, and all is well. This can occur if a new node's connection request to another node manages to race ahead of the routing updates produced by that node joining the network. As a result, a node can receive a connection from another node while not being able to connect back to that node. This is bad for Overnet, which needs to be able to freely establish connections to move handles around. The solution is to add a route to the routing table when we get a connection from a node we don't recognize. We have to score it low on link quality because we don't know how fast it is without the quality information that comes in a routing update, but as long as it's present we can connect back to any node that connects to us. Original-Fixed: 120884 Original-Bug: 119353 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/797149 Original-Revision: 4d565cc90e29ccb4463df598f30b8032dcb85a72 GitOrigin-RevId: 0afd62ca45c3b3e2dc9f5282bf42ec719bf43b5a Change-Id: I00d817ee76933bd480f26c53853accc1af3a2e35
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.