Skip to content

WAN / ISP Business — Pointer & Relationship to the Metro Design

Related pages

This is the separate WAN/ISP business (AS 204258). The corporate internet edge is in WAN & Internet Edge.

Full design: wan/WAN-DESIGN.md

The retail internet service (PPPoE, public IPs) is a separate business with its own design: AS 204258, 185.109.40.0/22 + 2a06:4e80::/29, its own border routers (bdr-1/2, replacing the Brocade CER2024), BNG, RADIUS/billing, LibreNMS instance, and addressing plan. It is not part of the corporate network in DESIGN.md.

How the two designs relate

  • The metro is an arm's-length L2 circuit supplier to the WAN business. It delivers, on tagged hand-off ports at the colo:
  • one VLAN per rooftop POP (BGP-VPLS hub-and-spoke, dual hand-off with DF multihoming),
  • a management VLAN per POP for the rooftop switch,
  • the transit-B backhaul from the Mathew St hub,
  • all at ≥ 1520 L2 MTU end-to-end. Circuit-order requirements: WAN-DESIGN §2.1. The metro-side delivery mechanics (why VPLS, rooftop access layer, RT policy, MTU) remain documented in DESIGN.md §9.
  • Where WAN-DESIGN supersedes DESIGN.md §9: the BNG peers eBGP with the WAN business's border routers — not the colo CCRs — so retail public traffic never enters the corporate routing domain at all. The corporate core carries it only as opaque payload inside VPLS.
  • Shared physical infrastructure (deliberate, and only these):
  • the colo OOB network, switch, and console server (DESIGN.md §7.3; WAN-DESIGN §8) — one OOB serves both businesses;
  • the metro acting as L2 carrier, above;
  • a common hardware family (CCR2004) — one spares pool.
  • No shared L3 anywhere. Corporate = 10/8 (+ guest 172.16/12); WAN business = 185.109.40.0/22, 2a06:4e80::/29, and 100.64/16 internals. Address family alone identifies the business.