{"version":"2.1.307","anchor":"sandbox-network-exclusions-add-private-ranges","canonical_anchor":"sandbox-network-exclusions-add-private-ranges","heading":"Sandbox network exclusions now include private address ranges","tier":"notice","area":"Sandbox","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/sandbox-network-exclusions-add-private-ranges","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Sandbox network exclusions now include private address ranges\n\nThe sandbox's default list of excluded network addresses now also covers common private and carrier address ranges\n\n**Unclear.** Whether these addresses are now allowed to bypass the sandbox's network handling or are now blocked is not settled.\n\n**What**\n\nThe sandbox's default list of excluded network addresses used to end at `host.docker.internal`. It now also includes:\n\n- `10.0.0.0\/8`\n\n- `172.16.0.0\/12`\n\n- `192.168.0.0\/16`\n\n- `100.64.0.0\/10`\n\nThe first three are private ranges, the kind used inside home and office networks. The last is a range internet providers use for shared addresses.\n\n**Why**\n\nThis changes how the sandbox's network handling treats addresses on internal networks.\n\n- Area: Sandbox\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}