Our “Network Management Policy” has been updated to reflect some changes
that had to be put in place regarding the operation of our two public DNS
servers. Project members and end users who make use of the public DNS servers
should take a quick glance over the policy and make note of the changes.
In short, Marbled Fennec Networks will react to sudden increases in DNS traffic
and, where warranted, will block the resolution of queries headed for what is
known as “Command and Control” servers when it comes to suspected malware.
Our team will do their best to research the domains behind the traffic spikes
before applying any network rules.
Category: Network
Post dealing with changes to how we route packets and configure our network.
Our network fennec found a few issues in our network stack that need to be resolved. One router ran out of space because debugging was left enabled and another because ntopNG hadn’t been cleared out recently. Some old rules were found from old tenants and SSL certs had expired. I guess things happen when you take a month off from upkeep.
Our team is working to resolve these issues and restore performance back to Ikus and CX routers. So far, the old firewall rules have been removed, a ton of logging data was chunked out and most SSL certs have been brought up to date.
Our team managed to get three server and two routers updated today, so some of the work log has been cleared. Still have three routers to update and a handful of VPS instances.
Side note, due to issues outside of MFN’s control, our project manager has left the project. Starting tomorrow, the PM position will be open for members and VTs to apply for, if they wish to take a go at running the project. If interested, get in contact with Skylar.