We got our routing adjusted upstream and will be making changes to our network to avoid what happened last week from being a future problem. During this time, our leased /48 may not operate properly.
Category: Network
Post dealing with changes to how we route packets and configure our network.
We got lucky and the config copy we had locally on my PC was able to get the router back up and going again without doing a full rebuild. Really not sure what happened, but something caused the firmware update to crash and it put the router in an unbootable state.
Networking should be up again, but I’ll need to do a look over to make sure everything is in place and working correctly.
As mentioned in this post a while back, our team has removed the NS entries for ‘multi.dns.marbledfennec.net’ from our name servers. We allowed a grace period for system and network admins to make the switch over to ‘dns.marbledfennec.net’ for a handful of months.
As of Jan 20th, devices and networks that are being setup to use our name servers should be pointing at ‘dns.marbledfennec.net’ as this entry is permanent and will not be changed.
We have processed disconnects for project members who have not be active for more than forty-five days. This means the related WireGuard profiles and PTR entries have been removed and those subnets have been returned to the pool.