anchor.diff:  
   ### <a id='overview'></a> Overview
   
  -Container-to-container networking integrates with [Garden-runC](./architecture/garden.html#garden-runc) in a [Diego](./diego/diego-architecture.html) deployment. The [CF Networking Release](https://github.com/cloudfoundry-incubator/cf-networking-release) includes several core components, as well as swappable components. 
  +Container-to-container networking integrates with [Garden-runC] in a Diego deployment. The CF Networking Release includes several core components, as well as swappable components. For more information about Garden-runC, see [Garden-runC](./architecture/garden.html#garden-runc) in _Garden_. For more information about Diego, see [Diego Components and Architecture](./diego/diego-architecture.html). For more information about the CF Networking release, see [CF Networking Release](https://github.com/cloudfoundry-incubator/cf-networking-release) on GitHub.
   
   To understand the components and how they work, see the diagram and tables below. The diagram highlights <%= vars.app_runtime_abbr %> components in blue and green. The diagram also highlights swappable components in red.
   
  
positive.code: owner: Container-to-Container Networking
  ---
  
  This topic provides an overview of how container-to-container networking works in <%= vars.app_runtime_full %> (<%= vars.app_runtime_abbr %>.
  
  <p class="note"><strong>Note:</strong> Container-to-container networking is not available for apps hosted on Windows.</p>
  
  
negative.code: 
  ### <a id='overlay-network'></a> Overlay Network
  
  Container-to-container networking uses an overlay network to manage communication between app instances.
  
  Overlay networks are not externally routable, and traffic sent between containers does not exit the overlay. You can use the same overlay network range for different <%= vars.app_runtime_abbr %> deployments in your environment.
  
  The overlay network range defaults to `10.255.0.0/16`. You can modify the default to any [RFC&nbsp;1918](https://tools.ietf.org/html/rfc1918) range that meets the following requirements:
  
  * The range is not used by services that app containers access.
  * The range is not used by the underlying <%= vars.app_runtime_abbr %> infrastructure.
  
  All Diego Cells in your <%= vars.app_runtime_abbr %> deployment share this overlay network. By default, each Diego Cell is allocated a /24 range that supports 254 containers per Diego Cell, one container for each of the usable IP addresses, `.1` through `.254`. To modify the number of Diego Cells your overlay network supports, see [Overlay Network](../devguide/deploy-apps/cf-networking.html#overlay) in _Configuring Container-to-Container Networking_.
  
  