IPv6 Network Allocations

The MFN Project operates a shared IPv6 network with more than
enough addressing space for the project and its members to make
use of for their various needs. This page list the current allocations
and who is making use of them.

Deployed IPs:
0.3% of our /48 (Last calc'd Jan 3rd, 2024)

MFN Reserved Allocations
These allocations are used internally by the project and cannot be
assigned to members for general use. The information listed here
is made public because security by obscurity is not security at all.
Anyone who really wants to know the network structure, who has the
time and resources, will enumerate the network eventually anyway.

2604:4300:f03::/64 - MFN IPv6 Backplane
The backplane bridge and router are currently configured in a set of
/127 subnets and VLANs to work around a virtIO driver bug on our
OPNsense routers.

                2604:4300:f03::/64 -VLAN'd - IPv6.fenfox.run (Live)
               
2604:4300:f03::1 - catos.fenfox.run (Live)
                2604:4300:f03::3 - routed.fenfox.run (Live)
                2604:4300:f03::5 - ikus.fenfox.run (Live)
                2604:4300:f03::7 - cx.fenfox.run (Live)

2604:4300:f03:1::/64 - MFN Services via routed.fenfox.run
               2604:4300:f03:1::2 - Web Services                 
               2604:4300:f03:1::3 - Support Desk (This page)
               2604:4300:f03:1::4 - Mail Service                   
               2604:4300:f03:1::5 - Support Desk                 
               2604:4300:f03:1::6 - Adrian
               2604:4300:f03:1::7 - Flight Deck

2604:4300:f03:2::/64 - Interconnects for members
               
2604:4300:f03:2::/120 - Deployed on Catos
               2604:4300:f03:2::100/120 - Deployed on Ikus
               2604:4300:f03:2::200/120 - Deployed on CX
               Remaining Address Space - Reserved for future use
                      These interconnect ranges are to be further
                      cut into /126s for routing to members; but 
                      are not for any member's general use!


 

MFN Member Allocations (Active)

Member allocations are those that we route over wireguard to our
project members for their use in their homelabs or networks. Anyone
who is a member can request a /64 from us. Projects with multiple
sites and endpoints may request a /58 from us, but it will have to
be justified.

2604:4300:f03:40::/58 - Router Pool #1 via catos.fenfox.run
       
2604:4300:0f03:0040::/64 - MFN_VT_Shared (MFN)
        2604:4300:0f03:0041::/64 - Leased to project member, Kyru

2604:4300:f03:80::/58 - Router Pool #2 via ikus.fenfox.run
        2604:4300:f03:80::/64 - MFN_VT_Shared (MFN)
        2604:4300:f03:81::/64 - Lanny Leased (Project Member)

2604:4300:f03:c0::/58 - Router Pool #3 via cx.fenfox.run
        2604:4300:f03:c0::/64 - Hosted Services Net (MFN)

        2604:4300:f03:100::/64 - Used Internally for Punch Deck 01
        2604:4300:f03:101::/64 - Used Internally for Punch Deck 02
        2604:4300:f03:102::/64 - Flight Deck Internetworking

MFN Member Allocations (Reserved)

Reserved member allocations are for request that have been approved
by our volunteer staff but the requester has asked that we not place the
allocation into service yet. This is normally done when the requester is
working on building themselves a router or otherwise preparing their
network for ipv6 traffic.

No reserved allocations at this time.

<---Network Wide DNS Settings--->

The addresses below are what we use for DNS across our network
for all of our internal resources and the public facing rVPN routers:
9.9.9.9 and 149.112.112.112 for IPv4.
2620:fe::fe and 2620:fe::9 for IPv6.
These are external DNS services operated by Quad9 and not managed
by MFN in any way.
MFN Project members are not restricted from using their own choice of DNS servers within their
environment. We provide on network DNS by default to make things easier to deploy.


Article Details

Article ID:
1
Category:
Rating :