Sunday, November 15, 2026
Transparency Report #020: Network changes, routing fixes and other fun stuff…
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 happened?! Why have y’all been so quiet???
Hey, it has been a while since our last update about the operation and upkeep of the
exchange, we apologize for that. Life kind of got in the way with our work seasons
picking back up full swing very suddenly and we got dragged under by it all. But do
not worry too much about FurrIX, the virtual exchange is still being worked and we
are trying our best to fit it in between our shifts.
TL;DR: we are not dead, just busy with real life.
Okay, but where did report #019 go?
We had drafted report nineteen about three weeks ago detailing some issues with BGP
and a fail router upgrade, but by the time of this posting, the report was so stale and old
that we decided to roll it into the report you’re reading right now and bring a bunch of
new with it!
Changes to the Exchange
- ASN and POP Changes:
FurrIX has been looking for and recently found an LIR over in the RIPE region that we
can agree on pricing and terms with. Nothing is set in stone just yet, and this is very
new territory for us, but we have applied for both transit and operational presence,
along with an ASN for FurrIX within the RIPE region. Hopefully the process goes smoothly
and we can let you all know more information within the next few weeks. Having an EU
network presence and custom routing would be a big jump for the vIXP project.
- BGP and our core:
When we were originally learning about BGP and designing our network core, we made
a few assumptions that worked on older versions of Opnsense, but promptly and silently
bit us square in the ass with the latest firmware updates. On all of our neighbor configs,
we were explicitly setting our internal AS65300 when it wasn’t needed. It took us a while
to realize what was happening and why due to the logs being less than helpful, but we
have fixed this so that BGP is live on our core once again and we have updated our NOC
playbooks to make note of only setting the ASN on peering neighbors and not internal,
though this will be phased out if the above paragraph becomes true.
We also learned that our external peering session with AS33371 would have never worked
properly because we need to enter Null6 routes for prefix scopes that aren’t physically
connected to our routers for them to announce our /44. NOC playbooks have been updated
and this has been solved as well.
- Network core domain:
With FurrIX leaning into the clubhouse and community vibe, we have decided to make
furrix.zone our public facing presence, governance, news blog and community resource
while obtaining maws-n-paws.exchange for the network itself. The routers will be moved
over to this new domain as time permits and peering will be on hold until this is done and
verified.
- Peering:
The entire point of this project is to connect with others and work together to have a real,
operationally mature and mildly governed network. As part of that, a lot of our policies are
being reworked to return to the clubhouse vibes FurrIX was built on. This includes our
peering agreement, which will be simplified and restructured to be easier to connect with
our network.
Are Exchange Operations Affected?
Actually, this time…Yes.
There have been a lot of updates going on in the last week to prepare for possible operation
changes and to get ready to throw switches when outside pieces fall into place. For our members
who are internal to our network, you will receive emails if your agreements and operations
involving FurrIX are affected, but most exchange members won’t be. For peers, who are external,
you will receive emails stating changes to BGP sessions, tunnel throttles and to update you on our
peering policy changes!