Dependencies

There are not many dependencies required for the DN42 project, though among the dependencies there are multiple ways to achieve the same functionality.

What	Description	Cost	Who Pays/Provides
Public IP Address	Public IP for incoming VPN connections to the router	None	School (from their pool)
DNS Name (optional)	DNS name to point at the public IP, especially if the IP is dynamic	Negligible	Myself/School
Router	Physical or virtual router capable of running VyOS	$0-300	School (virtual or already purchased)/Myself
Server	Physical or virtual server(s) capable of hosting RPKI cache, DNS server, and looking glass	$0-35	School (virtual)/Myself (Raspberry Pi 3B)
Email Address (optional)	If the project is allowed to continue after end of year, then a delegated email address should be used for registration and public communication	None	School
DN42 IP ranges	Allocations assigned by the DN42 registry, which I must request	N/A	DN42
DN42 Peers	People I can peer with to join the network, most of whom I have to contact first	N/A	DN42 Members

The main variables are the router and server, which can come in many forms. Anything capable of running VyOS could work as the router, such as a Protectli, APU2/4, generic PC, or a VM. The supplementary services could also run in either a VM (ideal) or at worst run alongside each other on a Raspberry Pi server (less than ideal). It might also be possible to make the project cloud-hosted (making things like getting a public IP and DNS name easier), though that would incur much higher costs on a recurring basis.

After discussing with Adam: Router can be any black-box router that supports VyOS, server could be an Antsel One or NUC or similar. Public IP is difficult because firewalling changes as more peers are added.