Keep in mind that the tunnel system of 44net is a mesh, not a star.
There is no default route that will get you routing to the various
disjoint subnets which make up the network.
That means that in order to participate fully in the mesh, you need
(at this moment) 648 routes via 460 distinct endpoints. Linux has
a clever way of doing this with a secondary routing table. FreeBSD,
Cisco, Mikrotik, etc. using conventional tunnel routing mechanisms
need to have 460 separate tunnel devices configured, with 648 subnets
routed to them. In addition, Linux can run a daemon to utilize the
RIP44 transmissions from amprgw to keep that table up to date instead
of having to fetch and process the flat file 'encap' table periodically.
It's probably better to configure some small appliance-grade processor
(such as a Raspberry Pi) with some variety of Linux to take advantage
of its secondary routing table mechanism rather than try to kludge
it in to some other kind of router.
- Brian