I am in the process of moving our two name servers from using IPtables for malicious domain blocking to using RPZs within BIND. If this works as I intend, it should cut back on the amount of upkeep involved in blocking known, high volume C&C lookups; making us quicker to update and add new domains to the list. Also, domains on this list will return NXDOMAIN.
Author: Adrian Alexdre (FurrIX, Network Operations Center)
Upkeep avali for FurrIX, typically hides in the NOC
I am happy to announce that both Marbled Fennec Networks and FurrIX have a full team of volunteers once again. We should be able to begin bringing the network back into an up to date state along with offering a broader range of services once the new team members are brought up to speed.
As it sits now, we have eight members working together to keep MFN and FurrIX operational. Feel free to take a look at our team page to see who all is volunteering and what parts of our projects they support!
I finally got a moment to check on what was going on with the secondary physical server and it appears something triggered some kind of bug in which the network interface started resetting randomly and would come back up at 100Mbps before dying again.
I don’t see an actual reason for this in the system logs, which is very puzzling…but after a system reboot and sending a tech to look at the server’s networking cable just to be sure- it appears the box is running okay again.
This means that we will need to keep an eye on this box and make sure we catch on to future possible errors before they take the system out.
I get this question a lot and usually my answer involves some kind of networking background and a bit of history as to how we got here.
This whole thing is really just a passion project that allows our team to learn about and toy with different network technologies, hosting solutions and gain a working knowledge how to tie everything together to provide our team and our users with IP transit and other little bits of hosting.
As of now, we provide the following public services:
- Two Nameservers
- Shared Web Hosting
- Two Shared IPv6 Routers
- Routed IPv6 subnets from our own network, deployed over Wireguard
- DayZ Server
- Two Minecraft Servers
- 7D2D Server
- IPv4 Site-2-Site Tunneling
- OpenShock Instance
- Photo Gallery
- FiveM Server
We provide the following tools to our team internally:
- eMail Server
- Status Tracker
- Hypervisor Interfaces
- IP Address Management Console
- Documentation Hub
- Private VRC Stream Server
- MQTT for Mesh Radios
- IRC for Discussions
- LibreNMS
- Network Planning Tools
Our main goal is to provide networking to other hobbyist, but the project has kind of grown beyond that scope as y’all can see. From a networking perspective, our services are provided through both a /44 subnet and a /48 subnet that we obtained through an LIR. Far as we can tell using HE’s Looking Glass, our network is the second largest being announced at our data center. We also may have way more address space than we could ever hope to deploy between our two physical servers.
The funny thing is that the IPv6 side got its start from wanting to play games, including VR, remotely from anywhere in Canada. Now look where we are!
Oh yea, on our team, we have one tech (myself), a finance dragon and two support goobers on a good day. Very small team running this ship and trying to keep it alive. Something to make note is that we do not make a penny off of this project, it is kept alive and running pretty much out of spite, nicotine, beer and lots of snacks.