From f5d9feac95b7f16dca8aa2090f7638c5eca7d6f6 Mon Sep 17 00:00:00 2001 From: Matthias Radestock Date: Wed, 17 Sep 2014 19:24:32 +0100 Subject: [PATCH] note that local traffic isn't captured --- README.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index b5cb0d8d..8769081c 100644 --- a/README.md +++ b/README.md @@ -483,10 +483,14 @@ connected to the bridge is the weave router container, which is given the IP address & netmask supplied in 'weave launch'. A weave router captures Ethernet packets from its bridge-connected -interface in promiscuous mode, using 'pcap'. It forwards these packets -over UDP to weave router peers running on other hosts. On receipt of -such a packet, a router injects the packet on its bridge interface -using 'pcap' and/or forwards the packet to peers. +interface in promiscuous mode, using 'pcap'. This typically excludes +traffic between local containers, or between the host and local +containers, which is routed straight over the bridge by the +kernel. Captured packets are forwarded over UDP to weave router peers +running on other hosts. On receipt of such a packet, a router injects +the packet on its bridge interface using 'pcap' and/or forwards the +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