As Marius said, there is no plug and play / universal setup, which I believe is good. Yes its frustrating at first, but when you do get it going at least you can say you learned something.

Everyones setup will be different, as is their understanding of Linux and networking.

I remember looking at the same wiki page quite some time back, and I was stumped at almost the very first step

ip link set dev ampr0 up

I'd get no such device returned as an error. I discovered the ampr0 naming convention wasn't liked by my flavor of Linux, it pretty much had to be tunl0 for me.

And from there many more things that took my mind quite a while to understand, specifically with the need for policy routing etc.

This is what I wrote after I had it working. An explanation that made sense to me. And I have tried to keep it to date in a minimal fashion to help others.

http://www.qsl.net/k/kb9mwr//wapr/tcpip/ampr-ripd.html

I have since done things differently. Rather than adding a USB network eth1, I use VLAN tags and a switch. And I never did really document the firewall stuff, which I do now as well.

Start small and work up from there is my suggestion. I always recommend starting by installing tcpdump and connecting directly to your modem (in a bridged mode if needed), and verifying the RIP traffic. From there you can see if your equipment can forward protocol 4 or DMZ correctly to whatever your gateway machine will be.

Steve, KB9MWR