push more of the topology docs into the topology section
plus some cosmetics
This commit is contained in:
1 parent
13fc0bf720
commit
fc85e12556
1 file changed
+8
-17
+8
-17
@@ -12,9 +12,9 @@ different each time it is run. These are opaque identifiers as far as
|
||||
the router is concerned, although the name defaults to a MAC address.
|
||||
|
||||
Weave routers establish TCP connections to each other, over which they
|
||||
perform a protocol handshake and subsequently exchange topology
|
||||
information (see below). These connections are encrypted if so
|
||||
configured. Peers also establish UDP "connections", possibly
|
||||
perform a protocol handshake and subsequently exchange
|
||||
[topology](#topology) information. These connections are encrypted if
|
||||
so configured. Peers also establish UDP "connections", possibly
|
||||
encrypted, which carry encapsulated network packets. These
|
||||
"connections" are duplex and can traverse firewalls.
|
||||
|
||||
@@ -35,19 +35,11 @@ packet to peers.
|
||||
Weave routers learn which peer host a particular MAC address resides
|
||||
on. They combine this knowledge with topology information in order to
|
||||
make routing decisions and thus avoid forwarding every packet to every
|
||||
peer. The topology information captures which peers are connected to
|
||||
which other peers; weave can route packets in partially connected
|
||||
networks with changing topology.
|
||||
|
||||
For example, in this network, peer 1 is connected directly to 2 and 3,
|
||||
but if 1 needs to send a packet to 4 or 5 it must first send it to
|
||||
peer 3:
|
||||
![diagram showing five peers in a weave network][diagram1]
|
||||
Weave peers [communicate their own topology](#topology) with neighbours, who then
|
||||
pass on changes to their neighbours, and so on, until the entire
|
||||
network knows about any change.
|
||||
|
||||
[diagram1]: images/top-diag1.png "Diagram 1"
|
||||
peer. Weave can route packets in partially connected networks with
|
||||
changing topology. For example, in this network, peer 1 is connected
|
||||
directly to 2 and 3, but if 1 needs to send a packet to 4 or 5 it must
|
||||
first send it to peer 3:
|
||||

|
||||
|
||||
### <a name="encapsulation"></a>Encapsulation
|
||||
|
||||
@@ -191,7 +183,6 @@ If a peer, after receiving a topology update, sees that another peer
|
||||
no longer has any connections within the network, it drops all
|
||||
knowledge of that second peer.
|
||||
|
||||
|
||||
#### Out-of-date topology
|
||||
The peer-to-peer passing of updates is not instantaneous, so it is
|
||||
very possible for a node elsewhere in the network to have an
|
||||
|
||||
Reference in new issue
Block a user