From f68a2e607942122c64f3c67b61e5d1e857507413 Mon Sep 17 00:00:00 2001 From: hitchhooker Date: Sun, 5 Jan 2025 12:33:15 +0700 Subject: [PATCH] update table --- docs/src/networking.md | 54 +++++++++++++++--------------------------- 1 file changed, 19 insertions(+), 35 deletions(-) diff --git a/docs/src/networking.md b/docs/src/networking.md index a8ea6ac..0856c28 100644 --- a/docs/src/networking.md +++ b/docs/src/networking.md @@ -4,37 +4,12 @@ This document outlines the BGP routing configuration for our multi-homed network with connections to various internet exchanges and transit providers in Bangkok, -Hong Kong, Singapore, and Europe. Currently 3x 10G fibers are used for uplinks. +Hong Kong, Singapore, and Europe. Currently 3x 10G fibers are used for physical +uplinks. ## Bandwidth Scaling bandwidth -## BGP Community Structure - -We use BGP communities to classify and manage routes based on their origin and characteristics. Our community format is `AABBCC`, where: - -- `AA`: Region/Type - - `10`: Local (Bangkok) - - `20`: Regional - - `30`: Remote -- `BB`: Provider - - `10`: BKNIX - - `20`: AMS-IX - - `30`: IPTX - - `40`: Reserved for future use -- `CC`: Connection Identifier - - `00`: Primary connection - - `01-99`: Additional connections, ordered by preference - -### Key Communities - -- 101000: BKNIX Primary (Local 10G - Bangkok) -- 102000: AMS-IX Bangkok Primary (Local 1G - Bangkok) -- 201000: AMS-IX Hong Kong Primary (Regional 200M - Hong Kong) -- 203000: IPTX Singapore Primary (Regional 500M - Singapore) -- 203001: IPTX Hong Kong Secondary (Regional 500M - Hong Kong) -- 302000: AMS-IX Europe Primary (Remote 100M - Amsterdam) - # Network Topology Diagram ```mermaid graph TD @@ -83,14 +58,23 @@ graph TD ## Routing Configuration -| Name | Speed | Path Prepend | MED | Local Pref | Community | Description | Edge Router | -|-------------------|-------|--------------|-----|------------|--------------|--------------------| ----------- | -| BKNIX | 10G | 0 | 50 | 200 | 142108:101000| LOCAL-BKNIX-PRIMARY | BKK10 | -| AMS-IX Bangkok | 1G | 0 | 100 | 190 | 142108:102000| LOCAL-AMSIX-PRIMARY | BKK20 | -| IPTX Singapore | 500M | 1 | 150 | 185 | 142108:203000| REGIONAL-IPTX-SG-PRI| BKK20 | -| IPTX Hong Kong | 500M | 1 | 150 | 180 | 142108:203001| REGIONAL-IPTX-HK-SEC| BKK10 | -| AMS-IX Hong Kong | 200M | 2 | 200 | 170 | 142108:201000| REGIONAL-AMSIX-HK-PRI| BKK10 | -| AMS-IX Europe | 100M | 3 | 300 | 160 | 142108:302000| REMOTE-AMSIX-EU-PRI | BKK20 | +| Name | Speed | Path Prepend | MED | Local Pref | External Communities | Description | Router | +|-------------------|-------|--------------|-----|------------|-------------------|-------------|---------| +| BKNIX | 10G | 0 | 10 | 200 | 142108:1:764 | Local IX | BKK10 | +| AMS-IX Bangkok | 1G | 0 | 20 | 190 | 142108:1:764 | Local IX | BKK20 | +| IPTX Singapore-BKK10 | 500M | 1 | 50 | 170 | 142108:2:35 | Regional Transit | BKK10 | +| IPTX Singapore-BKK20 | 500M | 1 | 50 | 160 | 142108:2:35 | Regional Transit | BKK20 | +| AMS-IX Hong Kong | 200M | 2 | 100 | 150 | 142108:2:142 | Regional IX | BKK20 | +| IPTX HK-BKK20 | 500M | 2 | 100 | 130 | 142108:2:142 | Regional Transit | BKK20 | +| IPTX HK-BKK10 | 500M | 2 | 100 | 120 | 142108:2:142 | Regional Transit | BKK10 | +| AMS-IX EU | 100M | 3 | 200 | 100 | 142108:2:142 | Remote IX | BKK10 | + +This way: +1. We keep our internal communities for our own routing decisions +2. We share geographic information allowing peers to optimize their routing +3. Peers can make informed decisions about traffic paths to our network + +Would this be a useful approach? ## Traffic Engineering Principles