44Net Wiki - User contributions [en]

ARDC

2019-07-25T11:55:35Z

WB6CYT:

The Amateur Radio Digital Communications corporation (ARDC) is a non-profit California corporation that owns the AMPRNet (44.0.0.0/9 and 44.128.0.0/10). It was formed to encourage and foster the development of Amateur Radio digital networking. You may contact ARDC by sending email to ardc@ampr.org.

Note that ARDC is not an Internet Service Provider. It does not provide any networking access or facilities. It manages and allocates subnets of network 44 (AMPRNet), to interested Amateur Radio operators. Persons who obtain an allocation of address space on AMPRNet must make their own arrangements for connectivity and Internet service.

ARDC also has a philanthropic arm which grants funding to organizations in support of related project and scholarships.

ARDC

2019-07-25T11:52:57Z

WB6CYT:

ARDC, the Amateur Radio Digital Communications corporation, is a non-profit California corporation that owns network 44 (44.0.0.0/9 and 44.128.0.0/10), known as the AMPRNet. It was formed to encourage and foster the development of the Amateur Radio packet and other amateur radio digital networking. You may contact ARDC by sending email to ardc@ampr.org.

Note that ARDC is not an Internet Service Provider. It does not provide any networking access or facilities. It manages and allocates subnets of network 44 (AMPRNet), to interested Amateur Radio operators. Persons who obtain an allocation of address space on AMPRNet must make their own arrangements for connectivity and Internet service. It also has a philanthropic arm which grants funding to organizations in support of related project and scholarships.

Startampr

2019-07-25T11:46:19Z

WB6CYT:

'''startampr''' is a custom suite of [https://en.wikipedia.org/wiki/Bash_%28Unix_shell%29 Bourne Again Shell] scripts developed by KB3VWG and others in the [[44Net mailing list]] Community, that turns a Debian/Ubuntu-based Linux machine into an AMPR [[Gateway]] on boot; and starts an [https://en.wikipedia.org/wiki/IP_in_IP IPENCAP] (or [https://en.wikipedia.org/wiki/List_of_IP_protocol_numbers IP Protocol] number four) tunnel. The primary advantage to using this suite is that it executes and enables AMPR RIP44 daemons, munge scripts, interfaces and routing commands in proper boot order; and references them using the command syntax, default command arguments and practices that have become the de facto standard on [[AMPRNet]]. It is also minimally invasive, in that the machine otherwise remains an "untouched" default installation; and can be returned to an OEM Ubuntu installation by simply removing all associated files and uninstalling all packages added when configuring the machine to run '''startampr''' (please assist me in developing an uninstall script, if interested). Also, if you install a server GUI (e.g. [http://www.webmin.com Webmin]), you can disable the routing features of the machine simply by checking a box, and hitting APPLY (on next reboot, it is disabled). '''The current versions are 1.0 (no longer developed), and 2.0, released to the [[44Net mailing list]] Community on May 26, 2017 at 14:14 UTC.

== Detailed Summary ==

In addition to the first and main script, '''startampr''', other tools included with the official release are: init scripts to execute the file, save the routing table (if using a method that does not automatically save it); and an executable script generator (made using [http://linux.die.net/man/1/sed the sed command]) that can restore the AMPR routing table (i.e. in the case the administrator flushes the table). The script uses the [http://www.linuxfoundation.org/collaborate/workgroups/networking/tunneling ipip Linux Kernel module] and implements [http://linux.die.net/man/8/ip Linux ip] routing table's [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] to properly move traffic across the routing plane. It is suggested that [https://en.wikipedia.org/wiki/Iptables iptables] be used to firewall traffic after verification of a proper installation.

The official release uses [[rip44d]] as its [[RIP]]44 protocol daemon; but [[ampr-ripd]] or [[Encap.txt]] with a [[munge script]] may be used (instructions by KB9MWR use ampr-ripd). '''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. The developer choose rip44d simply because it was the only daemon available when version 1.0 was developed. The use of any method to add route information to table 44 will work. It should be noted that: '''startampr''' was developed around '''rip44d'''; and improves on features not included (e.g. reload of routing table upon reboot). The scripts to backup/restore are not needed when using [[ampr-ripd]] (but can be developed to provide geographically-local tertiary sources of the AMPR routing table).

'''NOTE: if you do not wish to compile software, you must use [[rip44d]] or [[Encap.txt]] with a [[munge script]].'''

== 2.0 Security Update ==

'''startampr 2.0's code includes a security fix that corrects a routing issue that allows unencapsulated traffic from the tunnel to leak onto the LAN or Public Internet interface in version 1.0 - this only occurs when a AMPRNnet-facing user attempts to connect using invalid source IPs or invalid AMPRNet IP address'''. In original development of version 1.0, it was considered that this behavior could be valid to reach subnets ran by operators using the option at: [[Announcing your allocation directly]]; '''but do not make their tunnel available on a non-44.0.0.0/8 address''' (it was announced on the [[44Net mailing list]] on 04AUG2015, that AMPRGW now routes traffic to/from BGPed and IPENCAPed AMPR subnets, making this programmatic workaround unnecessary).

It is a generally accepted practice on the Internet that network operators source filter their traffic, making BGPed subnets an exception for AMPRNet Gateways (see [https://tools.ietf.org/html/rfc3013 RFC3013, section 4.3 and 4.4]). It is also accepted AMPRNet practice that these operators consider running a tunneled Gateway on any non-AMPRNet IP available for accessibility to/from those running IPENCAP Gateways. It may be useful to also have redundant VLANs on two or more interfaces possessing the same Public IP at two or more borders; and run a script between the AMPR Gateways - using [https://en.wikipedia.org/wiki/Dynamic_DNS Dynamic DNS] to synchronize them, verify if connectivity goes down on either device's tunl0 interface and update the [[Portal]] accordingly.

I'm happy and willing to work with any BGP subnet operator who wishes to develop a script to establish an AMPR Gateway for your multi-homed AMPRNet BGPed subnet.

= Requirements, Installation Overview and Features =

# You'll need a Linux computer, which has been added in the Gateways file using the [[Portal]], so that it is known as an AMPRnet Gateway; and will receive RIP44 updates from the main [[Gateway]]. It will take some time before Amprgw will learn about new gateways.
# The instructions below are currently only for Debian/Ubuntu, but there's nothing Debian-specific - it should work fine on other distributions (if the correct packages used (e.g. wget/curl, The Bourne Again Shell/BASH, sed, ip, chmod, PERL, etc.) Interface names, file and folder locations, file permissions, etc. are edited.

You must first properly install:
* the operating system and network interfaces
* then properly install '''startampr''' at '''/usr/local/sbin''' to enable the tunnel. '''The tunnel interface must be operational and in 'UP' status before proceeding.'''
* the [[RIP]]44 daemon ([[rip44d]] uses the location '''/usrlocal/sbin/''') which receives periodic routing table updates from the [[AMPRNet]] routing service, and inserts them in the Linux routing table of your choice (most users use table 44; and the scripts use this value as well). '''You must verify that you are receiving route information before proceeding.'''
* boot script for '''startampr''', to '''/etc/init/'''
* (Optional) a script to backup the routing table and create a corresponding restore script, at '''/etc/cron.hourly/'''
* (Optional) a script to restore the AMPRNet routing table on boot, at '''/etc/if-ip.d/'''

= Installation of startampr =

Install the the script to '''/usr/local/sbin''' and '''sudo chmod ug+x /usr/local/sbin/startampr'''

After obtaining the correct password from the route announcement and entering it into the properly configured script, install the boot and interface-up scripts (sample init scripts provided).

The additional script '''/etc/cron.hourly/backup_ampr''' creates an hourly backup of the AMPR routing table, located in two files at '''/usr/local/sbin''':

* '''/usr/local/sbin/table44_bak ''' - It is a text file that contains a copy of output from the command: 'ip route get table 44'
* '''/usr/local/sbin/restore44sh''' - It contains a copy of '''table44_bak''' with the command "ip route add table 44 " appended to each line. '''backup_ampr''' gives this file executable permissions to user:root and group:root. Execute this file using the command: '''sudo ./usr/local/sbin/restore44sh''' to restore your routing table if the need ever occurs.

You can verify the backup is running by issuing the command: '''ls -l /usr/local/sbin/restore44sh''' and '''ls -l /usr/local/sbin/table44_bak'''
If the machine has been up, the files should be no more than an hour old.

That should be all. Really. The downside of this configuration is that it will take up to 5 minutes for the gateway to receive a routing update and become operational after a reboot. The additional scripts provided store the current routing table in a local file hourly and load it from there when starting up. Thereafter, after every hour of uptime your routing table is backed up at :17 on the hour. This backup can be used if you ever need to execute the ip command to flush table 44.

= Installation of dependencies on Debian/Ubuntu =

'''If you use rip44d''', install perl, and IO::Socket::Multicast, a Perl module used for receiving the RIP multicast packets

sudo apt-get install perl libio-socket-multicast-perl libio-interface-perl

recommended:

sudo apt-get install traceroute openssh-server ipset

= Installation of dependencies on other distributions =

Other distributions should have an easy way to install the required packages too (using yum or a similar program). Please fill in details here, if you know them.

= Script =

#!/bin/bash
#############################################################
###STARTAMPR v2.0 May 26, 2017###
###
### TO DO - Have the AMPRNet Community test and verify
###
### CHANGELOG
###
### v2.0 RC4
### - Dialogue about how to add routes and rules for any created test subnet(s).
###
### v2.0 RC3
### - Exclusively seperates route and tables, as well as priotities by: class and type
### - This makes unnecessary the exclusion of local subnets in ampr-ripd using the '-a' switch,
### by adding local 44 network(s) to a higher priority routing table
### - This should enable you can to become a tunnel GW for BGPed 44/8 subnets
### - Provides table 7777 as a BLACKHOLE/NULL Route
### - Adds script to load last hourly backup of table 44 on boot
### - With script backup_ampr, creates a backup of the routing table a file named table44_bak
### and an executable restore44sh hourly to use on the running machine to
### restore table 44 if the table needs to be flushed during uptime
###
### v2.0
### - Streamlined commands and routes
### - Placed syntax for Debian/Ubuntu and OpenWRT/LEDE devices
#############################################################
## This script was developed by KB3VWG on a standard
## Ubuntu 16.04.2 LTS PC eth0 configured to the Public facing
## LAN and eth1 to the 44LAN. It is designed to enable an
## AMPR Router using the ampr-ripd v2.0, the standard ampr-ripd,
## using the -t switch to add routes to routing table '44'
## with no further configuration needed (firewall optional)
##############################################################
##################################################################
## This script was modified by LX1DUC to automate even more tasks.
##################################################################
##################################################################
## Thanks to PE1CHL for discovering the need for policy-based routing
## Thanks to KI4SZJ for testing v2.0
##################################################################

### ENABLE IP FORWARDING ###
sysctl -w net.ipv4.ip_forward=1
## Allows traceroute to respond using 44net IP of tunl0 or br-amprlan ##
echo 1 > /proc/sys/net/ipv4/icmp_errors_use_inbound_ifaddr

################### AMPRNet IPENCAP UBUNTU SYNTAX #######################
# modprobe ipip
# ip tunnel add tunl0 mode ipip
###NUMBER tunl0 with a /32 from your allocation
###(you may reuse this IP on an Ethernet interface
# ip addr add <IP from your 44>/32 dev tunl0
# ip link set tunl0 mtu 1480 up
# ip tunnel change tunl0 ttl 64 tos inherit pmtudisc

################### AMPRNet IPENCAP OpenWRT/LEDE SYNTAX #######################
# ip tunnel add tunl0
# ip tunnel change tunl0 mode ipip ttl 64 tos inherit pmtudisc
###(you may reuse this IP on an Ethernet interface
# ip addr add <IP from your 44>/32 dev tunl0
# ip link set tunl0 mtu 1480 up

################### OPTIONAL - DEFAULT ROUTE FOR INTERNET ACCESS #######################
ip route add default dev tunl0 via <AMPRGW_IP> onlink proto 44 table 44

################### POLICY-BADED ROUTING #######################
###OPTIONAL LOCAL RULES
ip rule add from <CIDR_44_allocation> to <LAN e.g. 192.168.1.0/24> table main priority 22

#REQUIRED RULES
ip rule add to <CIDR_44_allocation> table main priority 44
ip rule add dev tunl0 table 44 priority 45
ip rule add dev <interface_for_44LAN> table 44 priority 46
ip rule add from <CIDR_44_allocation> table 44 priority 47

###SOME OF THIS MAY BE NEEDED TO RUN ampr-ripd from another folder than the compile option
###make sure you create the correct save and working folders, etc if you cant recompile ampr-ripd
# This directory is not persistent on OpenWRT/LEDE, it must be made on boot for dynamic filtering
# mkdir /var/lib/ampr-ripd
# Create a blank bootstrap file at /etc/config/encap.txt for this to work
# ln -s /etc/config/encap.txt /tmp/lib/ampr-ripd/encap.txt
# cd /usr/local/sbin

################### RUN AMPR-RIPD
################### WITH DYNAMIC FIREWALL SCRIPT USING -x
################### see http://wiki.ampr.org/wiki/Firewalls for dynamic script
./ampr-ripd-2.0.x64_Ubuntu16 -i <tunl_interface> -t 44 -a <CIDR_44_allocation> -s -x '/etc/config/load_ipipfilter.sh' -L <CALLSIGN>@<GRID_SQUARE> &

= Notes =

* '''startampr documentation uses tunl0 as the tunnel interface (it is the default on RIP44 daemons) and table 44 for those routes. Use the -i <if> and -t <ip table> option to change to another. The command arguments differ between [[rip44d]] and [[ampr-ripd]]. startampr uses rip44d. See the documentation for the RIP44 programs if decide to use custom interfaces, tables or switch to a routing daemon other than [[rip44d]].'''
* '''The script places the routing daemon at /usr/local/sbin/rip44d_<version number> (this assists in preventing inadvertent running of RIP44 Protocol before you have configured startampr.
* '''The routing rules do not account for rogue traffic containing both an invalid source and destination IP (which the security of the [[Portal]] generally prevents). Use iptables to DROP forwarding of all traffic entering tunl0 not matching a source or destination of in your allocated subnet(s). This can be done by adding adding rules to drop forwarding, by default, packets not possessing correct source and destination IPs in the range of 44.0.0.0/8, etc.'''
* The -a <IP in [[Portal]]> is used to remove your routes from the table (which is incorrect, as they are local). '''startampr''' places your local routes in a higher routing table, eliminating the need to use the -a argument. This is a good feature for those who are assigned a dynamic IP address from their Internet Service Provider.
* The tunnel interface must be up and configured before '''rip44d''' starts up. '''startampr''' places this command in the proper location.
* rip44d automatically adds an AMPR route to the Main AMPRNet Gateway on table 44
* The '''startampr''' backup script '''/etc/cron.hourly/backup_ampr''' is added to a folder that is configured in Ubuntu, by default, to run scripts at :17 after the hour. The Main AMPR Gateway sends an update every five minutes. For advanced instructions on changing this time interval, see [https://help.ubuntu.com/community/CronHowto the Ubuntu Community cron HowTo].
* A strict assortment of: file permissions, naming conventions and leading characters (e.g. '''"#!/bin/bash"''') are required in '''/etc/init/''', '''/etc/if-up.d/''' (used in a script to reload table 44 on boot) and '''/etc/cron.hourly/'''. Note that: '''startampr''' has properly named those files. If you wish to edit them, please follow the documentation and README for more details.
* '''Please note that: any machine acting as an AMPRNet Gateway must explicitly create high-priority routing rules for all traffic addressed to or from eth0. The network assigned to eth0 must be configured to ONLY use table main.''' No other valid configuration has been found to properly work (discovered by PE1CHL and tested by KB3VWG and others in the [[44Net mailing list]] Community). '''This is due to the unique fact that, on AMPRNet routers, 44.0.0.0/8 exists on both the Public (eth0) and AMPRNet-facing (tunl0) sides of the device. There is no way to properly differentiate the route or destination interface of the traffic received from 44.0.0.0/8 over tunl0 (with your 44Router's 44 IP address), versus that from eth0 (on the Gateway's Public-facing IP). Meaning, there is no way to route traffic for all cases, except by SOURCE OR DESTINATION IP ADDRESS. Therefore, ALL traffic to and from the network facing eth0, must use eth0.''' In order to access your AMPRNet from a local network, you must create another routable LAN (and add TO rules, e.g. ip route add to 172.55.0.0/24 table main priority - and masquerade accordingly if configured to reach all of AMPRNet), or simply connect directly to an AMPR-facing interface. The rule to only use the main table for the eth0 network allows the AMPRNet Gateway to reach 44 hosts on the Public Internet, leaving the operator to provide all routing rules for AMPR-facing interfaces, which is the intent of '''startampr'''.

= Support, bug reports and improvements =

If you have questions to ask about the usage of this script, please contact the [[44Net mailing list]].

If you have improvements to the script and wish to submit a patch, please contact KB3VWG on the [[44Net mailing list]], or via contact details in the [[Portal]]. Thank you!

The daemon was written by Lynwood, KB3VWG, and with major contributions from PE1CHL (for implementation of policy-based IP routing), Heikki Hannikainen, OH7LZB (to version 1.0's integration with '''[[rip44d]]'''), and Marc, LX1DUC (to automate enabling of IP forwarding).

=See also=

* [[Ubuntu Linux Gateway Example]]
* [[Setting up a gateway on Linux]]
* [[ampr-ripd]]
* [[Encap.txt]]
* [[munge script]]
* [[rip44d]]

= Links =

* [http://www.qsl.net/kb9mwr/wapr/tcpip/ampr-ripd.html Alternative installation instructions by KB9MWR]
* [http://marc.storck.lu/blog/2013/08/howto-setup-an-amprnet-gateway-on-linux/ Alternative installation instructions by Marc, LX1DUC]
* [(link to KB3VWG's site here) Detailed Readme and Installation instructions by KB3VWG]

Gateway

2019-07-25T11:42:53Z

WB6CYT:

A lot of the AMPRNet address space is interconnected via [[gateway|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel|tunnels]] that carry the AMPRNet address space allocated to a particular region or end user. There exists a database of all the gateways public IP addresses and the subnets they service on the [[portal]]. This database is used to dynamically generate gateway information via modified [[RIP]] advertisements. This database also generates a file called [[encap.txt]] which is basically a routing table that specifies which subnets can be reached via which gateway.

Learn how to [[Setting up a gateway on Linux|setup a Linux gateway]]

Learn how to [[Setting up a gateway on OpenWRT|setup an OpenWRT gateway]]

Learn how to [[Setting up a gateway on Cisco Routers|setup a Cisco Router gateway]]

Learn how to [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]]

In order to keep this database up to date, everyone that operates a gateway must register on the [[portal]] and have their gateway assigned to their account.

ARDC

2019-07-25T11:41:11Z

WB6CYT:

ARDC, the Amateur Radio Digital Communications corporation, is a non-profit California corporation that owns network 44 (44.0.0.0/9 and 44.128.0.0/10), known as the AMPRNet. It was formed to encourage and foster the development of the Amateur Radio packet and other amateur radio digital networking. You may contact ARDC by sending email to ardc@ampr.org.

Note that ARDC is not an Internet Service Provider. It does not provide any networking access or facilities. It solely manages and allocates Internet address space, subnets of network 44 (AMPRNet), to interested Amateur Radio operators. Persons who obtain an allocation of address space on AMPRNet must make their own arrangements for connectivity and Internet service.

Quickstart

2019-07-25T11:39:46Z

WB6CYT:

So you're a licensed amateur radio operator, you're interested in IP networking, and you want to combine the two. [[AMPRNet]] is for you. This Quickstart guide can help get you set up quickly.

To get online with [[AMPRNet]], you will probably want to start with a tunnel connection to the rest of the network. You will need the following:

# A router. This can be a specialized routing device, or a general purpose computer. It probably won't need a lot of compute power, so you can recycle an old PC or something similar.
# An Internet connection that gives you a stable IP address for the rest of the network to talk to you: [[AMPRnet]] tunnels pass AMPRNet data between parts of the AMPR network by encapsulating them in non-44net Internet traffic. Static IP addresses are best for this, but IP addresses dynamically assigned to you by your ISP may work if they change infrequently.

Once you have a machine to act as a router and a suitable network connection, do the following:

# [https://portal.ampr.org/register.php Register] on the [[portal]].
# Request a network allocation from your regional coordinator.
## From the portal's [https://portal.ampr.org/networks.php networks] page, navigate to your country and region's network subpage.
## From the regional network page, request an allocation. Note, select only ONE of the connection options (Radio, Tunnel, or Direct). To start, you probably want to select 'Tunnel'. For more information on requesting an allocation, see the wiki page on [[Requesting a block]].
# Once your allocation has been granted, [https://portal.ampr.org/gateways_manage.php register your gateway through the portal].
# Once your gateway has been registered, contact your regional coordinator to register DNS mappings for the hosts on your network. Note that the main tunnel router at UCSD will NOT pass traffic to an IP address unless that address is associated with a hostname in the [[Ampr.org|ampr.org]] DNS domain.
# Configure your router to act as a [[Gateway]] to the rest of the network.

That's it! You now have a tunnel to the rest of the network. From here, you can connect devices via RF links, subnet your network if you like, and start exploring TCP/IP over amateur radio.

== Next Steps ==

Once you are connected, you should subscribe to the [[44Net mailing list]].

Gateway

2019-07-25T11:38:22Z

WB6CYT:

A lot of the 44/8 address space is interconnected via [[gateway|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel|tunnels]] that carry the AMPRNet address space allocated to a particular region or end user. There exists a database of all the gateways public IP addresses and the subnets they service on the [[portal]]. This database is used to dynamically generate gateway information via modified [[RIP]] advertisements. This database also generates a file called [[encap.txt]] which is basically a routing table that specifies which subnets can be reached via which gateway.

Learn how to [[Setting up a gateway on Linux|setup a Linux gateway]]

Learn how to [[Setting up a gateway on OpenWRT|setup an OpenWRT gateway]]

Learn how to [[Setting up a gateway on Cisco Routers|setup a Cisco Router gateway]]

Learn how to [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]]

In order to keep this database up to date, everyone that operates a gateway must register on the [[portal]] and have their gateway assigned to their account.

Setting up a gateway on Cisco Routers

2019-07-25T11:37:09Z

WB6CYT:

To create a gateway using Cisco equipment you must have a Cisco Router (preferred from series 2600 and above)

Preferred with two Ethernet ports (but can be done also with one Ethernet port)

Pre requirement to the setup to work are as follows:

You have already registered with AMPRNet and got your 44.x.x.x/y allocation and it is showing in the encap.txt file (see "If you are looking to get an IP allocation within the AMPRNet please read the Portal page.") info on the main page .

You have registered some hosts of your allocated network in the AMPRNet DNS like <your call sign>.ampr.org

The example given here here is of one Ethernet port.

You have to assign the router Ethernet port the Commercial IP

The commands are:

enable
configure terminal
interface ethernet0
ip address <and here you give the ip of the commercial isp the router is connected to> (it can also be the IP of a network the router is on (as long as this IP is accessible to the outside world))> <The NetMask of the network>

The interface name can vary depending on your router type, it can be Ethernet0 FastEthernet0 GigabitEthernet0/0 etc.

(To see what interfaces you have in order to assign them the address use the command Show interface and identify the Ethernet port name.)

Then you have to assign the AMPRNet 44.x.x.x IP .

For a router with one port any additional network IP has to be secondary and the command is:

int eth0
ip add <the AMPR IP > <the netmask of the network > secondary

Now some tunneling commands have to be added to redirect your outgoing traffic (via tunnel) to the main AMPRNET router , you do it because every ISP block outgoing IP's which is not a part of their network (and 44 net is not belong to any ISP) so in order to allow the 44 net IP traffic to gain access to the outside world you need to do a tunnel to the AMPR.ORG router to the outgoing traffic (traffic that intend to reach the internet (all other IP's that are not part of the AMPRNet))

To open a tunnel channel you have to specify the tunnel source address (from where the tunnel is established) and tunnel destination (to where the tunnel establish to)

This is done by a few commands here they are

interface tunnel0
tunnel source <here you put the router commercial IP>
tunnel destination <here you put the AMPR.ORG main tunnel router IP>
tunnel mode ipip (this command is to tell the tunnel (cisco support lot of tunneling types) which mode to use)

In addition the router has to be notified to pass all the outgoing 44 Net Traffic to the tunnel interface and not to route it just like that to the Internet (because as explained they will be probably blocked by the closest ISP you are connected to )

The command to do it is

ip route 0.0.0.0 0.0.0.0 Tunnel0 <the ip address of the AMPR.ORG main tunnel router >

(0.0.0.0 0.0.0.0 mean "any IP") (will be explained latter)

Another important command is a command to route the tunneled traffic from the router to the main ampr.org router not via a tunnel (this important to establish tunnel)

This command is more specific then the "any IP" route command described before and say to the router : "pass the tunneled traffic belong to the other side of the tunnel direct and not via tunnel"

The Command is :

ip route <the ampr.org main tunnel IP > 255.255.255.255 Ethernet0 <your router commercial IP>

This are the minimum commands necessary to be able to route your inside 44 net IP to the outside world (but not to any other 44 net networks worldwide)

This method will redirect any outgoing traffic (no matter what local IP is used ) to the tunnel and since the AMPR.ORG tunnel deal with tunneling from only 44 Net IP it mean that if the router local Lan is sharing 44 and non 44 IP machines the non 44 Net machines will have no connectivity to the world

To overcome this problem a route policy will have to be used (with the command route-map) because regular route command deal with route for destination IP without looking at the source (local net) and route policy can do it ...

So two policy have to be created one for all addresses (excluding the AMPRnet that needed to be routed direct to the internet (without tunnel) and second one specifically for the 44 net hosts that needed to redirect their outgoing traffic to the tunnels

In order to route your traffic to other 44 net gateways you need to build a tunnel interface to every gateway (unlike JNOS that one tunnel deal with all tunnels)
and the tunnel have to have a tunnel source tunnel destination (as explained above ) and tunnel mode

In addition two route lines have to be added

One is route command to route the specific 44 network of the gateway this tunnel deal into this tunnel

And another is to allow the tunnel traffic to go thorough the internet

Enclosed is example from router that is doing tunnel to the main AMPR router and to one gateway somewhere in the world

The tunnel0 interface is the Main AMPR.ORG router and the tunnel with 741916672 is one tunnel to a gateway

The section of tunnel74xxx have to duplicated to every 44 net gateway (of course with the corresponding ip of the specific gateway) (currently about 400 times)

TIP: If you are not familiar with Cisco Commands you can use the GUI Software called Cisco Configuration Professional (CCP)

to config the router with it

Later on we will deal of how to create these tunnels lines configuration using a script
that takes the info from the ENCAP.TXT file and convert it to Cisco config

interface Tunnel0
ip unnumbered Ethernet0
no ip directed-broadcast
tunnel source Ethernet0
tunnel destination 169.228.34.84
tunnel mode ipip
!
interface Tunnel741916672
description Link to 44.56.192.0
ip unnumbered Ethernet0
ip access-group acl_44 in
no ip directed-broadcast
tunnel source 10.0.0.180
tunnel destination 24.229.88.253
tunnel mode ipip

interface Ethernet0
description connected to EthernetLAN_HAIFA
ip address 44.138.1.1 255.255.255.0 secondary
ip address 10.0.0.180 255.255.255.0
no ip directed-broadcast

ip classless
ip route 0.0.0.0 0.0.0.0 Tunnel0 169.228.34.84
ip route 169.228.34.84 255.255.255.255 Ethernet0 10.0.0.138
ip route 44.56.192.0 255.255.255.0 Tunnel741916672
ip route 24.229.88.253 255.255.255.255 Ethernet0 10.0.0.138

Making the route commands automatically

Because the route info of the gateways (the encap file) changes periodically
mainly because a lot of gateway sits on dynamic ip

and because the tunnel ip as a result change you may loose the tunnel to these gateways

In order to be "updated" it is needed to take the new encap file periodically and put it into the cisco router

Because the encap file lines are not a format of commands that Cisco "understand" a fomat conversion need to be made in order to convert route info in the encap file to commands that cisco can "understand"

So a Script that take the encap file and make a new file of Cisco commands must be run

There are two scripts that do it available , one is Perl and other is VBS

The example will give the results of the Perl Script

The Perl Script for the Cisco enclosed

#!/usr/bin/perl
#encapconvert.pl V0.1 10-31-12
#Script created by Jason Begley KY9J ky9j.com ky9j@arrl.net
#This script is used for converting the encap.txt file from the AMPR net
#into a loadable config file for use on cisco routers. It is advised to use
#this on a 2600 or better router due to interface limits.
#

my ($line);
my %nets = ();
my $net = undef;
my $mask = undef;

#####
#Below are user defined varibles

my $loop = "Ethernet0"; #LOOPBACK INT CHANGE IF ALREADY IN USE
my $outip = "10.0.0.180"; #YOUR PUBLIC IP ADDRESS
my $loopip = "44.138.1.1"; #YOUR AMPR IP ADDRESS
#EO user defined varibles
#####

my $file = $ARGV[0];
my $debug = $ARGV[1];
if(!$file) { usage(); exit; }
if($file =~ /--help/) { usage(); exit; }

open (MYFILE, '>cisco-config.txt');
print MYFILE "!\ninterface $loop\nip address $loopip 255.255.255.255\n!\n";
close (MYFILE);
open(ENCAP, $file);
@line = <ENCAP>;
close (ENCAP);
@line = grep (!/^\s*$/,@line);
@line = grep (!/^#/,@line);
chomp(@line);

foreach $line(@line)
{
$n1 = $n2 = $n3 = $n4 = undef;
@ln = (split(/ +/, $line));
($n, $s) = (split(/\//, $ln[2]));
($n1, $n2, $n3, $n4) = split(/\./, $n);
$gw = $ln[4];
$gw =~ s/\s*$//;

if ($n1 == '') { $n1='0'};
if ($n2 == '') { $n2='0'};
if ($n3 == '') { $n3='0'};
if ($n4 == '') { $n4='0'};

if ($s == '1') { $mask='128.0.0.0'};
if ($s == '2') { $mask='192.0.0.0'};
if ($s == '3') { $mask='224.0.0.0'};
if ($s == '4') { $mask='240.0.0.0'};
if ($s == '5') { $mask='248.0.0.0'};
if ($s == '6') { $mask='252.0.0.0'};
if ($s == '7') { $mask='254.0.0.0'};
if ($s == '8') { $mask='255.0.0.0'};
if ($s == '9') { $mask='255.128.0.0'};
if ($s == '10') { $mask='255.192.0.0'};
if ($s == '11') { $mask='255.224.0.0'};
if ($s == '12') { $mask='255.240.0.0'};
if ($s == '13') { $mask='255.248.0.0'};
if ($s == '14') { $mask='255.252.0.0'};
if ($s == '15') { $mask='255.254.0.0'};
if ($s == '16') { $mask='255.255.0.0'};
if ($s == '17') { $mask='255.255.128.0'};
if ($s == '18') { $mask='255.255.192.0'};
if ($s == '19') { $mask='255.255.224.0'};
if ($s == '20') { $mask='255.255.240.0'};
if ($s == '21') { $mask='255.255.248.0'};
if ($s == '22') { $mask='255.255.252.0'};
if ($s == '23') { $mask='255.255.254.0'};
if ($s == '24') { $mask='255.255.255.0'};
if ($s == '25') { $mask='255.255.255.128'};
if ($s == '26') { $mask='255.255.255.192'};
if ($s == '27') { $mask='255.255.255.224'};
if ($s == '28') { $mask='255.255.255.240'};
if ($s == '29') { $mask='255.255.255.248'};
if ($s == '30') { $mask='255.255.255.252'};
if ($s == '31') { $mask='255.255.255.254'};
if ($s == '32') { $mask='255.255.255.255'};
if ($s == '') { $mask='255.255.255.255'};

$net = "$n1.$n2.$n3.$n4";
$ifid = cipdec(1, $net);
$wmask = do_subtract($mask);
print "*ip info*\n";
print "NET:$n\nBITS:$s MASK:$mask-$wmask\nGW:$gw\nIF:$ifid\n\n";
open (MYFILE, '>>cisco-config.txt');

if ($debug != NULL) {
print "LINE:$line";
print "\n!\n";
print "interface tunnel $ifid\n";
print "description Link to $net\n";
print "ip unnumbered $loop\n";
print "tunnel source $outip\n";
print "tunnel destination $gw\n";
print "tunnel mode ipip\n!\n";
}

if ($gw != $outip) {

print MYFILE "!\n";
print MYFILE "interface tunnel $ifid\n";
print MYFILE "description Link to $net\n";
print MYFILE "ip unnumbered $loop\n";
print MYFILE "tunnel source $outip\n";
print MYFILE "tunnel destination $gw\n";
print MYFILE "ip tcp adjust-mss 1436\n";
print MYFILE "ip access-group acl_44 in\n!\n";
print MYFILE "tunnel mode ipip\n!\n";
print MYFILE "ip route $net $mask tunnel$ifid\n!\n";
}
print MYFILE "ip route $gw 255.255.255.255 Eth0 10.0.0.138\n";
}
print MYFILE "!\nend\n!\n";
close (MYFILE);

sub usage
{
print << "EOT";
*** This script is for creating a loadable config (copy tftp run) for cisco routers ***
*** Please note that this was tested to work on 2651XM or better, expect poor resp- ***
*** -onse on smaller/slower platforms. ***
*** Edit this file and change varibles as noted to your values. ***
*** File \"cisco-config.txt\" will be generated in this directory for tftp upload ***
*** Run as follows: ***
*** perl encapconvert.pl encap.txt ***
EOT
}

########################################################
# Sub cipdec
# USAGE: For converting IP to DEC values and reverse
#
# my ($err, $ret) = cipdec(1, $ip); #1 =from ip to dec, 2 = from dec to ip
# if($err != 0) { print "MAIN: ERR ON \"$ret\"\n"; next; }
#
sub cipdec
{
my $debug = 0;
my (@oct, $opt, $var, $err, $ret, $errmsg);
my ($oct1, $oct2, $oct3, $oct4);
my ($dec1, $dec2, $dec3);
$opt = shift(@_); #1 =from ip to dec, 2 = from dec to ip
$var = shift(@_); # IP or a DEC
$err = 0;
$ret = 0;
if($debug == 1)
{
print "SUB TEST: OPT=\"$opt\"\n";
print "SUB TEST: VAR=\"$var\"\n";
}
if($opt == 1) #1 =from ip to dec
{
my $ip = $var;

if(!($ip) || ($ip eq "") || !($ip =~ /\./))
{
if($debug == 1) { print "NO . in IP.. Next\n"; }
$err = 1;
$ret = "ERR: IP WITH NO \".\"";
return($err, $ret);
}
@oct = split(/\./, $ip);
my $numoct = @oct;
if($numoct != 4)
{
if($debug == 1) { print "--INVALID IP: \"$ip\"\n"; }
$err = 1;
$ret = "ERR: OCT CT \"$ip\"";
return($err, $ret);
}
foreach my $val (@oct)
{
if(!(defined $val) || ($val eq "") || ($val =~ /\D/) || ($val > 255) || ($val < 0))
{
if($debug == 1) { print "--INVALID IP: \"$ip\"\n"; }
$err = 1;
$ret = "ERR: OCT SIZE \"$ip:$val\"";
return($err, $ret);
} # EO IF oct container
} #EO FOREACH OCT
$ret += ($oct[0] * (256**3)); #Convert 1st octet to decimal and add
$ret += ($oct[1] * (256**2)); #Convert 2nd octet to decimal and add
$ret += $oct[2] * 256; #Convert 3rd octet to decimal and add
$ret += $oct[3]; #Add the 4th octet to decimal
if(($ret < 0) || ($ret > 4294967296)) #0.0.0.0 or 255.255.255.255 = Err
{
if($debug == 1) { print "--INVALID IP: \"$ip\"\n"; }
$err = 1;
$ret = "ERR: DEC SIZE \"$ip\"";
return($err, $ret);
} #EO DEC Size

return($err, $ret);
} #EO OPT == 1

if($opt == 2) #1 = dec to ip
{
$oct1 = 0; $oct2 = 0; $oct3 = 0; $oct4 = 0;
my $dec = $var;
if($debug == 1) { print "SUB TEST: DEC=\"$dec\"\n"; }

if(!(defined $dec) || ($dec eq "") || ($dec < 1) || ($dec > 4294967295)) #0.0.0.0 or 255.255.255.255 = Err
{
if($debug == 1) { print "--INVALID DEC: \"$dec\"\n"; }
$err = 1;
$ret = "ERR: DEC SIZE \"$dec\"";
return($err, $ret);
} #EO DEC Size

if($dec >= 256**3)
{
$oct1 = ($dec / 256**3);
my @num = split(/\./, $oct1);
$oct1 = $num[0];
if($debug == 1) { print "OCT1: \"$oct1\"\n"; }
$dec1 = ($oct1 * 256**3);
$dec = $dec - $dec1;
}
if($dec >= 256**2)
{
$oct2 = ($dec / 256**2);
my @num = split(/\./, $oct2);
$oct2 = $num[0];
if($debug == 1) { print "OCT2: \"$oct2\"\n"; }
$dec2 = ($oct2 * 256**2);
$dec = $dec - $dec2;
}

if($dec >= 256)
{
$oct3 = ($dec / 256);
my @num = split(/\./, $oct3);
$oct3 = $num[0];
if($debug == 1) { print "OCT3: \"$oct3\"\n"; }
$dec3 = $oct3 * 256;
$dec = $dec - $dec3;
}

$oct4 = $dec;
if($debug == 1) { print "OCT4: \"$oct4\"\n"; }
$ret = "$oct1.$oct2.$oct3.$oct4";
return($err, $ret);
} #EO If $opt == 2

$err = 1;
$ret = "I'm lost and sent to leftovers";
return($err, $ret);
}
################### EO SUB CIPDEC#################################

### wildcard sub ###
sub do_subtract( ) {
local($ip) = @_;

# break up the bytes of the incoming IP address
$_ = $ip;
($a, $b, $c, $d) = split(/\./);

if ($a > 255 || $b > 255 || $c > 255 || $d > 255 || /[^0-9.]/) {
print "invalid input mask or wildcard\n";
exit( );
}

$a = 255 - $a;
$b = 255 - $b;
$c = 255 - $c;
$d = 255 - $d;

return ($a . "." . $b . "." . $c . "." . $d);
}

### EO wildcard sub ### </CODE>

Before you run the script make sure to take out the line of your gateway from the encap file

The result of the script is set of commands that look like that

interface tunnel 748306432
description Link to 44.154.64.0
ip unnumbered Ethernet0
tunnel source 10.0.0.180
tunnel destination 79.107.164.191
ip tcp adjust-mss 1436
ip access-group acl_44 in
!
tunnel mode ipip
!
ip route 44.154.64.0 255.255.255.0 tunnel748306432
!
ip route 79.107.164.191 255.255.255.255 Ethernet0 10.0.0.138
!

This section return on itself (with different IP , destination and route IPs's ) as the amount of lines in the encap file

When the file is ready (after running the perl script) you can copy it with editor and send it to the cisco or by terminal (with the config t command) or by TFTP

The Encap file can be taken automatically from the Portal using the API
and you can push the commands to the cisco (after the encap convert to cisco commands after running perl) with TFTP

So with a small software work the whole procedure can be done fully automatic

Setting up a gateway on MacOS

2019-07-25T11:33:51Z

WB6CYT:

Note to editor: when this is complete and tested, link to home page.

These are instructions for setting up a MacOS system as a gateway, using the [[Setting up a gateway on Linux]] as a starting point.

Before configuring the MacOS gateway you'll need to:

* Using the Portal, obtain your AMPRnet IP addresses from a regional coordinator.
* Obtain a public static IP address for your gateway.
* Using the Portal, create an entry for your gateway.
* Get some of your AMPRNet IP addresses registered in the ampr.org DNS.

Setting up a gateway on Linux

2019-07-25T11:32:18Z

WB6CYT:

There are a few different ways to run an AMPRnet gateway on a Linux system. Each has some benefits, so you'll need to pick your favourite.

Before configuring the Linux gateway you'll need to:
# Using the [[Portal]], obtain your AMPRnet IP addresses from a regional coordinator.
# Obtain a public static IP address for your gateway.
# Using the [[Portal]], create an entry for your gateway.
# Get some of your AMPRNet IP addresses registered in the [[ampr.org]] DNS.

= Flavours of Linux gateways =

== Native Linux kernel AX.25 and IPIP tunneling ==

Linux contains the necessary building blocks for a gateway without much added software. Radio interfaces are configured much like any other network interfaces such as Ethernet, they're just given amateur radio callsigns in addition to an IP address (callsign will act the role of the Ethernet MAC address). If you're familiar with Linux configuration but have not heard of NOS, or if you wish to go with minimal amount of moving parts, this would probably be your choice.

Setting up a native Linux gateway consists of two main steps:

=== Step 1: Setting up tunnel routing to the rest of the AMPRnet===
Configuring your Linux system to learn about other AMPRNet [[gateway| gateways]] can be done two ways:

# Automatically learn about other gateways via modified RIPv2 advertisements. Two popular programs to do this are:
## Using [[ampr-ripd]], a C based routing daemon
## Using [[rip44d]], a PERL based routing daemon
# Manually Downloading the [[encap.txt]] file using FTP and setting up routes using a [[munge script]] is the traditional method

====Example Gateway Configuration Instructions====
* [[Ubuntu Linux Gateway Example]]
* [http://www.qsl.net/k/kb9mwr//wapr/tcpip/ampr-ripd.html Two Interface Debian Linux Amprnet Gateway Example]
* [[URONode|N1URO's information on setting up a gateway on Linux]]

=== Step 2: Setting up radio interfaces in Linux===

* [http://www.tldp.org/HOWTO/AX25-HOWTO/ Linux AX.25 set-up]
* 802.11 WiFi on amateur frequencies (2.4 or 5 GHz) is a new popular way to set up fast links.

== Running JNOS (or other NOS) on top of Linux ==

If you're already familiar with running NOS on top of DOS or Linux, or wish to keep the AMPRnet IP packet routing away from the host Linux system, it might make sense to run JNOS as an application on top of Linux.

The downside is that it'll have a slightly higher overhead (consumed memory and CPU), and you'll have two IP routers running on top of each other instead of just one, which is seen as slightly complicated by some.

The upside is that you'll also get the JNOS BBS-type features, and some other traditional services without installing additional software on top.

John Martin KF8KK has written a [http://kf8kk.com/packet/jnos-linux/linux-jnos-setup-1.htm Linux - Jnos Setup and Configuration HOW-TO].

=See also=

* [[Ubuntu Linux Gateway Example]]
* [[startampr]]

Portal

2019-07-25T11:30:41Z

WB6CYT:

We have developed a Portal that allows users of the AMPRNet address space to manage their allocations, configure gateway information and manage their entries in the ampr.org domain. The portal can be found here:

[https://portal.ampr.org https://portal.ampr.org]

If you are looking to get an IP allocation within AMPRNet please register on the portal and place your request.

==Background==
The main problem we faced with the old setup was how to ensure the data we have is accurate and up to date.

The new portal is our answer to that problem: folks register and are allocated an IP or subnet of IP's that they are responsible for. The system doesn't then just let them get on with it - the system is designed to actively ensure that each allocation is still being used, the person must login to the portal on a regular basis, or if they do not, an email will be sent automatically to them asking them to confirm their continued use of the IP(s). If no response is received from the emailed request, two further attempts are made to contact the person, after which the system places their allocation in a de-activated state. The person is able to login and re-activate the allocation for a certain time after de-activation, beyond that time period the allocation will be deleted from the database - thus keeping it all as up to date as is possible.

Some manual intervention is encouraged, for example the second, and all subsequent reminder emails and de-activation emails are cc'd to the co-ordinator responsible for the next higher subnet, so they could attempt a more manual approach to remind the person to login - this is to be encouraged as sometimes emails (especially automated ones) can be blocked in spam folders, people change their email address and forget to update the portal, etc.

== API ==
The Portal has an associated [[API]]

Archive/Main Page

2019-07-25T11:28:52Z

WB6CYT:

Welcome to the AMPRNet Wiki.

Since its allocation to Amateur Radio in the mid-1980's, Internet network 44 (44.0.0.0/9, 44.128.0.0/10), known as the AMPRNet™, has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio with a goal of advancing the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques. - [http://www.ampr.org/ www.ampr.org]

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the [[AMPRNet]]
* Basic information about the [[AMPRNet]] and the [[ampr.org]] domain
* [[Services]] available on AMPRNet
* If you are looking to get an IP allocation within the AMPRNet please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]

== How to connect to AMPRNet ==

* Instructions for [[Setting up a gateway on Linux|setting up a Linux gateway]]
* Instructions for [[Setting up a gateway on OpenBSD|setting up an OpenBSD gateway]]
* Instructions for [[setting up a gateway on Cisco Routers|setting up a gateway on Cisco Routers]].
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* Instructions for [[setting up a gateway on OpenWRT|setting up a gateway on OpenWRT]].
* Instructions for [[setting up a gateway on Ubiquiti EdgeRouter|setting up a gateway on Ubiquiti EdgeRouter]].
* Instructions for [[setting up a gateway on a VyOS instance|setting up a gateway on a VyOS instance]].
* Instructions for [[Installing ampr-ripd on a Ubiquiti EdgeRouter or EdgeRouter X|Installing ampr-ripd on a Ubiquiti EdgeRouter or EdgeRouter X]].
* Instructions for [[announcing your allocation directly|directly announcing your allocation via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet VPN|Accessing AMPRNet via VPN]] (experimental).
* [[Why can't I just route my AMPRNet allocation directly myself ?]]
* If you already operate a [[gateway]] please ensure you have registered on the [[portal]] and "claimed" your [[gateway]].
* After your gateway is operational, consider '''[[Firewalls]]''' and other best practices

== Mailing List ==
To keep up-to-date on AMPRNet information please consider joining the [[44Net mailing list]].

== Contribute! ==
If you wish to contribute to the wiki, please send an email to <tt>wiki (at) ampr.org</tt> introducing yourself. Please specify your full name, amateur radio callsign and your preferred username. A login will then be created for you.

== Terms of Service ==
Use of AMPRNet address space is governed by these [http://www.ampr.org/terms-of-service/ Terms of Service]

== Other useful features ==
* Instruction on using the [[ampr-map]] position reporting

== All Pages ==
[http://wiki.ampr.org/wiki/Special:AllPages Here's a list of all pages currently on the AMPRNet Wiki]

Amprgw

2017-05-27T04:55:24Z

WB6CYT: AMPRGW is amprgw.ucsd.edu, at IP address 169.228.34.84

AMPRGW is amprgw.ucsd.edu, at IP address 169.228.34.84. It is the Internet-to-AMPRNet router.

Announcing your allocation directly

2017-05-15T12:00:18Z

WB6CYT:

NOTE: Direct announcements of AMPRNet address allocations are usually reserved for larger regional or country wide networks. Please consult with your regional allocation coordinator and the AMPRNet network administrator to determine whether directly announcing your AMPRNet allocation is appropriate.

To announce your allocation directly via your Internet Service Provider (ISP) you will need to:

# Contact your ISP and ask them if they are willing to announce your AMPRNet allocation in accordance with the terms of the [http://www.ampr.org/terms-of-service/ AMPRNet Terms of Service and Acceptable Use]. Many ISPs won't do this, and others charge a significant amount for the service.
# Apply for your AMPRNet allocation via the [[Portal]]. Check the Direct box to indicate that your connection will be using a direct announcement of the subnet (via the BGP protocol).
# Upon verification and approval, the AMPRNet administrator will provide authorization to your ISP allowing them to announce your allocation.

NOTE: How your ISP chooses to forward traffic for your AMPRNet allocation varies by ISP. You will have to work with them to set this up.

NOTE: Upon approval, [[ARDC]] issues a no-cost lease for five years (renewable) for the subnet. This includes a letter of authority that should be provided to your ISP. ARDC does NOT [[SWIP]] subnet allocations.

Archive/Main Page

2017-03-31T17:20:06Z

WB6CYT:

Welcome to the AMPRNet Wiki.

Since its allocation to Amateur Radio in the mid-1980's, Internet network 44 (44.0.0.0/8), known as the AMPRNet™, has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio with a goal of advancing the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques. - [http://www.ampr.org/ www.ampr.org]
__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the [[AMPRNet]]
* Basic information about the [[AMPRNet]] and the [[ampr.org]] domain
* [[Services]] available on AMPRNet
* If you are looking to get an IP allocation within the 44/8 AMPRNet please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]

== How to connect to AMPRNet ==

* Instructions for [[Setting up a gateway on Linux|setting up a Linux gateway]]
* Instructions for [[Setting up a gateway on OpenBSD|setting up an OpenBSD gateway]]
* Instructions for [[setting up a gateway on Cisco Routers|setting up a gateway on Cisco Routers]].
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* Instructions for [[setting up a gateway on OpenWRT|setting up a gateway on OpenWRT]].
* Instructions for [[setting up a gateway on Ubiquiti EdgeRouter|setting up a gateway on Ubiquiti EdgeRouter]].
* Instructions for [[announcing your allocation directly|directly announcing your allocation via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet VPN|Accessing AMPRNet via VPN]] (experimental).
* [[Why can't I just route my AMPRNet allocation directly myself ?]]
* If you already operate a [[gateway]] please ensure you have registered on the [[portal]] and "claimed" your [[gateway]].

== Mailing List ==
To keep up-to-date on AMPRNet information please consider joining the [[44Net mailing list]].

== Contribute! ==
If you wish to contribute to the wiki, please send an email to <tt>wiki (at) ampr.org</tt> introducing yourself. Please specify your full name, amateur radio callsign and your preferred username. A login will then be created for you.

== Terms of Service ==
Use of 44.0.0.0/8 address space is governed by these [http://www.ampr.org/terms-of-service/ Terms of Service]

== All Pages ==
[http://wiki.ampr.org/wiki/Special:AllPages Here's a list of all pages currently on the AMPRNet Wiki]

FAQ

2016-11-06T14:24:47Z

WB6CYT:

'''Frequently Asked Questions'''

'''What is AMPRNET?'''

AMPRNET stands for Amateur Radio Packet Radio Network. It is a collection of amateur radio-oriented computers, connected together via a variety of technologies, including radio, Internet, and ethernet. However, all of these computers have an IP address that begins with 44 (that is, IP addresses of the form 44.x.x.x). For this reason, AMPRnet can also be referred to as 44-net.
Some further details can be found at https://en.wikipedia.org/wiki/AMPRNet and http://wiki.ampr.org/wiki/Main_Page

'''What is AMPRNET for?'''

The purpose of AMPRNET is to permit experimentation by amateurs in digital networking, and to provide computer services to other amateurs using AMPRNET.

'''What does it cost to use AMPRNET?'''

There is no cost for using any AMPRNET facilities, however there may be costs associated with Internet access to reach AMPRNET and/or amateur radio equipment costs.

'''How do I connect to AMPRNET?'''

There are four main methods people use:

a) IP Tunneling

b) VPN

c) BGP routing

d) Direct radio links.

Note: Functionally, a VPN and a tunnel do much the same thing, except a VPN is designed for privacy (i.e. strong authentication and encryption), while a tunnel is for the transfer of packets, not necessarily encrypted. However, in the AMPRNET world, they tend to get used quite separately and so are discussed separately in this FAQ.

'''What is IP Tunneling?'''

The information that traverses the Internet does so as "packets" of data, traveling over a variety of routes, between a source and a destination. Each packet contains a header, which tells all the devices along the route information such as the source and destination, plus the payload, which is the data to actually be transferred. Clearly, there must be a path all the way from the sources to the destination, and back.
AMPRNET consists of small, non-connected groups of computers, that would otherwise not be able to connect to one another. However, since internet devices along the route really don't care about the contents of the payload section, you can put a complete new packet into that section, including an entirely different header, and it's own payload section. That second header has source and destination addresses completely different to the first header - all that is required is that the first destination recognises the encapsulated packet, de-encapsulates it, and forwards it the the second header destination. Return traffic follows a corresponding process. In that way, 44-net hosts can communicate with other 44-net hosts, by means of encapsulating their data packets in packets to non-44net hosts. This is called tunneling (or encapsulating). A later section in this FAQ discusses installing a tunnel. This diagram http://ericleahy.com/wp-content/uploads/2011/08/IP-Tunnel-Encp-300x256.jpg shows tunnelling another way.
Tunneling is probably the most commonly used method of accessing AMPRNET.

'''What is a VPN?'''

VPN stands for Virtual Private Network. It is a facility that enables a computer to act (using the Internet) as though is is physically connected to another computer network. There are many different ways to set up a VPN, so this is beyond the scope of this FAQ. However it always involves configuring software and accounts on a computer, to connect to the VPN server. Some amateurs who have connections to AMPRNET have set up VPN servers, so that other amateurs can achieve a "virtual" connection to AMPRNET. The technical details, account details and IP address details must be obtained from the operator of that VPN. One such VPN is listed at http://wiki.ampr.org/wiki/AMPRNet_VPN.

'''What is BGP Routing?'''

The Internet has millions of different computers connected to it, each having an address. Devices called routers deliver traffic between computers, and can send "advertisements" to other routers to tell those other routers about the locations of some of those addresses. The protocol used is called BGP, Border Gateway Protocol. If you are fortunate enough to have a computer that can send BGP advertisements, then you can advertise that your computer is part of the AMPRNET address range, and hence receive AMPRNET traffic.

Unfortunately, most most companies and most commercial ISP's will not permit their users to originate BGP advertisements (especially for address ranges that are not in their usual address range), so BGP is not a viable means to connect to AMPRNET for most people.

Installing BGP is beyond the scope of this FAQ. Note however that you must have written permission from Brian Kantor, the administrator of the 44 address space, before you BGP advertise any part of that space.

'''What about radio links?'''

In many places, groups of amateurs have established networks of radio links, and often have used one of the preceding approaches so that those radio networks connect to and become part of AMPRNET. You would need to contact those groups regarding frequencies, modes, and address allocations.

'''Do I need to consider security?'''

Yes! Any computer connected to the Internet must be configured and maintained in a secure fashion, and this includes any computer connected to AMPRNET (regardless of the connection technique). Repeat - you MUST secure your computer! This includes using firewalls, keeping software up to date, using strong passwords, etc etc. In some cases, encryption may also be used.

How to maintain security is beyond the scope of this FAQ. Searching for "How to secure my computer" will return many, many hits though!

'''How do I get an address allocation?'''

If you connect to an existing VPN or existing radio network, it is likely that the operators of those facilities will already have address ranges established and will allocate your address(es). If you wish to establish a new tunnel or BGP-based link, then the process is handled by a semi-automated process on our portal. The steps are:
1. Register using your callsign on the portal https://portal.ampr.org
2. Log in and navigate to the Networks page.
3. Click on your country. A list of regions/subnets may appear; if so, click on the appropriate one.
4. Click on the subnet and you'll be presented with a simple form to complete.
5. If you are requesting a single address for a host, leave the netmask as /32;
6. if you are requesting a block/subnet, select the appropriate netwidth. E.g. for a 256 host subnet, select /24.
7. Put a short message explaining your request in the Message area of the form. Be sure to indicate
if you are planning to directly route a subnet as these require special handling
8. Click Send. Your request will be forwarded to the coordinator for your region/subnet. You'll
receive a confirming email. The coordinator may contact you for further details if required.

'''Can I have a domain name entry for my AMPRNET host?'''

Yes. Currently domain name requests are handled by the area coordinators - contact details are on the portal. Note: the old email robot facility no longer functions.

'''What about IPv6?'''

There is no IPv6 equivalent of AMPRNET at present.

'''How do I configure a Tunnel?'''

The technique varies according to the Operating System you use. However, all involve the creation of a new "pseudo" interface - unlike your normal ethernet network connection, this one doesn't actually exist on the back panel of your computer. However, it exists as far as the Operating System is concerned. A normal ethernet device accepts a data packet (consisting of a header and payload, as previously discussed) and sends it out the ethernet cable (often via a modem, to the Internet). A "pseudo" interface however accepts a data packet, encapsulates it in the data portion of a new packet, adds a new and different header, and passes all that to the ethernet device, which then processes this new data packet as normal, sending it to a recipient who will de-encapsulate it. Reception of tunneled traffic is the reverse process.

Consequently, two requirements apply:

a) The computer must have full connectivity to the non-44 hosts that will send or receive the tunneled packets containing 44-net traffic. You cannot route ALL traffic to the pseudo interface!

b) The pseudo driver must have a mechanism to tell it which non-44 net hosts can handle particular subsets of 44-net traffic - very few can handle the entire 44-net range! It should be noted that the information changes quite frequently, as tunnel hosts come and go, so must be updated as described below.

http://wiki.ampr.org/wiki/Main_Page has links to several different ways of configuring tunnels.

'''How do I obtain and maintain a list of tunnel hosts?'''

There are three main mechanisms:

a) log on to the portal (as described above) and navigate to the "Gateways/List" section that permits downloading of the "encap" file. Download that file, and use a script on the computer to turn it into commands that update the configuration of the tunnel device.

b) receive the encap file by mail, and use a script to process it. You can register for this email on the portal "Gateways/Options" page.

c) Receive and process "broadcasts" of configuration data that are available. This information is broadcast to all gateways listed on the portal. There is a software package called "ampr-ripd" that enables this process

'''Can I just route all 44net traffic via a single tunnel?'''

No. The main AMPRNET gateway does not provide this functionality - you must have a tunnel to each system you wish to contact.

'''Can BGP, VPN and IP tunnel hosts inter-communicate?'''

Yes. The AMPRNET gateway has been configured to support this functionality.

'''Can I put my tunnel on my home LAN and use NAT?'''

Yes. However, in general, a home modem using NAT won't be able to correctly process inbound tunneled 44-net traffic and forward it to the correct host - the "port forward" facility in most NAT devices relies on a port number, but there are no port numbers for a tunnel packet! However, most modems have a "DMZ" facility, whereby all unrecognised traffic (and this includes tunneled traffic) can be forwarded to one particular host on the LAN. That host can then be configured to recognise and correctly process tunneled data. However - security alert! - it will also be exposed to all sorts of other, unwanted traffic as well! See the Security section above.

'''Can I use an AMPRNET VPN on my home LAN?'''

Generally, yes. Most home modem/routers have good support for VPN usage.

'''How can I get help with AMPRNET issues?'''

Many amateurs are willing to assist other hams. There is also a very active mailing list - see http://hamradio.ucsd.edu/mailman/listinfo/44net. The wiki at http://wiki.ampr.org/ has a great deal of information.

'''What about 44.128.0.0/16?'''

Subnet 44.128.0.0/16 is currently reserved for testing. No operational subnets are planned for this address space. Older documentation incorrectly referred to this block of addresses as "private", that is, unrouted like the 192.168.0.0/16 RFC1918 subnet. This is incorrect; the 44.128.0.0/16 subnet can be routed. Do not use it except for brief test purposes.

'''Credits'''

This FAQ originally commenced by Steve VK5ASF, using material from earlier FAQ's, from various contributors to the 44net mailing list, and from Brian Kantor.

ARDC

2016-10-29T12:05:55Z

WB6CYT:

ARDC, the Amateur Radio Digital Communications corporation, is a non-profit California corporation that owns network 44.0.0.0/8, known as the AMPRNet. It was formed to encourage and foster the development of the Amateur Radio packet and other amateur radio digital networking. You may contact ARDC by sending email to ardc@ampr.org.

Note that ARDC is not an Internet Service Provider. It does not provide any networking access or facilities. It solely manages and allocates Internet address space, subnets of network 44 (AMPRNet), to interested Amateur Radio operators. Persons who obtain an allocation of address space on AMPRNet must make their own arrangements for connectivity and Internet service.

SWIP

2016-10-29T11:59:50Z

WB6CYT: Created page with "SWIP is the [https://en.wikipedia.org/wiki/Shared_Whois_Project Shared Whois Project]. It consists of a database showing the ownership of subnets of the Internet. ARDC d..."

SWIP is the [https://en.wikipedia.org/wiki/Shared_Whois_Project Shared Whois Project]. It consists of a database showing the ownership of subnets of the Internet. [[ARDC]] does not list its allocated subnets in the SWIP database because listing of a subnet in that database implies that the entity listed has ownership of the subnet, and ARDC does not relinquish nor assign ownership of its subnets. Rather, allocations take the form of a limited-term no-cost lease of the subnet address space, with ARDC retaining full ownership. This is done primarily to prevent allocated subnets from being sold.

ARDC

2016-10-29T11:48:23Z

WB6CYT: Created page with "ARDC, the Amateur Radio Digital Communications corporation, is a non-profit California corporation that owns network 44.0.0.0/8, known as the AMPRNet. It was formed to encour..."

Announcing your allocation directly

2016-10-29T11:39:11Z

WB6CYT:

NOTE: Direct announcements of AMPRNet address allocations are usually reserved for larger regional or country wide networks. Please consult with your regional allocation coordinator and the AMPRNet network administrator to determine whether directly announcing your AMPRNet allocation is appropriate.

To announce your allocation directly via your Internet Service Provider (ISP) you will need to:

# Contact your ISP and ask them if they are willing to announce your AMPRNet allocation in accordance with the terms of the [http://www.ampr.org/wp-content/uploads/tos.txt AMPRNet Terms of Service and Acceptable Use Agreement]. Many ISPs won't do this, and others charge a significant amount for the service.
# Apply for your AMPRNet allocation via the [[Portal]]. Check the Direct box to indicate that your connection will be using a direct announcement of the subnet (via the BGP protocol).
# Upon verification and approva, the AMPRNet administrator will provide authorization to your ISP allowing them to announce your allocation.

NOTE: How your ISP chooses to forward traffic for your AMPRNet allocation varies by ISP. You will have to work with them to set this up.

NOTE: Upon approval, [[ARDC]] issues a no-cost lease for five years (renewable) for the subnet. This includes a letter of authority that should be provided to your ISP. ARDC does NOT [[SWIP]] subnet allocations.

Announcing your allocation directly

2016-10-29T11:38:26Z

WB6CYT:

NOTE: Direct announcements of AMPRNet address allocations are usually reserved for larger regional or country wide networks. Please consult with your regional allocation coordinator and the AMPRNet network administrator to determine whether directly announcing your AMPRNet allocation is appropriate.

To announce your allocation directly via your Internet Service Provider (ISP) you will need to:

# Contact your ISP and ask them if they are willing to announce your AMPRNet allocation in accordance with the terms of the [http://www.ampr.org/wp-content/uploads/tos.txt AMPRNet Terms of Service and Acceptable Use Agreement]. Many ISPs won't do this, and others charge a significant amount for the service.

# Apply for your AMPRNet allocation via the [[Portal]]. Check the Direct box to indicate that your connection will be using a direct announcement of the subnet (via the BGP protocol).

# Upon verification and approva, the AMPRNet administrator will provide authorization to your ISP allowing them to announce your allocation.

NOTE: How your ISP chooses to forward traffic for your AMPRNet allocation varies by ISP. You will have to work with them to set this up.

NOTE: Upon approval, [[ARDC]] issues a no-cost lease for five years (renewable) for the subnet. This includes a letter of authority that should be provided to your ISP. ARDC does NOT [[SWIP]] subnet allocations.

Archive/Main Page

2016-09-24T02:49:17Z

WB6CYT: /* How to connect to AMPRNet */

Welcome to the AMPRNet Wiki.

Since its allocation to Amateur Radio in the mid-1980's, Internet network 44 (44.0.0.0/8), known as the AMPRNet™, has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio with a goal of advancing the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques. - [http://www.ampr.org/ www.ampr.org]
__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the [[AMPRNet]]
* Basic information about the [[AMPRNet]] and the [[ampr.org]] domain
* [[Services]] available on AMPRNet
* If you are looking to get an IP allocation within the 44/8 AMPRNet please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]

== How to connect to AMPRNet ==

* Instructions for [[Setting up a gateway on Linux|setting up a Linux gateway]]
* Instructions for [[Setting up a gateway on OpenBSD|setting up an OpenBSD gateway]]
* Instructions for [[setting up a gateway on Cisco Routers|setting up a gateway on Cisco Routers]].
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* Instructions for [[setting up a gateway on OpenWRT|setting up a gateway on OpenWRT]].
* Instructions for [[setting up a gateway on Ubiquiti EdgeRouter|setting up a gateway on Ubiquiti EdgeRouter]].
* Instructions for [[announcing your allocation directly|directly announcing your allocation via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet VPN|Accessing AMPRNet via VPN]] (experimental).
* [[Why can't I just route my AMPRNet allocation directly myself ?]]
* If you already operate a [[gateway]] please ensure you have registered on the [[portal]] and "claimed" your [[gateway]].

== Mailing List ==
To keep up-to-date on AMPRNet information please consider joining the [[44Net mailing list]].

== Contribute! ==
If you wish to contribute to the wiki, please send an email to <tt>wiki (at) ampr.org</tt> introducing yourself. Please specify your full name, amateur radio callsign and your preferred username. A login will then be created for you.

== Terms of Service ==
Use of 44.0.0.0/8 address space and ampr.org DNS is governed by the following [http://www.ampr.org/wp-content/uploads/tos.txt Terms of Service]

== All Pages ==
[http://wiki.ampr.org/wiki/Special:AllPages Here's a list of all pages currently on the AMPRNet Wiki]

Archive/Main Page

2016-06-19T21:07:59Z

WB6CYT: /* Terms of Service */

Welcome to the AMPRNet Wiki.

Since its allocation to Amateur Radio in the mid-1980's, Internet network 44 (44.0.0.0/8), known as the AMPRNet™, has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio with a goal of advancing the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques. - [http://www.ampr.org/ www.ampr.org]
__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the [[AMPRNet]]
* Basic information about the [[AMPRNet]] and the [[ampr.org]] domain
* [[Services]] available on AMPRNet
* If you are looking to get an IP allocation within the 44/8 AMPRNet please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]

== How to connect to AMPRNet ==

* Instructions for [[Setting up a gateway on Linux|setup a Linux gateway]]
* Instructions for [[setting up a gateway on Cisco Routers|setting up a gateway on Cisco Routers]].
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* Instructions for [[setting up a gateway on OpenWRT|setting up a gateway on OpenWRT]].
* Instructions for [[setting up a gateway on Ubiquiti EdgeRouter|setting up a gateway on Ubiquiti EdgeRouter]].
* Instructions for [[announcing your allocation directly|directly announcing your allocation via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet VPN|Accessing AMPRNet via VPN]] (experimental).
* [[Why can't I just route my AMPRNet allocation directly myself ?]]
* If you already operate a [[gateway]] please ensure you have registered on the [[portal]] and "claimed" your [[gateway]].

== Mailing List ==
To keep up-to-date on AMPRNet information please consider joining the [[44Net mailing list]].

== Contribute! ==
If you wish to contribute to the wiki, please send an email to <tt>wiki (at) ampr.org</tt> introducing yourself. Please specify your full name, amateur radio callsign and your preferred username. A login will then be created for you.

== Terms of Service ==
Use of 44.0.0.0/8 address space and ampr.org DNS is governed by the following [http://www.ampr.org/wp-content/uploads/tos.txt Terms of Service]

== All Pages ==
[http://wiki.ampr.org/wiki/Special:AllPages Here's a list of all pages currently on the AMPRNet Wiki]