Home /Modules/preferred-routers/README.md

README.md

preferred-routers/README.md · 50 line(s) · markdown

<img align="right" src="https://github.com/mearvk/SLeeLa/blob/master/images/debian/debian-logo.png" width="75" height="75" alt="SLeeLa">

Preferred Routers

Configuration-driven preferred/well-known routing anchors for SLeeLa HTTP implementations.

Purpose

The selector gives HTTP 1.0+ implementations a common policy layer for preferring national backbone/ISP and IXP anchors before regional and international interconnection roles. It does not install routes, alter the operating-system routing table, bypass ISP policy, or claim that a provider is objectively “perfect.”

The checked-in rating is a routing preference tier from 1–5. Tier 5 is the highest preference; it is not a latency, uptime, security, or quality measurement.

Data

Configuration

\preferred-routers.conf\ is read by the native selector. Set \country\, \preferred_role\, \min_score\, and \international\. Set \SLEELA_PREFERRED_ROUTER_CONFIG\ to override the configuration path.

Build

\\\`sh make \\\`

The HTTP build compiles this directory before checking HTTP 7/8/9 syntax. HTTP servers 1, 2 and 3 link the selector into their native startup path.

Data refresh

\\\`sh python3 refresh_peeringdb.py \\\`

Refresh is opt-in so normal builds remain deterministic and offline.

Safety / scope

This component is a route preference policy. Actual route installation and forwarding remain the responsibility of the host networking stack and authorized network operators.


SLeeLa

<p align="center"><img src="images/sleela/sleela-wordmark.svg" alt="SLeeLa — The Now. The Ingredient." width="560"></p> <p align="center"><img src="https://github.com/mearvk/SLeeLa/blob/master/images/sleela-programming-language-002.jpg" alt="SLeeLa Marketing Logo" width="560"></p>