Routing gear is switching namespaces!

For over a year now, our routing gear has been operating under the namespace ‘fenfox.run’, which was borrowed from Skylar to get this project off the ground and running. When it was just her working on things and the project mainly served her, this domain made sense.

But now the project is running pretty well and is serving multiple people for their IPv6 needs and is no longer just some fennec fox’s toy anymore. The project fleshed out and took on a nature of its own, and with that, a rebranding of the gear is due. As of July 31, 2024 the namespace ‘fenfox.run’ will begin being migrated away from and once done, will be released back to Skylar for personal use.

The routing gear will be moved to its new namespace of “FurrIX, a Furry Internet Exchange” along with the domain ‘furrix.zone’. This process should be mostly seamless for project members and end users. Since our routing gear serves more than just us (we provide connectivity to end users in the midwest who need v6 and don’t have it natively, provide connectivity to a mobile weather research guy down in Texas and so on) it makes sense for us to pick a name that describes the gear’s function better and is more inclusive.

As of August 15th, 2024 the domain ‘fenfox.run’ will no longer be in service within Marbled Fennec Networks.

fenfox.run has moved…

This should not affect any end users, but we have moved ‘fenfox.run’ over and into our name servers. This put both of our namespaces within our infrastructure. For the next few hours, end users might see two sets of name servers responding, since it takes time for the older data to age out.

[OPS/NOC] VTs, need your help!

Hey VTs,
Skylar needs you to crawl the network and check everything connected against our documentation. The network map had errors and some of our recent task got messed up. Please take a moment to crawl the network and let her know your findings, it would be very helpful to get a few more eyes on this.