Our contributions to free software
Our infrastructure runs on open source. Giving back is only natural: upstream-accepted fixes, published code, shared tools.
At RDEM Systems, we operate our own BGP network (AS206014), our Proxmox virtualization and our backups on free software. These are the very same building blocks we operate for our clients under managed Linux server services: the code we patch runs in production, on our systems and on theirs. When we hit a bug or a gap, we don't settle for a local workaround: we fix it at the source and submit the patch upstream.
Two recent contributions illustrate this approach: a BGP fix accepted upstream in FRRouting, and NimbusBackupClient, our open-source Windows-to-Proxmox Backup Server client, fully rewritten and given a graphical interface.
FRRouting — extended-size BGP messages (RFC 8654)
A fix accepted and merged into the official project
FRRouting (FRR) is the reference free-software routing suite (BGP, OSPF, IS-IS, PIM…), used by operators and datacenters worldwide. It's the engine that powers our autonomous network: the BGP sessions, peering and prefix announcements of AS206014 and its transit providers all run on this daemon — a bug in FRR is a bug in our production.
We identified and fixed a flaw in the reception of extended-size BGP messages (RFC 8654): the bgpd daemon could stay stuck on the historical 4096-byte limit instead of accepting messages up to 65535 bytes. The fix recomputes the receive limit at capability-negotiation time, rather than relying on a stale value.
PR #22423 — merged
master branch · original fix
PR #22543 — merged
Backport to stable/10.5
PR #22544 — merged
Backport to stable/10.6
PR #22545 — merged
Backport to stable/10.7
The fix was merged into the development branch and then backported by the maintainers to three stable releases (10.5, 10.6, 10.7): it now benefits every FRRouting user, not just our infrastructure.
NimbusBackupClient — Windows-to-PBS backup
Open-source GUI client, fully rewritten by us
There was no decent graphical client to back up a Windows machine to Proxmox Backup Server (PBS). We started from the command-line project tizbac/proxmoxbackupclient_go and reworked it entirely: a graphical interface (Go + Wails), a Windows service mode, application-consistent backups via VSS, and infrastructure-as-code automated deployment.
The story doesn't stop at our fork: Tiziano Bacocco, author of the original project, invited us to contribute that graphical interface back to his repository. We walk through this Windows GUI merge into the upstream proxmoxbackupclient_go repository on the NimbusBackup blog.
Consistency & security
VSS snapshots, certificate pinning, input validation, SHA-256 checksums and build attestations.
GUI or service
Bilingual EN/FR interface with real-time monitoring, or Windows service mode with built-in scheduling. Multiple PBS servers.
Infrastructure-as-code
JSON-file configuration, deployment with no interactive step. Smart exclusions (VSS, recycle bin, page file…).
Why we contribute
A technical stance, not just marketing
Fixing at the source avoids local patches and invisible technical debt.
An upstream-accepted fix is reviewed by maintainers: a mark of quality.
What we run every day, we can also read, debug and improve.
Infrastructure operated by the people who write the code
BGP network, virtualization, backup: we master our stack all the way down to the source code. Let's talk about your project.
Contact usContact
Address
5 B RUE DES NOYERS, 95300 PONTOISE, FRANCE