44Net Wiki - User contributions [en]

RIP44.lua

2019-04-08T10:51:02Z

M6XCV: fix download instructions

== Status: Experimental. ==
M6XCV has written a RIP44 daemon in Lua. The expected primary use case is OpenWRT/LEDE based devices, however the script was developed on Debian and should work on any Linux platform with the appropriate libraries. The script is currently considered experimental, having received only limited testing on a couple of devices.

== Requirements ==
The script should only require Lua and the LuaSocket module to work. As well as the IPIP kernel module, of course. If you do not have the "ip" command installed then you will also need this.

== OpenWRT Install ==
I have provided an OpenWRT package which should install the required dependencies.

SSH in to your device and run the following commands:

*opkg update
*opkg install wget libustream-openssl ca-bundle ca-certificates (to support HTTPS for the download)
*wget https://raw.githubusercontent.com/NotMikeDEV/RIP44/master/rip44_2019.04.07-1_all.ipk
*opkg install rip44_2019.04.07-1_all.ipk

You then need to edit '''/etc/rip44.conf''' to specify your AMPRNet allocation. Once this is done, reboot to load the required modules and start the daemon.

If the configuration setting GATEWAY is false then it will use your normal default route for Internet-based destinations, set it to the main gateways IP address to use that instead. You might also want to change SAVE_FILE to a different location.

Once you have received a broadcast, check your routing table. By default it will use routing table 44, therefore you need to use the command <code>ip route list table 44</code> to check. Broadcasts are sent every 5 minutes, so you will have to wait for the next broadcast to confirm everything is working.

You should not need to wait for a RIP broadcast before the routes appear after the initial run.

If you have just added your gateway to the portal then you may need to wait an hour or so before you start receiving broadcasts.

== Other Linux systems ==

Get the script by cloning https://github.com/NotMikeDEV/RIP44 you will need to place rip44.conf in /etc/rip44.conf and rip44.lua in an appropriate directory. You will also need to set rip44.lua to run on startup. Further instructions are distro-specific, but anyone familiar with Linux should be able to figure it out. Startup scripts are not currently provided for distributions other than OpenWRT as it is felt that another routing daemon is probably more appropriate on platforms with full toolchains. This script is primarily designed for OpenWRT devices where binary releases are awkward to build.

== Testing ==
Perform a TraceRoute from one of your AMPRNet IP addresses to 44.88.0.1 and ensure it does *not* go through your ISP. By default the script adds the specified address to your tunnel interface, so if your network allocation is 44.1.2.0/29 you could test from the router with the command <code>traceroute 44.88.0.1 -s 44.1.2.0</code>. Note that this does not stop you from assigning your allocation to an Ethernet interface.

If traffic appears to be blocked, you may need to add the interface (tunl0) in the OpenWRT web interface and add it to a firewall zone. It depends on your firewall configuration for if this will be needed or not, you may also need to set your WAN interface to ALLOW inbound traffic to receive the IPIP encapsulated packets. The requirements for OpenWRT network configuration should be the same as with other daemons, so if you have previously set up another routing daemon it should work the same with this one.

Check out the [[Services]] page for other hosts you can run tests to.

This script will set up your routing with a separate routing table for your 44Net prefix. This means other traffic will continue to use your normal Internet connection. Only traffic from your 44/8 prefix will be routed through the tunnels. If you wish for all traffic to come from a 44Net IP you will need to adjust the routing and NAT accordingly.

== Updates ==
This script is experimental, please let m6xcv@m6xcv.uk know if you are using this script and if it worked or not. If you have any problems then contact me and I will look in to it.

RIP44.lua

2019-04-07T23:26:46Z

M6XCV:

== Status: Experimental. ==
M6XCV has written a RIP44 daemon in Lua. The expected primary use case is OpenWRT/LEDE based devices, however the script was developed on Debian and should work on any Linux platform with the appropriate libraries. The script is currently considered experimental, having received only limited testing on a couple of devices.

== Requirements ==
The script should only require Lua and the LuaSocket module to work. As well as the IPIP kernel module, of course. If you do not have the "ip" command installed then you will also need this.

== OpenWRT Install ==
I have provided an OpenWRT package which should install the required dependencies.

SSH in to your device and run the following commands:

*wget https://github.com/NotMikeDEV/RIP44/blob/master/rip44_2019.04.07-1_all.ipk
*opkg update
*opkg install rip44_2019.04.07-1_all.ipk

You then need to edit '''/etc/rip44.conf''' to specify your AMPRNet allocation. Once this is done, reboot to load the required modules and start the daemon.

If the configuration setting GATEWAY is false then it will use your normal default route for Internet-based destinations, set it to the main gateways IP address to use that instead. You might also want to change SAVE_FILE to a different location.

Once you have received a broadcast, check your routing table. By default it will use routing table 44, therefore you need to use the command <code>ip route list table 44</code> to check. Broadcasts are sent every 5 minutes, so you will have to wait for the next broadcast to confirm everything is working.

You should not need to wait for a RIP broadcast before the routes appear after the initial run.

If you have just added your gateway to the portal then you may need to wait an hour or so before you start receiving broadcasts.

== Other Linux systems ==

Get the script by cloning https://github.com/NotMikeDEV/RIP44 you will need to place rip44.conf in /etc/rip44.conf and rip44.lua in an appropriate directory. You will also need to set rip44.lua to run on startup. Further instructions are distro-specific, but anyone familiar with Linux should be able to figure it out. Startup scripts are not currently provided for distributions other than OpenWRT as it is felt that another routing daemon is probably more appropriate on platforms with full toolchains. This script is primarily designed for OpenWRT devices where binary releases are awkward to build.

== Testing ==
Perform a TraceRoute from one of your AMPRNet IP addresses to 44.88.0.1 and ensure it does *not* go through your ISP. By default the script adds the specified address to your tunnel interface, so if your network allocation is 44.1.2.0/29 you could test from the router with the command <code>traceroute 44.88.0.1 -s 44.1.2.0</code>. Note that this does not stop you from assigning your allocation to an Ethernet interface.

If traffic appears to be blocked, you may need to add the interface (tunl0) in the OpenWRT web interface and add it to a firewall zone. It depends on your firewall configuration for if this will be needed or not, you may also need to set your WAN interface to ALLOW inbound traffic to receive the IPIP encapsulated packets. The requirements for OpenWRT network configuration should be the same as with other daemons, so if you have previously set up another routing daemon it should work the same with this one.

Check out the [[Services]] page for other hosts you can run tests to.

This script will set up your routing with a separate routing table for your 44Net prefix. This means other traffic will continue to use your normal Internet connection. Only traffic from your 44/8 prefix will be routed through the tunnels. If you wish for all traffic to come from a 44Net IP you will need to adjust the routing and NAT accordingly.

== Updates ==
This script is experimental, please let m6xcv@m6xcv.uk know if you are using this script and if it worked or not. If you have any problems then contact me and I will look in to it.

RIP44.lua

2019-04-07T23:01:56Z

M6XCV:

== Status: Experimental. ==
M6XCV has written a RIP44 daemon in Lua. The expected primary use case is OpenWRT/LEDE based devices, however the script was developed on Debian and should work on any Linux platform with the appropriate libraries. The script is currently considered experimental, having received only limited testing on a couple of devices.

== Requirements ==
The script should only require Lua and the LuaSocket module to work. As well as the IPIP kernel module, of course. If you do not have the "ip" command installed then you will also need this.

== OpenWRT Install ==
I have provided an OpenWRT package which should install the required dependencies.

SSH in to your device and run the following commands:

*wget https://github.com/NotMikeDEV/RIP44/blob/master/rip44_2019.04.07-1_all.ipk
*opkg update
*opkg install rip44_2019.04.07-1_all.ipk

You then need to edit '''/etc/rip44.conf''' to specify your AMPRNet allocation. Once this is done, reboot to load the required modules and start the daemon.

If the configuration setting GATEWAY is false then it will use your normal default route for Internet-based destinations, set it to the main gateways IP address to use that instead. You might also want to change SAVE_FILE to a different location.

Once you have received a broadcast, check your routing table. By default it will use routing table 44, therefore you need to use the command <code>ip route list table 44</code> to check. Broadcasts are sent every 5 minutes, so you will have to wait for the next broadcast to confirm everything is working.

You should not need to wait for a RIP broadcast before the routes appear after the initial run.

If you have just added your gateway to the portal then you may need to wait an hour or so before you start receiving broadcasts.

== Other Linux systems ==

Get the script by cloning https://github.com/NotMikeDEV/RIP44 you will need to place rip44.conf in /etc/rip44.conf and rip44.lua in an appropriate directory. You will also need to set rip44.lua to run on startup. Further instructions are distro-specific, but anyone familiar with Linux should be able to figure it out. Startup scripts are not currently provided for distributions other than OpenWRT as it is felt that another routing daemon is probably more appropriate on platforms with full toolchains. This script is primarily designed for OpenWRT devices where binary releases are awkward to build.

== Testing ==
Perform a TraceRoute from one of your AMPRNet IP addresses to 44.88.0.1 and ensure it does *not* go through your ISP. By default the script adds the specified address to your tunnel interface, so if your network allocation is 44.1.2.0/29 you could test from the router with the command <code>traceroute 44.88.0.1 -s 44.1.2.0</code>. Note that this does not stop you from assigning your allocation to an Ethernet interface.

If traffic appears to be blocked, you may need to add the interface (tunl0) in the OpenWRT web interface and add it to a firewall zone. It depends on your firewall configuration for if this will be needed or not, you may also need to wet your WAN interface to ALLOW inbound traffic to receive the IPIP encapsulated packets. The requirements for OpenWRT network configuration should be the same as with other daemons, so if you have previously set up another routing daemon it should work the same with this one.

Check out the [[Services]] page for other hosts you can run tests to.

This script will set up your routing with a separate routing table for your 44Net prefix. This means other traffic will continue to use your normal Internet connection. Only traffic from your 44/8 prefix will be routed through the tunnels. If you wish for all traffic to come from a 44Net IP you will need to adjust the routing and NAT accordingly.

== Updates ==
This script is experimental, please let m6xcv@m6xcv.uk know if you are using this script and if it worked or not. If you have any problems then contact me and I will look in to it.

Setting up a gateway on OpenWRT

2018-06-09T17:35:20Z

M6XCV: add RIP44.lua link

[[ampr-ripd]] has been compiled for the AppliedMicro APM82181 and Atheros 71xx router CPUs

'''NOTE: To operate a [[Gateway]] on [[AMPRNet]], you must have a method of obtaining up-to-date route information. On AMPRNet, a variant of [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] protocol, named [[RIP]]44 is used. [https://en.wikipedia.org/wiki/Routing_Information_Protocol RIP version 2] is not the same as [[RIP]]44.''' [[rip44d]] is written in the Perl programming language by Heikki Hannikainen, OH7LZB. [[ampr-ripd]] is written in C by YO2LOJ. The routing table is relatively small, so the performance or memory consumption of this daemon isn't very critical. [[ampr-ripd]] is used in this instance, so no other prerequisite software is required to run the [[RIP]]44 daemon.

* '''You must have access to a binary [https://en.wikipedia.org/wiki/Executable executable] of [[ampr-ripd]] that is compatible with the [https://en.wikipedia.org/wiki/Central_processing_unit CPU] in your OpenWRT device (e.g. i386, i586, x86_64, MIPS, PPC, etc.). If you do not, you must [https://en.wikipedia.org/wiki/Compiler compile] ampr-ripd yourself, or install the packages necessary to run [[rip44d]].'''

There is also an experimental LUA daemon at [[RIP44.lua]] which should run with standard packages.

== '''See''' ==

* [https://openwrt.org/docs/guide-developer/crosscompile Cross Compile - OpenWRT]
* [https://openwrt.org/docs/start OpenWRT Manual]

== Summary ==

'''NOTE: These instructions assume first that you have been assigned AMPRNet IP address allocations that are properly assigned and configured to your account in the [[Portal]]. Next, that you intend to configure your OpenWRT-based (version 14.07 or greater) AMPRNet [[Gateway]] to be a [https://en.wikipedia.org/wiki/Stateful_firewall stateful firewall] for your AMPRNet allocations (i.e. enabling connection tracking). If you prefer to forward all traffic to your allocated AMPRNet IP addresses, you may follow these instructions; but configure your Firewall Zones to forward all traffic to/from AMPRLAN to AMPRWAN. These instructions configure your AMPRNet Tunnel and AMPRNet Local Interfaces in their own [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] sernario; and places all local AMPRNet allocations in the main routing instance (you must provide routing rules for your local AMPR subnets to reach local subnets, if you desire). Since the OpenWRT Kernel is aware that your AMPRNet allocations exist locally (and are populated on the MAIN ROUTING TABLE), you must provide routing rules for AMPRLAN to reach these local subnets, or omit those rules (not permitting your AMPRLAN to route to your local subnets). Lastly, it assumes that the user can navigate the default OpenWRT LuCI web-based graphical user interface locally (and that they are using a device capable of having the package installed), are familiar with the [https://en.wikipedia.org/wiki/Chmod chmod] command, and/or familiar with entering OpenWRT UCI (Unified Configuration Interface) commands by serial console or SSH.'''

Install:

* kmod-ipip
* ip-full
* libstdcpp
* [[ampr-ripd]] to '''/etc/config/''' (always run [[RIP]]44 software in console mode FIRST after installation to verify execution and obtain the password, the execution of the file is commented-out below)
* diffutils (optional for dynamic IP filtering)
* (optional) dynamic firewall script to /etc/config/load_ipipfilter.sh (see the iptables section of the [[Firewalls]] wiki)
* the following to '''System > Startup > Local Startup:'''

ip tunnel add tunl0
ip tunnel change tunl0 mode ipip ttl 64 tos inherit pmtudisc
ip link set tunl0 mtu 1480 up
'''# This directory is not persistent on OpenWRT, it must be made on boot for dynamic filtering
mkdir /var/lib/ampr-ripd
# A blank bootstrap file must be created at /etc/config/encap.txt for this to work
# Running '''touch /etc/config/encap.txt''' once can create it
# after which, you may run ampr-ripd to populate it
ln -s /etc/config/encap.txt /tmp/lib/ampr-ripd/encap.txt
# Dynamic filter, script executed by -x argument
# Dynamic filter, -s argument creates encap.txt
'''# ./etc/config/ampr-ripd -p <PASSWORD> -s -t 44 -a <44.xxx.xxx.xxx/xx> -x ./etc/config/load_ipipfilter.sh &'''
## Allows traceroute to respond using 44net IP of tunl0 or br-amprlan ##
echo 1 > /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr

'''UPDATE 2018 (routes and rules have been added to the UCI):'''

# add IP Route to /etc/config/network

config route
option interface 'amprwan'
option target '0.0.0.0'
option netmask '0.0.0.0'
option gateway ''''<AMPRGW>''''
option onlink '1'
option table '44'

# add IP Rules to /etc/config/network

#OPTIONAL AMPR TO LAN RULES (NUMBER 22-2X ACCORDINGLY)
config rule
option src '44.xxx.xxx.0/24'
option dest '192.168.xxx.0/24'
option priority '22'
option lookup 'main'

#ADD A MAIN RULE FOR EVERY LOCAL AMPR SUBNET, RENUMBER 44-4X ACCORDINGLY)
config rule
option dest '44.xxx.xxx.0/24'
option priority '44'
option lookup 'main'

### This ensures all traffic received on tunl0 uses table 44
config rule
option in 'amprwan'
option dest '0.0.0.0/0'
option priority '45'
option lookup '44'

###Add this after you create the AMPRLAN bridge, this ensures all traffic from AMPRLAN uses table 44
config rule
option in 'amprnet'
option dest '0.0.0.0/0'
option priority '46'
option lookup '44'

### You must add an IP rule for all 44net IPs residing on the device
config rule
option src '44.xxx.xxx.0/24
option priority '47'
option lookup '44'

* '''reboot'''
* create an unmanaged Interface instance for tunl0 ('''AMPRWAN''') '''(set to not bring up on boot)''', adding it to its own firewall zone '''amprwan''' using Input: Drop (or Reject), Output: Drop (or Reject) and Forward: Drop (or Reject). '''(OpenWRT 14.07 or lower - Be sure to enable connection tracking if you will not masquerade)'''
* an interface instance for a new VLAN and bridge (the example above uses AMPRNET), add it to its own firewall zone using Input: Accept (if you wish for you AMPRLAN devices to reach the router), Output: Accept and Forward: Drop (or Reject). '''Assign an IP from your allocation to this interface, you will configure this IP on your devices as the Default Route/Gateway address.'''
* '''reboot'''
* Permit forwarding from AMPRLAN to AMPRWAN and WAN (you must masquerade this traffic when using WAN)
* Permit forwarding from LAN to AMPRLAN (as desired, NOTE: you must make an IP Rule for the AMPRLAN to use the LAN's route on the Main Routing Table)
* Create Traffic Input rule to allow IPv4 IPENCAP (IP protocol type 4) from Any IP on WAN to any IP on Router (or specify WAN IP if statically assigned)
* Create Traffic Input rule to allow IPv4 udp/520 from 44.0.0.1 in AMPRWAN to 224.0.0.9 at port udp/520 IP on Router
* Create Traffic Forward rules for any inbound services (as desired)
* the VLAN to any switch/trunk ports (as desired)
* make ampr-ripd and load_ipipfilter.sh executable using '''chmod +x'''
* test ampr-ripd in console using the '''-d''' argument
* add password to the '''Local Startup''' entry and uncomment ampr-ripd line
* '''reboot'''

RIP44.lua

2017-06-07T18:04:01Z

M6XCV: /* Testing */

RIP44.lua

2017-05-10T23:22:21Z

M6XCV: /* Install */

RIP44.lua

2017-05-10T23:21:30Z

M6XCV: Create initial page