I had to setup many AMPRnet gateways on Linux machines and I always had a hard time remembering the different steps, so I try to provide a quick start over here.<\/p>\n
I have been using the RIP44d deamon for all my installations, so we’ll start with downloading the current version of RIP44d:<\/p>\n
sudo wget -O \/usr\/local\/sbin\/rip44d\u00a0https:\/\/raw.github.com\/hessu\/rip44d\/master\/rip44d<\/p><\/blockquote>\n
The file needs to be executable by root<\/p>\n
sudo chmod 744\u00a0\/usr\/local\/sbin\/rip44d<\/p><\/blockquote>\n
Next we need is a starter script which does all the magic around RIP44d, the IPIP tunnel interface, enable ip forwarding in sysctl etc, etc. I usually create a file in \/usr\/local\/sbin called startampr with the following content<\/p>\n
##################################################################
\n## This script was developed by KB3VWG on a standard Ubuntu 12.04.1 LTS PC
\n## with IPv4 forwarding enabled in \/etc\/sysctl.conf by changing the
\n## net.ipv4.ip_forward variable to 1, eth0 configured to the Public facing
\n## LAN and eth1 to the 44LAN. It is designed to enable an AMPR Router using the
\n## rip44d_table44 file, the standard rip44d, using the -t switch to add routes
\n## to routing table ’44’ with no fruther configuration needed (firewall optional)
\n##################################################################
\n## This script was modified by LX1DUC to automate even more tasks.
\n##################################################################<\/p>\n########################################
\n### ENABLE IP FORWARDING ###
\nsysctl -w net.ipv4.ip_forward=1<\/p>\n########################################
\n### ENABLE IPIP TUNNEL INTERFACE tunl0 ###
\n### you must enable the tunnel before specifying routes using the tunnel
\nmodprobe ipip
\nip addr add 44.256.0.1\/32 dev tunl0
\n### gives tunnel its own TTL of 64 enabling traceroute over tunnel
\nip tunnel change ttl 64 mode ipip tunl0
\nip link set dev tunl0 up<\/p>\n########################################
\n### FIREWALL TO COMPLY WITH AMPR ROUTING RULES ###
\n### REGARDING TEST SUBNET ###
\niptables -A FORWARD -s 44.128.0.0\/16 -j REJECT
\niptables -A FORWARD -d 44.128.0.0\/16 -j REJECT<\/p>\n########################################
\n### LAN ROUTING RULES (required if used as the LAN’s gateway) ###
\n### Allows 44LAN to use main routing table to access LAN (optional)
\n### (NAT\/masquerade from 44.60.44.0\/24 to must be configured
\n### if LAN hosts do not use AMPR Router as their LAN Gateway)
\n#ip rule add from 44.60.44.0\/24 to table main priority 1<\/p>\n########################################
\n### AMPR ROUTING RULES ###
\n### Per PE1CHL: ‘This is “required” to get routing of the net-44 traffic correct ###
\n### and have a default route for the tunneled traffic different from the default ###
\n### route of the system. It may be possible to get it working without this, but ###
\n### policy based routing is so much easier.’ ###
\n### Packets to and from the 44 Network use Route Table 44
\nip rule add to 44.0.0.0\/8 table 44 priority 44
\nip rule add from 44.256.0.0\/24 table 44 priority 45<\/p>\n########################################
\n### TABLE 44 ROUTES ###
\n### Default Route [Internet Access] using AMPRGW for 44\/8 hosts (optional)
\n### do NOT change the IP 169.228.66.251, this is the central AMPR Gateway
\n### and all traffic leaving AMPRnet towards the internet MUST pass this router.
\nip route add default dev tunl0 via 169.228.66.251 onlink table 44
\n### Leave the 44.0.0.1 route below commented if the default route is used,
\n### in which case, RIP44 will create it automatically
\n### ip route add 44.0.0.1 dev tunl0 via 169.228.66.251 onlink table 44 window 840
\n### Adds 44LAN Network to Table 44
\nip route add 44.256.0.0\/24 dev eth1 table 44
\n########################################<\/p>\n### STARTS THE rip44d ROUTER DAMEON – removing the WAN IP address of the local gateway ###
\n### (rip44d announcements, 44LAN route, and removing local WAN IP with -a switch
\n### equals full AMPR routing table)
\n\/usr\/local\/sbin\/rip44d -a 192.0.2.1 -p pAsSwOrDgOeShErE -t 44 < \/dev\/null &<\/p><\/blockquote>\nMany thanks to KB3VWG and PE1CHL.<\/p>\n
The file must also be executable by root<\/p>\n
sudo chmod 744 \/usr\/local\/sbin\/startampr<\/p><\/blockquote>\n
IMPORTANT<\/strong><\/span>, please replace the invalid IP address network 44.256.0.0\/24, the invalid IP address 44.256.0.1 and the documentation IP 192.0.2.1 according to your local setup:<\/p>\n
\n
- 44.256.0.0\/24 must be replaced with your network and netmask (your netmask may differ from \/24!!!)<\/li>\n
- 44.256.0.1 should be replaced by the IP address assigned to the gateway on your AMPRnet LAN<\/li>\n
- 192.0.2.1 should be replaced by your public static IP address<\/li>\n<\/ul>\n
Next you can run execute<\/p>\n
sudo startampr &<\/p><\/blockquote>\n
TODO<\/strong><\/span>:<\/p>\n
\n
- setup iptables to limit access to the system<\/li>\n
- setup AMPRnet gatway behind NAT (hoepfully there will be another solution for this soon)<\/li>\n
- detect external public IP address automatically<\/li>\n<\/ul>\n
UPDATES<\/strong><\/span>:<\/p>\n
\n
- make startampr script executable<\/li>\n
- show how to launch startampr<\/li>\n
- explain the IP address 169.228.66.251<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
I had to setup many AMPRnet gateways on Linux machines and I always had a hard time remembering the different steps, so I try to provide a quick start over here. I have been using the RIP44d deamon for all … Continue reading