Posts

Years ago, I created a site named wisptools.net. No, I’m not going to link to it - because somehow, it’s been purchased by a Russian adult-content company (no, I have no idea why, either). I had the idea for the site because I’d been visiting WISPAmerica in St. Louis, and discovered that the majority of WISP owners weren’t really doing any automated coverage; others were using Radio Mobile, Splat or TowerCoverage. Those are all fine solutions, but they didn’t scratch my itch.

Dynamic circuits appear quickly and vanish when they are no longer in use.

Sometimes, technical problems, licensing issues and the need to eat collide. API access to LibreQoS was one of those uncomfortable areas. In this post, we’ll talk about our design philosophy, competing needs that lead to the separation of the API, and how we’re working to find a happy medium in release 2.2.

When you want to add HTTPS to an existing LibreQoS installation - go to Configuration -> SSL:

Cuando terminamos de eliminar la penalización por recarga, desbloqueamos muchas opciones de desarrollo — muchas de ellas son funciones que la gente ha querido durante mucho tiempo. La más reciente son los circuitos dinámicos.

Soy Herbert, desarrollador principal de LibreQoS. Me uní poco después de que Robert y Dave iniciaran el proyecto, agregué soporte para IPv6 y creé la mayor parte de los componentes en Rust, C, etc.