Category: News Releases

Over the years, Marbled Fennec Networks has grown from a small hobbyist experiment into a surprisingly capable community platform. We’ve hosted projects, game servers, websites and countless experiments — and we’ve had a lot of fun doing it.

But as MFN evolved, so did the complexity of the systems behind it. MFN’s infrastructure has always relied on a deep stack of technologies: Debian Linux, Proxmox, pfSense/OPNsense, routing frameworks, BIND DNS and a lot of behind‑the‑scenes engineering work that most of us on the volunteer team never touched directly because it was outside of our knowledge. We mostly let our network engineer take specifications from us and make them happen- which is showing to have some strain over the years.

The truth to our projects splitting and MFN downsizing is simple:

Only one volunteer at MFN ever had the full technical knowledge required to maintain the networking and a majority of our infrastructure.

The rest of us — the people who now operate MFN — know how to:

• Maintain the WordPress website
• Manage our game servers through our panel
• Keep our small community spaces running for our various passions

But we do not have the background to safely operate the larger network, the routing layer or the virtualization environment that MFN depends on. When our sole infrastructure engineer expressed the need to step back and return to focusing on network engineering — instead of being the only person responsible for two entire projects — we had to make a responsible decision. We chose to reduce MFN’s scope to the parts we can confidently maintain:

• Our website
• Our game servers
• Our community projects
• Our history

Everything else — the network, the routing, the DNS, the infrastructure — was beyond our skillset. Continuing to operate those systems ourselves would have been unsafe, unsustainable and unfair to the community. This is why we asked FurrIX to take over the network layer, to allow our network engineer to pursue their passion and have less overall responsibility- but this change also gives our team the chance to learn how to handle the things we do host on our own. (And Adrian is still more than willing to walk us through things, thankfully!) FurrIX already had the technical foundation, the operational structure and the engineering expertise to safely run the parts of MFN that we could not.

We are simply operating at a scale that matches our abilities — and letting FurrIX handle the network‑engineering responsibilities that none of us were equipped to manage. This was a cooperative decision, made with transparency, respect and months of discussion. It allows MFN to continue existing in a sustainable form and it allows FurrIX to continue the technical legacy that originally grew out of MFN.

Thank you to everyone who has been part of MFN’s journey. We’re still here — just smaller, simpler and truer to our roots.

— The MFN Operators, Ty Dwagon and Riot the Yeen

We’ve been working on our agreement with FurrIX in the background and have reached what we deem to be an acceptable way of moving forward and ensuring the survival of both projects, as well as allowing us both to do our own thing on the same hardware. This new version is what is being used to govern interactions and responsibilities between both of our projects as of March 25th, 2026.

You can review the agreement at:
https://www.marbledfennec.net/separation-cooperation-agreement-gentlemans-agreementmfn-furrix/

We are working on redefining our operations agreement with FurrIX.

The major changes are that we are giving them direct control of the network allocations that we obtained from the LIR, just makes more sense for the vIX to have their contact and operations information in the records for both the /44 and /48. Our operations information will be placed into the name servers in the form of PTR records.

The second change is that we are considering a server rebuild with FurrIX that would result in MFN’s service becoming a nested virtualization, the details on this are still being worked out as time permits.

With FurrIX being spun off from MFN and into its own project, theres a loose agreement in
place that benefits both projects and allows them to coexist on the same physical servers
and routers. Mostly in who manages what being clearly defined now.

Marbled Fennec Networks:

• Provides the two name servers
• Maintains the IP allocations and leases them directly to FurrIX
• Maintains the game servers, email and support systems
• Provides support for their single user tunnels, managed by FurrIX
• Maintains the web host
• No longer touches or operates the routing or network VMs
• Maintains and provides physical infrastructure for both projects
• Provides financial backing for FurrIX until Jan 20th, 2028
• Maintains private peering with FurrIX via internal BGP

FurrIX, a Furry Virtual Internet Exchange:

• Directly leases the /44 and /48 IPv6 allocations without cost from Marbled Fennec Networks
• Maintains, designs and operates the network that forms the virtual internet exchange
• Provides and configures networking service(s) for Marbled Fennec Networks without cost
• Maintains the two name servers
• Maintains and Provides IP transit and tunneling services
• Maintains private peering with MFN via internal BGP
• Focuses solely on being a network service provider

Transitional Items of Interest:

• Ty Dwagon becomes the owner and operator of Marbled Fennec Networks
• Adrian/Skylar becomes the owner and operator of FurrIX
• The two projects provide one another with services that the other needs to function without cost and expectation (think settlement-free peering and sharing of the hardware/virtual environment)

This agreement is in place to the benefit of both projects and the spin off of FurrIX was done to
allow the virtual internet exchange to govern itself and expand at its own pace without approval
or interference from Marbled Fennec Networks, as long as network services are provided to
MFN on an as needed and requested basis. As of this post, FurrIX is no longer a subproject of Marbled Fennec Networks. It is a self governing, standalone project that we have entered into an agreement with for the foreseeable future.

Will we still be seeing the cute banners and VR pictures getting thrown up?

Yea, that won’t be changing. Adrian is still part of the VR crew and her pictures will still be featured on both our website and FurrIX’s. It is cute and we like it, adds a little character to both places.