Category: Core

Information about how the board is doing, changes they bring to the table and things that have been successfully actioned by the board.

More network changes!

Adrian Alexdre
Posted by Adrian Alexdre Posted on August 8, 2024
Posted in Core, Network, News Releases, Operations

Hey guys,
As some of your probably have pieced together by now, I (Skylar) took back one of my personal domains that MFN was borrowing for about a year. With the fully complete launch of FurrIX, fenfox.run has been pulled out of service from MFN/FurrIX’s routing stack and FurrIX now has their own domain under the name “furrix.zone” that was donated to Marbled Fennec Networks by Skylar W. and Ty Dwagon.

The project has also leased an additional /48 from NoPKT to give our project members and end users a choice of whether they want to use ‘2604:4300:f03’ or ‘2602:f992:f3’ as their subnet space when we connect them to our network. Only catch is that we cannot set PTR records for the /48 that we leased.

We also reconfigured our name servers after not fully understanding how to setup DNSSEC. Everything should now be working as intended on both server for both of our zones. We are also offering to allow project members to make use of our name servers for their own domains. You’ll need to provide our techs with a BIND ready file and they will handle the rest. At the moment, there is no GUI front end for the name servers.

[OPS/NOC] VTs, need your help!

Adrian Alexdre
Posted by Adrian Alexdre Posted on July 29, 2024
Posted in Core, Network, Operations

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.

Changes to our routing stack!

Adrian Alexdre
Posted by Adrian Alexdre Posted on July 29, 2024
Posted in Core, Network

We have reached a point where our name servers are working well enough for daily use that we feel like we can cut down on some of the duplicate functionality in our routing stack. At present, each router in our stack is running its own instance of Unbound for client DNS and this leads to a bunch of duplication that is probably not needed and just adds to our hypervisor’s workload.

Starting around 1000EST today, we will be turning off each router’s Unbound instance and will be updating profiles to point their DNS at our two name servers. If you are an end user or project member and you notice that DNS functions stop working, you should update your connection profiles to point their DNS at the following addresses:

  • 204.12.237.197
  • 173.208.212.205
  • 2604:4300:f03:c1::2
  • 2604:4300:a:6e::5

For our WireGuard users, this most likely means replacing the line “DNS = 2604:4300:f03:XX::1, 10.0.XX.1” with the line “DNS = 2604:4300:f03:c1::2, 2604:4300:a:6e::5” to retain DNS functions after today. We know that our DNS changes have been a moving target for our project and our users, but this should wrap things up on that front.