Tuesday, June 16, 2026

[Transparency Report #009][OPERATIONS] BGP Is Enabled! (Internally)

What are Transparency Reports?
As a community‑operated and governed virtual internet exchange, FurrIX maintains
a commitment to open and honest communication with its members. From time to
time, operational work may occur that affects the exchange or its supporting infrastructure.
When this happens, the FurrIX operations team publishes a transparency report to
ensure all members remain informed. As a hobbyist‑rooted vIX, we aim to keep
communication clear, accessible and practical to the best of our ability.

What is happening?
This is a good thing for the exchange to have figured out. As of Jun 15th, we have learned
how to configure and enable BGP on OpnSense within the exchange. This means our techs
can now peer the exchange with member delegated /64s over /127 wireguard links! This is
a goal that we have been working towards, which also serves to get us moving towards our
goal of one day having a public ASN. Going forward, members who join the exchange will
have the option of having their /64 on-link or BGP peering with us an announcing their
/64 to our routing fabric.

Changes to the exchange:
- FurrIX Transit Fabric: Edge, Catos and Nardoragon are all peered using AS65300. Edge
announces a default route downstream, while the other two routers announce their assigned
/58s to the Edge.
- Exchange Member Peering: FurrIX has reserved AS65320 for peering with members of
our exchange, we also have started to rework our peering policies along with reserving
AS65400-65500 for member BGP sessions and AS65501-AS6550 for peering with other
hobbyist networks.

Changes Proposed:
Eventually FurrIX would like to add a BGP looking glass to our network that is peered
with the Edge that will should all ASNs and routes on the exchange, but this is a ways
off for the moment.

Are exchange operations affected?

Everything is operating normally, this was just quiet work in the background in order to
mature the exchange a little further and get to a point that we are reaching some of our
goals that were set for this year.

Tuesday, May 19, 2026

[Transparency Report #006][OPERATIONS] Full Environment Rebuild Scheduled (May 22–23)

What are Transparency Reports?
As a community‑operated and governed virtual internet exchange, FurrIX maintains
a commitment to open and honest communication with its members. From time to
time, operational work may occur that affects the exchange or its supporting infrastructure.
When this happens, the FurrIX operations team publishes a transparency report to
ensure all members remain informed. As a hobbyist‑rooted vIX, we aim to keep
communication clear, accessible and practical to the best of our ability.

What is happening?
FurrIX will be performing a full environment rebuild of its core infrastructure between
May 22nd and May 23rd. This maintenance window includes a comprehensive refresh
of the physical and virtual systems that support the exchange.
The following work is planned:
- Rebuilding the physical Proxmox host to ensure long‑term stability and alignment
with current operational standards
- Rebuilding all virtual routers, consolidating the routing layer down to three routers
for improved clarity and maintainability
- Transitioning the Games‑3P LXC container into a Games‑4P virtual machine, providing
better isolation and resource management
- Renumbering internal and service networks into FurrIX’s LIR‑assigned IPv6 ranges,
enabling the release of legacy datacenter‑provided address space
- General housekeeping tasks, including cleanup of unused resources, configuration
standardization and documentation updates

This work completes the post‑handoff cleanup following MFN’s network retirement and
removes legacy configurations that cannot be maintained in the current layout. It also
allow FurrIX the breathing room needed to ensure we can grow and control our operations
without legacy tooling getting in the way or having to rewrite large chunks of configuration.

Why this rebuild is needed
As FurrIX continues to mature into a vIX that tries to mimic the real world, several infrastructure
improvements are required to maintain operational clarity, reduce technical debt and ensure
long‑term sustainability:
- Infrastructure modernization: The current Proxmox host and routing layer have accumulated
legacy configurations from earlier phases of the project. A clean rebuild ensures consistency
and reliability.
- Routing simplification: Reducing to three routers improves manageability, reduces complexity
and aligns with the vIX’s current scale.
- Address space alignment: Moving fully into FurrIX’s LIR ranges allows the project to retire
datacenter‑assigned prefixes and operate with a clean, independent addressing plan.
- Service isolation: Migrating Games‑3P from an LXC container to a VM provides better performance
boundaries and operational flexibility.
- Operational hygiene: Housekeeping tasks ensure the environment remains maintainable and
well‑documented.

These changes support FurrIX’s goal of maintaining a clear governance boundary, a stable operational
footprint and a better run vIX while preserving its hobbyist openness.

What this means for members of the exchange
During the rebuild:
- Members may experience extended periods of routing instability or service unavailability during
the maintenance window. These interruptions will be minimized where possible, but the entire
vIX has to come offline for this work to be completed. We are aiming for no more than seven
hours of downtime, but have allotted two days in-case something unexpected happens.
- Member configuration changes will be required:
Member tunnel configurations, peering sessions and addressing assignments will require modification
and our volunteers will email new credentials and profiles soon as we are able to.
- No policy or governance changes:
This is strictly an infrastructure rebuild and does not affect membership, governance or peering policy.

Are exchange operations affected?

Yes — temporarily.
During the rebuild window, routing and service availability will be null as systems are rebuilt
and renumbered. Once the work is complete, normal operations will resume with improved
stability, ease of expansion, better rooted upkeep and clarity.