Browse Source

improve documentation

master
Marek Isalski 3 years ago
parent
commit
5819aa49e5
1 changed files with 60 additions and 53 deletions
  1. +60
    -53
      README.md

+ 60
- 53
README.md

@ -6,14 +6,14 @@
| 185.149.208.0/22 | Customer /32 (was acquired from LonsdaleNet) | Accept IPv4 /32 from Aggregation |
| 185.66.204.0/22 | Customer /32 (was acquired from Fibre WiFi) | Accept IPv4 /32 from Aggregation |
| 149.255.168.0/21 | Customer /32 (was acquired from Fibre WiFi) | Accept IPv4 /32 from Aggregation |
| 193.162.44.0/24 | Core and Loopbacks | (not announced to DFZ) |
| 193.162.44.0/24 | Core and Loopbacks | *Not announced to DFZ* |
| 172.22.0.0/16 | Management | Static |
| 172.22.0.0/24 | Infrastructure/Servers | Static /32, via Wireguard |
| 172.22.1.0/24 | OOB/Management at TN2 | Static /24, via Wireguard |
| 172.22.2.0/24 | OOB/Management at LD5 | Static /24, via Wireguard |
| 172.22.3.0/24 | OOB/Management at MA1 | Static /24, via Wireguard |
| 172.22.4.0/24 | OOB/Management at PUE | Static /24, via Wireguard |
| 100.64.0.0/10 | RFC6598 CGNAT for customer access | OSPF within agg network |
| 100.64.0.0/10 | RFC6598 CGNAT for customer access | PPPoE/OSPF within agg network |
| 169.254.0.0/16 | Link-local addressing for linknets | Used to establish BGP to Core |
## Core: Loopbacks and Linknets
@ -43,7 +43,7 @@
| 2a04:1840::/29 | Business Static /48 (can de-agg to /52) | Accept IPv6 /48-/52 from Aggregation |
| 2a0b:8640::/29 | Residential /56 (was acquired from Dyfed IT) | Accept IPv6 /40-/48 from Aggregation |
| 2a0d:a0c0::/29 | Residential /56 (was acquired from LonsdaleNET) | (will become like 2a0b:8640::/29 if required) |
| 2a10:f0c0::/29 | Core and Loopbacks (was acquired from FibreWiFi) | (not announced to DFZ) |
| 2a10:f0c0::/29 | Core and Loopbacks (was acquired from FibreWiFi) | *Not announced to DFZ* |
## Core: Loopbacks and Linknets
@ -83,56 +83,63 @@ Addressing within the prefix is as follows:
## `59811:2` send to aggregation routers
These are routes learned from ASNs that Voneus meets at 2 (or more) locations.
## `59811:666` DDoS and blackhole
Where:
* `/24` = only send to Voxility
* `/32` = announce to RTBH on ixs/upstreams/UTRS
## `65535:666` COMMUNITY-AS59811-BLACKHOLE
## `59811:6500x` originated from site
Where:
* `x` is from:
- `0` = all
- `1` = TN2
- `2` = LD5
- `3` = MA1
- `4` = PUE
## `650xy:zzzzz`
Where:
* `x` is from:
- `0` = all
- `1` = TN2
- `2` = LD5
- `3` = MA1
- `4` = PUE
* `y` is from:
- `0` = no-announce
- `1` = prepend 1
- `2` = prepend 2
- `3` = prepend 3
- `9` = no-export
* `z` is ASN, where:
- `0` = any peer/upstream/downstream
- `1299` = Arelion
- `2914` = NTT
- `3223` = Voxility (NB see also 59811:666)
- `6762` = TISparkle
- `65511` = Tampnet (would be 200781)
- `65521` = LON1
- `65522` = LON2
- `65523` = LINX Manchester
- `65524` = LINX Scotland
- `65525` = LONAP
Added to routes learned from peer ASNs that Voneus meets at 2 (or more) locations.
## `59811:666` announce for DDoS scrubbing
Accepted on `/24` routes only, and will:
* only work for routes where their aggregate could be announced to the DFZ
* will force that /24 to be announced to (and only to) Voxility for DDoS scrubbing
## `65535:666` blackhole
This is accepted on IPv4 `/32` routes and IPv6 `/56` through `/64`, and will:
* blackhole traffic within the core
* announce to RTBH on ixs/upstreams/UTRS
## `59811:6500x` learned through site
Added to routes learned from core sites. `x` is from:
* `0` = all
* `1` = TN2
* `2` = LD5
* `3` = MA1
* `4` = PUE
## `650xy:zzzzz` traffic engineering
Where `x` is from:
* `0` = all
* `1` = TN2
* `2` = LD5
* `3` = MA1
* `4` = PUE
And `y` is from:
* `0` = no-announce
* `1` = prepend 1
* `2` = prepend 2
* `3` = prepend 3
* `9` = no-export
And `z` is ASN:
* `0` = any peer/upstream/downstream
* `1299` = Arelion
* `2914` = NTT
* `3223` = Voxility (NB see also 59811:666)
* `6762` = TISparkle
* `65511` = Tampnet (would be 200781)
* `65521` = LON1
* `65522` = LON2
* `65523` = LINX Manchester
* `65524` = LINX Scotland
* `65525` = LONAP
# BGP Local Preferences

Loading…
Cancel
Save