44net-request@hamradio.ucsd.edu wrote:
I have had a couple requests to tailor my attempt to document setting up a Linux AMPRNet gateway for the Raspberry Pi.
I've just recently purchased a Pi and have been looking over the documentation, and I don't think it will work for what I'm trying to document.
I have a quite simple setup for a Raspberry Pi as a Linux AMPRnet gateway, but in my experience everyone's setup is different and what works fine for me is not what other people want to use.
My Raspberry Pi is in a datacenter so no NAT worries. It terminates all tunnels (IPIP) and users Marius' RIP daemon for automatic routing. This works very well after we have ironed out some problems.
It also runs a local copy of KA9Q NET which I access from home via "screen", and it forwards a subnet of 44 adresses via an IPsec tunnel to my home machine, where several of these addresses are used to provide other services (e.g. WWW).
The setup basically only brings up tunl0 and assigns an address, sets up a separate route table and rules for net-44, manually inserts a couple of routes and then fires up the ampr-ripd. Maybe 10 lines of bash code, that is all.
As I wrote, the setup is very simple and the details vary enough for it to be less useful to others than I thought. I forwarded my complete config to a fellow amateur who has a Raspberry Pi as well, ready for him to load it, but he never did that and somehow prefers to build it again for himself. And probably that is better anyway, as most of the fun of building such a thing is the studying of the matter and the debugging.
Tinkering with the Raspberry Pi and networking is like homebrewing, copying an existing configuration is like buying a shiny new Icom.
Rob