44Net Wiki - User contributions [en]

Quickstart

2023-11-14T01:15:22Z

W9OQI:

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.

A system diagram showing 44Net is available

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]].
Click on REGISTER and complete the requested information

# 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]].

Here

2023-11-13T16:01:08Z

W9OQI: Created page with "https://wiki.ampr.org/wiki/File:44NetArch-23-7.jpg"

https://wiki.ampr.org/wiki/File:44NetArch-23-7.jpg

Quickstart

2023-11-13T15:57:44Z

W9OQI:

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.

A system diagram showing 44Net is available [[here]]

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]].
Click on REGISTER and complete the requested information

# 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]].

Quickstart

2023-11-13T15:54:21Z

W9OQI:

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.

A system diagram showing 44Net is available here

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]].
Click on REGISTER and complete the requested information

# 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]].

File:44NetArch-23-7.jpg

2023-11-09T16:08:24Z

W9OQI:

Archive/Main Page

2023-11-08T20:02:31Z

W9OQI:

Welcome to the AMPRNet Wiki.

44Net is shorthand for Internet network 44 (44.0.0.0/9 & 44.128.0.0/10), also known as AMPRNet. Since its allocation to amateur radio in the mid-1980s, the network has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio. The goals are to of advance the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques.

To request an assignment of IPv4 addresses see below.

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* Instructions for [[Setting up a gateway on Linux|setting up a Linux gateway]]
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* 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 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[OH7LZB_VPN|Accessing 44Net 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

== Groups.io ==
We are now on Groups.io Please consider joining https://ardc.groups.io/g/44net

== 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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

Archive/Main Page

2023-11-08T19:56:23Z

W9OQI:

Welcome to the AMPRNet Wiki.

44Net is shorthand for Internet network 44 (44.0.0.0/9 & 44.128.0.0/10), also known as AMPRNet. Since its allocation to amateur radio in the mid-1980s, the network has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio. The goals are to of advance the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques.

To request an assignment of IPv4 addresses see below.

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* Instructions for [[Setting up a gateway on Linux|setting up a Linux gateway]]
* Instructions for [[setting up a gateway on MikroTik Routers|setting up a gateway on MikroTik Routers]].
* 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 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[OH7LZB_VPN|Accessing 44Net 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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

Gateway

2023-11-08T19:53:29Z

W9OQI:

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 MikroTik Routers|setting up a gateway on MikroTik Routers]]

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]]

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.

Ampr.org

2023-08-16T13:54:00Z

W9OQI:

AMPR.ORG is the domain that is available for ham radio operators to register their [[AMPRNet]] network [https://en.wikipedia.org/wiki/Host_%28network%29 hosts], and for other ham radio related computer systems.

Domain names in AMPR.ORG are available to any licensed [https://en.wikipedia.org/wiki/Amateur_radio_operator amateur radio operator] who is interested in advancing the art of ham radio digital communications. In most countries, there is a local coordinator who is responsible for assigning an address and updating the master hosts list. [https://portal.ampr.org/networks.php https://portal.ampr.org/networks.php] There is no formal organization, no membership requirements, and no dues. All of the work is done by volunteers as they have time to do it. Note that an IP address ''must'' be associated with a domain name in AMPR.ORG in order for the main gateway at UCSD to pass packets to it.

If you are a licensed ham who needs an address, contact your local coordinator. AMPR.ORG is not intended to be, and should not be used as, a substitute for buying a personal domain name.

Ampr.org

2023-08-16T13:53:34Z

W9OQI:

AMPR.ORG is the domain that is available for ham radio operators to register their [[AMPRNet]] network [https://en.wikipedia.org/wiki/Host_%28network%29 hosts], and for other ham radio related computer systems.

Domain names in AMPR.ORG are available to any licensed [https://en.wikipedia.org/wiki/Amateur_radio_operator amateur radio operator] who is interested in advancing the art of ham radio digital communications. In most countries, there is a local coordinator who is responsible for assigning an address and updating the master hosts list. [https://portal.ampr.org/networks.php https://portal.ampr.org/networks.php] There is no formal organization, no membership requirements, and no dues. All of the work is done by volunteers as they have time to do it. Note that an IP address ''must'' be associated with a domain name in AMPR.ORG in order for the main gateway at UCSD to pass packets to it.

If you are a ham who needs an address, contact your local coordinator. AMPR.ORG is not intended to be, and should not be used as, a substitute for buying a personal domain name.

Tunnel

2023-08-16T13:37:09Z

W9OQI:

From: [https://en.wikipedia.org/wiki/IP_tunnel]:

An IP tunnel is an Internet Protocol (IP) network communications channel between two networks. It is used to transport another network protocol by encapsulation of its packets.

IP tunnels are often used for connecting two disjoint IP networks that don't have a native routing path to each other, via an underlying routable protocol across an intermediate transport network.

Tunnel

2023-08-16T13:00:02Z

W9OQI:

Archive/Main Page

2023-08-16T12:58:40Z

W9OQI:

Welcome to the AMPRNet Wiki.

44Net is shorthand for Internet network 44 (44.0.0.0/9, 44.128.0.0/10), also known as AMPRNet. Since its allocation to amateur radio in the mid-1980s, the network has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio. The goals are to of advance the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques.

To request an allotment of IP v4 addresses see below.

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet_VPN|Accessing 44Net 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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

Archive/Main Page

2023-07-19T20:02:10Z

W9OQI:

Welcome to the AMPRNet Wiki.

44Net is shorthand for Internet network 44 (44.0.0.0/9, 44.128.0.0/10), also known as AMPRNet. Since its allocation to amateur radio in the mid-1980s, the network has been used by amateur radio operators to conduct scientific research and to experiment with digital communications over radio. The goals are to of advance the state of the art of Amateur Radio networking, and to educate amateur radio operators in these techniques.

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet_VPN|Accessing 44Net 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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

Filtering RFC1918 Addresses

2023-07-12T21:23:44Z

W9OQI:

== Mikrotik RouterOS ==

<ol>
<li>Define an RFC1918 address list
<pre>/ip firewall address-list
add address=10.0.0.0/8 list=RFC1918
add address=172.16.0.0/12 list=RFC1918
add address=192.168.0.0/16 list=RFC1918</pre>
</li>
<li>Perform NAT on traffic coming into AMPR from RFC1918 space
<pre>/ip firewall nat
add action=masquerade chain=srcnat src-address-list=RFC1918</pre>
</li>
</ol>

Filtering RFC1918 Addresses

2023-07-12T21:23:15Z

W9OQI:

FAQ

2023-06-06T17:31:31Z

W9OQI: Deleted sentence and link to the file as the server the image resides on does not respond correctly.

'''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.0.0.0/9 or 44.128.0.0/10). For this reason, AMPRnet can also be referred to as 44Net.
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:

* IP Tunneling
* VPN
* BGP routing (See Also [[Announcing your allocation directly]])
* 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 completely new packet into that section, including an entirely different header, and its own payload section. That second header has source and destination addresses completely different from the first header - all that is required is that the first destination recognizes the encapsulated packet, de-encapsulates it, and forwards it to 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.
Tunneling is probably the most commonly used method of accessing AMPRNet.

'''How does AMPR over IP tunnel actually work?'''

AMPR nodes are actually not connected via a single tunnel but via a large mesh network of tunnels. Suppose user1 has public IP address 198.51.100.1 and user2 has 203.0.113.1. These two can normally communicate over the internet. However, if both users have a 44net IP address, user1 can encapsulate the 44 packet into an outer packet and send it to 203.0.113.1. Similarly, user2 can encapsulate the IP packet with the 44net addresses and send it to 198.51.100.1. In Linux (and most other systems), this is accomplished using a single ipip device and adding a route using the "nexthop" statement. When a packet is pushed into the ipip device, the outer IP header is added and sent to the router in the nexthop statement. A list of all AMPR users is required and this can be either accomplished by downloading a simple textfile and adding the routes manually or by using RIP44, as discussed in the FAQ section below.

'''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 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 companies and most commercial ISPs 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. There are Virtual Private Server (VPS) Providers (or Cloud Providers) who will announce your AMPRNet allocation without the need for your own Autonomous System (AS) number. [[Routing your allocation via BGP]] has a list of VPS/Cloud Providers.

Installing BGP is beyond the scope of this FAQ. Note however that you must have written permission from the administrator of the ARDC 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.

'''What is the AmprGW?'''

The AmprGW is a server run by ARDC at UCSD as part of a long-running Internet research project. It has a number of functions:

a) It provides a selective gateway between non-AMPRNet internet devices and the IPIP (mesh) AMPRNet. For this traffic, it filters at the per-host(/32) level. Each host which is to receive traffic from the Internet into AMPRNet must individually be listed in the permissions file, which is built from the AMPR.ORG DNS 'A' records. If there is no DNS A record for a tunneled amprnet destination host, the traffic is not forwarded in either direction. Therefore, if you want hosts on your subnet to be able to communicate with the Internet, you will need to have your local coordinator add them to the AMPR.ORG DNS for you.

b) It forwards traffic between Internet hosts (including those AMPRNet that are directly connected to the Internet [BGP-routed]) and IPIP tunneled AMPRNet hosts. Some "validity" filtering is applied during this process - traffic that is invalid or misconfigured will be dropped. Note: AmprGW does NOT forward between different IPIP tunneled AMPRNet hosts. That is why you cannot have just a single IPIP tunnel for all of AMPRNet. Thus the tunneled AMPRNet as a whole forms a fully-connected mesh, not a 'star' configuration.

c) AmprGW originates RIP44 broadcasts containing routing information about gateways and the AMPRNet subnets they service. The RIP44 transmissions are sent as IPIP encapsulated UDP packets for port 520 from 169.228.34.84 and sent individually to the commercial (external) address of every gateway. The packets have an inner source address of 44.0.0.1 and an inner destination of 224.0.0.9, the RIP multicast address. They are IPIP encapsulated packets, so without de-encapsulating them, the RIP is not visible to conventional routing software. Specialized software such as 'ampr-ripd' may be employed to make use of the RIP44 broadcasts, to set up AMPRNet routes.

'''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 unrecognized traffic (and this includes tunneled traffic) can be forwarded to one particular host on the LAN. That host can then be configured to recognize 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://mailman.ampr.org/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 was originally commenced by Steve VK5ASF, using material from earlier FAQs, from various contributors to the 44net mailing list, and from Brian Kantor.

AxMail-FAX

2023-06-01T16:25:11Z

W9OQI:

'''About axMail-FAX - Drafted by N1URO'''

'''SMTP based mail'''

One of the more powerful utilities we have for services on packet radio and ''Amprnet'' is the ability to send/receive SMTP based mail but also the ability to send facsimiles 100% via RF. Unlike other SMTP based email client/server configs for packet, axMail-FAX is the perfect plugin module for [https://manpages.debian.org/bullseye/uronode/uronode.8.en.html URONode.] axMail-FAX has the ability to let the end user do the following:
*Send/receive SMTP mail
*Send file attachments
*Request Read receipts
*Append to a message when accidentally attempting to send
*Request server-to-server delivery receipts
*Unkill/undelete mail before exiting the mailbox you may have flagged for deletion accidentally
*Send facsimilies

With the plugin suite, you may also allow the ability to send/receive to any stationary or mobile client. I've designed the interface to be as simple as possible including displaying your email address within the prompt system. To send an SMTP based mail just hit S at the prompt. To list your mail enter L.
To read a message R #, or if you wish to display full headers V #. You may kill multiple mail messages by using K # # # #, and check the status of them
by using L to view the status of the message(s).

'''Sending a fax'''

Sending a fax is just as simple if your host has configured a fax server gateway. There are some available if you ask the sysop, or if you are a sysop you may ask in the amprnet email list. To send a fax, it's a matter of simply following the prompts. Unlike SMTP based mail however, instead of having To: or Subject: fields a fax requires:
*Phone number
*Destination person
*Cover page
These are all provided within the ''header'' field. After typing SF to Send Fax, you enter in your header as
FirstName or First_Lastname@########### brief message about fax here. If you need to pause dialing, you may insert a comma (,) for a pause to give the remote time to answer and/or to make a menu selection if you're dialing into a PBX system such as [http://www.asterisk.org Asterisk]. After entering in your header information, you will be prompted to enter your fax message. When finished enter a period "." or "/ex" on a blank line to send. You will be asked whether or not you wish to send/cancel/continue editing, just like when sending SMTP based mail via axMail-FAX. Depending on the fax server your sysop has configured, it may have the ability to send you a confirmation of receipt of your fax job, and also confirmation of delivery of your fax when it's sent. This may come in very handy along with the SMTP server-to-server receipts if you have the need to send communications to an EOC or to another point of emergency office such as a Red Cross. Your fax will be sent with a full cover page and also your fax message.

'''Getting the software'''

If you're interested in obtaining axMail-FAX, you may download it from [https://sourceforge.net/projects/axmail/ Sourceforge]. If you're looking to set up your own fax gateway rather than use an existing one - perhaps due to geographical location, please contact me directly and I'll share the needed information with you. axMail-FAX runs on the linux operating system and is designed to interface with [http://www.hylafax.org/content/Main_Page HylaFax].

73 de '''N1URO'''

Requesting a block

2023-06-01T16:21:32Z

W9OQI:

'''ARDC/44net'''

You '''must''' request an amprnet block direct from the Portal.
First you must create your account at the [https://portal.ampr.org/ Portal].
Once you do, you must login. 

* '''You also must login every 3-6 months even if it's just to check in to keep your block active, you have been warned!'''
* '''AMPRNet is a closed network that is only accessible to licensed radio amateurs.'''

Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
row below. You will see a listing of blocks pre-allocated to the
people who coordinate for those blocks. Find the country you are
from and click on the block to the left that's associated with
the place you live in. If you're in the United States, than
you would first select 44.0.0.0/9, and then search for the state
you live in and click on that block assignment to the left.

Once you find the block associated with your QTH, you then click
on that block. When it opens you'll see a listing of pre-allocated
IP space for that block assigned by that area's coordinator. You
will also notice the following:
"If the address range you want is not within any of the subnets above,
or the region you are located in is not listed above,
you may request an allocation from the parent network by clicking here: x.x.x.x/16"
This will open up a new screen. This will bring you to the "Request Allocation" page.

Your origin's subnet will automatically be selected as a /16 subnet however
you need to enter in the actual subnet below it in which would suit your
needs. Don't be '''greedy''' request what you actually need for service
nodes. This would not include any 802.11 routers for use on ''HamWan/HamNet'' as
doing so would make you quite insecure. ISPs don't configure their routers
with publicly routable IP space for end users, why would you? To start with, we suggest
a /29 or if you feel you have a handful of devices such as a dozen Raspberry Pi
units you wish to host [http://wiki.ampr.org/wiki/URONode Nodes] with a /28
may better suit your needs.

Basic space allocation per block request and usable hosts within such as a quick
guideline would be:
*/32 - 1 usable host
*/30 - 2 usable hosts
*/29 - 6 usable hosts
*/28 - 14 usable hosts
*/27 - 30 usable hosts

Plan out your topology accordinly before you request your subnet. Many devices may share IPs for
the services you might plan to host on them. An example for a full service [http://wiki.ampr.org/wiki/URONode Node]
you may have 44.1.2.3.4 and that may bind to such things as:
*SMTP/[http://wiki.ampr.org/wiki/URONode axMail]
*[http://wiki.ampr.org/wiki/URONode Node]
*APRS
*BBS
*IMAP
*POP3
*HTTP/HTTPS
*and more!
All the above services may use a single IP on 1 host as these each may use 1 IP port each on the same IP address. As an example
if you had 4 Raspberry Pi units, and 4 PCs you were going to deploy out, that'd be 8 individual devices
in which you'd want a /28 subnet for because a /29 would leave you short 2 IPs for the host devices.

In the description field, I suggest you enter your callsign. It makes your subnet easier to locate in the portal.

Type will always be: '''End User'''

Underneath that will be 3 tick boxes:
*Radio
*Tunnel
*[http://wiki.ampr.org/wiki/Announcing_your_allocation_directly Direct]
Unless you're jumping right into the fire and intend on BGP announcing your subnet,
you can ignore the last one otherwise click on the link above to see how to do BGP with the AmprNet.
If you'll be routing IP via RF you'll obviously want to tick on ''Radio''. If you'll have IP
connectivity via your ISP you'll want to also tick on ''Tunnel''. Note: Not all ISPs allow for the
passing of our tunnel protocol however most do. If you find you can not tunnel, check with your router's
manufacturer to insure they allow for passing of IP protocol 4. You may also want to place your main amprnet
device's lan IP into your local router's DMZ so that anything coming into your IP will default
route into the device you'll designate as your amprnet routing device. (Note: Raspberry Pi
units are a great device for this and you can turn them into a Wifi hotspot to route 44/8
via 802.11a/b/g/n)

Lastly you'll want to send a note to your coordinator. You'll find this to be a good way to
open communications with your coordinator as well as helping them sort out your needs for a
subnet.

Your next step is [https://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your AmprNet Gateway.

Requesting a block

2023-06-01T16:18:03Z

W9OQI:

'''ARDC/44net'''

You '''must''' request an amprnet block direct from the Portal.
First you must create your account at the [https://portal.ampr.org/ Portal].
Once you do, you must login. 

* '''You also must login every 3-6 months even if it's just to check in to keep your block active, you have been warned!'''
* '''AMPRNet is a closed network that is only accessible to licensed radio amateurs.'''

Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
row below. You will see a listing of blocks pre-allocated to the
people who coordinate for those blocks. Find the country you are
from and click on the block to the left that's associated with
the place you live in. If you're in the United States, than
you would first select 44.0.0.0/9, and then search for the state
you live in and click on that block assignment to the left.

Once you find the block associated with your QTH, you then click
on that block. When it opens you'll see a listing of pre-allocated
IP space for that block assigned by that area's coordinator. You
will also notice the following:
"If the address range you want is not within any of the subnets above,
or the region you are located in is not listed above,
you may request an allocation from the parent network by clicking here: x.x.x.x/16"
This will open up a new screen. This will bring you to the "Request Allocation" page.

Your origin's subnet will automatically be selected as a /16 subnet however
you need to enter in the actual subnet below it in which would suit your
needs. Don't be '''greedy''' request what you actually need for service
nodes. This would not include any 802.11 routers for use on ''HamWan/HamNet'' as
doing so would make you quite insecure. ISPs don't configure their routers
with publicly routable IP space for end users, why would you? To start with, I suggest
a /29 or if you feel you have a handful of devices such as a dozen Raspberry Pi
units you wish to host [http://wiki.ampr.org/wiki/URONode Nodes] with a /28
may better suit your needs.

Basic space allocation per block request and usable hosts within such as a quick
guideline would be:
*/32 - 1 usable host
*/30 - 2 usable hosts
*/29 - 6 usable hosts
*/28 - 14 usable hosts
*/27 - 30 usable hosts

Plan out your topology accordinly before you request your subnet. Many devices may share IPs for
the services you might plan to host on them. An example for a full service [http://wiki.ampr.org/wiki/URONode Node]
you may have 44.1.2.3.4 and that may bind to such things as:
*SMTP/[http://wiki.ampr.org/wiki/URONode axMail]
*[http://wiki.ampr.org/wiki/URONode Node]
*APRS
*BBS
*IMAP
*POP3
*HTTP/HTTPS
*and more!
All the above services may use a single IP on 1 host as these each may use 1 IP port each on the same IP address. As an example
if you had 4 Raspberry Pi units, and 4 PCs you were going to deploy out, that'd be 8 individual devices
in which you'd want a /28 subnet for because a /29 would leave you short 2 IPs for the host devices.

In the description field, I suggest you enter your callsign. It makes your subnet easier to locate in the portal.

Type will always be: '''End User'''

Underneath that will be 3 tick boxes:
*Radio
*Tunnel
*[http://wiki.ampr.org/wiki/Announcing_your_allocation_directly Direct]
Unless you're jumping right into the fire and intend on BGP announcing your subnet,
you can ignore the last one otherwise click on the link above to see how to do BGP with the AmprNet.
If you'll be routing IP via RF you'll obviously want to tick on ''Radio''. If you'll have IP
connectivity via your ISP you'll want to also tick on ''Tunnel''. Note: Not all ISPs allow for the
passing of our tunnel protocol however most do. If you find you can not tunnel, check with your router's
manufacturer to insure they allow for passing of IP protocol 4. You may also want to place your main amprnet
device's lan IP into your local router's DMZ so that anything coming into your IP will default
route into the device you'll designate as your amprnet routing device. (Note: Raspberry Pi
units are a great device for this and you can turn them into a Wifi hotspot to route 44/8
via 802.11a/b/g/n)

Lastly you'll want to send a note to your coordinator. You'll find this to be a good way to
open communications with your coordinator as well as helping them sort out your needs for a
subnet.

Your next step is [https://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your AmprNet Gateway.

Requesting a block

2023-06-01T16:17:28Z

W9OQI: Deleted "drafted for" at top where it now says "ARDC/44-net

'''ARDC/44-net'''

You '''must''' request an amprnet block direct from the Portal.
First you must create your account at the [https://portal.ampr.org/ Portal].
Once you do, you must login. 

* '''You also must login every 3-6 months even if it's just to check in to keep your block active, you have been warned!'''
* '''AMPRNet is a closed network that is only accessible to licensed radio amateurs.'''

Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
row below. You will see a listing of blocks pre-allocated to the
people who coordinate for those blocks. Find the country you are
from and click on the block to the left that's associated with
the place you live in. If you're in the United States, than
you would first select 44.0.0.0/9, and then search for the state
you live in and click on that block assignment to the left.

Once you find the block associated with your QTH, you then click
on that block. When it opens you'll see a listing of pre-allocated
IP space for that block assigned by that area's coordinator. You
will also notice the following:
"If the address range you want is not within any of the subnets above,
or the region you are located in is not listed above,
you may request an allocation from the parent network by clicking here: x.x.x.x/16"
This will open up a new screen. This will bring you to the "Request Allocation" page.

Your origin's subnet will automatically be selected as a /16 subnet however
you need to enter in the actual subnet below it in which would suit your
needs. Don't be '''greedy''' request what you actually need for service
nodes. This would not include any 802.11 routers for use on ''HamWan/HamNet'' as
doing so would make you quite insecure. ISPs don't configure their routers
with publicly routable IP space for end users, why would you? To start with, I suggest
a /29 or if you feel you have a handful of devices such as a dozen Raspberry Pi
units you wish to host [http://wiki.ampr.org/wiki/URONode Nodes] with a /28
may better suit your needs.

Basic space allocation per block request and usable hosts within such as a quick
guideline would be:
*/32 - 1 usable host
*/30 - 2 usable hosts
*/29 - 6 usable hosts
*/28 - 14 usable hosts
*/27 - 30 usable hosts

Plan out your topology accordinly before you request your subnet. Many devices may share IPs for
the services you might plan to host on them. An example for a full service [http://wiki.ampr.org/wiki/URONode Node]
you may have 44.1.2.3.4 and that may bind to such things as:
*SMTP/[http://wiki.ampr.org/wiki/URONode axMail]
*[http://wiki.ampr.org/wiki/URONode Node]
*APRS
*BBS
*IMAP
*POP3
*HTTP/HTTPS
*and more!
All the above services may use a single IP on 1 host as these each may use 1 IP port each on the same IP address. As an example
if you had 4 Raspberry Pi units, and 4 PCs you were going to deploy out, that'd be 8 individual devices
in which you'd want a /28 subnet for because a /29 would leave you short 2 IPs for the host devices.

In the description field, I suggest you enter your callsign. It makes your subnet easier to locate in the portal.

Type will always be: '''End User'''

Underneath that will be 3 tick boxes:
*Radio
*Tunnel
*[http://wiki.ampr.org/wiki/Announcing_your_allocation_directly Direct]
Unless you're jumping right into the fire and intend on BGP announcing your subnet,
you can ignore the last one otherwise click on the link above to see how to do BGP with the AmprNet.
If you'll be routing IP via RF you'll obviously want to tick on ''Radio''. If you'll have IP
connectivity via your ISP you'll want to also tick on ''Tunnel''. Note: Not all ISPs allow for the
passing of our tunnel protocol however most do. If you find you can not tunnel, check with your router's
manufacturer to insure they allow for passing of IP protocol 4. You may also want to place your main amprnet
device's lan IP into your local router's DMZ so that anything coming into your IP will default
route into the device you'll designate as your amprnet routing device. (Note: Raspberry Pi
units are a great device for this and you can turn them into a Wifi hotspot to route 44/8
via 802.11a/b/g/n)

Lastly you'll want to send a note to your coordinator. You'll find this to be a good way to
open communications with your coordinator as well as helping them sort out your needs for a
subnet.

Your next step is [https://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your AmprNet Gateway.

OH7LZB VPN

2023-05-31T01:31:24Z

W9OQI: /* Mac OS X: Tunnelblick */

AMPRNet VPN is an experimental method to access the AMPRNet using a VPN from anywhere on the Internet. The VPN is openly available to any amateur radio operators who have successfully applied for an X.509 certificate from one of the following Certificate Authorities:

* [http://www.arrl.org/logbook-of-the-world ARRL Logbook of the World (LoTW)]

The Certificate Authority (CA) validates using a relatively strong method that the operator is actually licensed, and gives the operator a cryptographic certificate to prove that. Other services, such as the AMPRNet VPN can then check that the operator possesses a valid amateur radio operator certificate (and the accompanying private key), without any manual work being performed by the operators of those services. The operator can use his private key to sign LoTW log files, or any other information he wishes to communicate, and other parties trusting the CA can use the certificate to check that they have been transmitted by someone who has a private key and a certificate for a callsign from the CA.

If and when other organisations start to give out X.509 certificates, after sufficient amateur radio license validation, the AMPRNet VPN will be configured to accept those in addition to the LoTW. If you're not willing to obtain a LoTW certificate, please set up a CA for your local club or association, document the method of license validation you're using, and I'll be happy to trust your certificates.

The VPN operator (Hessu, OH7LZB) does not have time to run a CA and validate licenses manually, so please don't ask for a certificate from anywhere else than the CAs listed above. Thanks!

The AMPRNet VPN is only used to access the AMPRNet. While you're connected to the AMPRNet VPN, the VPN client will only transmit packets from you to the AMPRNet via the VPN. Packets from you to the rest of the Internet will not go via the VPN - they'll flow out from your local network connection as before. This is called a [http://en.wikipedia.org/wiki/Split_tunneling split tunnel VPN configuration].

The setup is still a bit complicated - it can be made easier and more automatic with a little additional software in a later phase.

The AMPRNet VPN is an experimental service. It might be shut down for technical or political reasons - we'll see if it's a feasible idea or not.

= Getting a certificate from LoTW =

Go through [https://lotw.arrl.org/lotw-help/getting-started/ these simple steps]. After step 4 you're ready to continue with the AMPRNet VPN.

It's going to take some time to validate, and you'll have to do some manual work (especially if you're outside the USA), but that is intentional. It significantly reduces abuse of the system, and increases its security.

= Extracting the certificate from LoTW =

LoTW uses a custom file format (.TQ*) to exchange certificates, but after the LoTW certificate process is done and the TrustedQSL software has your certificates, they can be easily copied from TrustedQSL's directories. You'll need three files: your '''user certificate''', an '''intermediate certificate''' that was used to sign it, and your '''private key'''. The only secret piece of information is the private key - you should not reveal it to anyone at any point, as they could then use services on your behalf, using your callsign.

== Windows ==

* C:\Documents and Settings\your-username\Application Data\TrustedQSL contains two directories, '''certs''' and '''keys'''.
* certs\user contains the '''user certificate'''
* certs\authorities contains an '''intermediate certificate'''
* keys\YOURCALL contains, within some XML, your '''private key'''

Make copies of those files in another directory, and work on those copies in order to avoid breaking the originals.

The user and intermediate certificates need to be concatenated to a single file named '''client.crt'''. The user certificate must be first, followed by the intermediate certificate. That can be done by an ascii editor such as Notepad (Wordpad or Word is likely to mess it up in a big way).

The private key needs to be extracted from the YOURCALL file. The file is a regular ASCII text file, and contains a block which looks something like this (just longer):

-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,0C7B5495F6A91F31

0xmWfliK/v9U88MFyYtUbteRoAkfVMK6BllcdID3pZzmdykHaPLZUjXOCUh3vFUX
1bjnYwXpLX/CxgZ6NIxQIk7jMjL3iaP5SkWzCswqi9mCO+zHxuS6PWq7YwbWNFgo
7smNcko1yTp7f/VbS4CZ5kgIF9kCgNaiqdxq+v0IcphQHRR4xjfLpBQ4ckYOi4nC
jqFR1BitwBL4K2JeE9PGUkkUBwvU4oOi9PGChuoxMXs8PwKi/dZTmSWM7kOfMiBw
-----END RSA PRIVATE KEY-----

Copy-paste that block to a separate file named '''client.key'''.

== Linux and Mac ==

* ~/.tqsl/certs/user contains the '''user certificate'''
* ~/.tqsl/certs/authorities contains an '''intermediate certificate'''
* ~/.tqsl/keys/YOURCALL contains, within some XML, your '''private key'''

The user and intermediate certificates need to be concatenated to a single file named '''client.crt'''. The user certificate must be first, followed by the intermediate certificate. That can be done by a single command:

cat ~/.tqsl/certs/user ~/.tqsl/certs/authorities > client.crt

The private key needs to be extracted from the YOURCALL file. The file is a regular ASCII text file, and contains a block which looks something like this (just longer):

-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,0C7B5495F6A91F31

0xmWfliK/v9U88MFyYtUbteRoAkfVMK6BllcdID3pZzmdykHaPLZUjXOCUh3vFUX
1bjnYwXpLX/CxgZ6NIxQIk7jMjL3iaP5SkWzCswqi9mCO+zHxuS6PWq7YwbWNFgo
7smNcko1yTp7f/VbS4CZ5kgIF9kCgNaiqdxq+v0IcphQHRR4xjfLpBQ4ckYOi4nC
jqFR1BitwBL4K2JeE9PGUkkUBwvU4oOi9PGChuoxMXs8PwKi/dZTmSWM7kOfMiBw
-----END RSA PRIVATE KEY-----

Copy-paste that block to a separate file named '''client.key'''. If you're going to open up the original private key file in a text editor, it's a good idea to make a backup copy of that file first in case of an accidental corruption of its contents.

= Configuring AMPRNet VPN =

== Windows: OpenVPN ==

# [http://openvpn.net/index.php/download/community-downloads.html Download the Windows Installer], it's free and open source.
# Run the installer to install it.
# [http://he.fi/amprnet-vpn/amprnet-vpn-win.zip Download the AMPRNet VPN configuration files for Windows]
# Open up the zip file, it contains two files: amprnet-vpn.ovpn and amprnet-vpn-ca.crt.
# In Start menu, under OpenVPN => Shortcuts you'll find an entry named '''OpenVPN configuration file directory'''. Open it, and move the two files from the zip to the configuration file directory.
# Place client.crt and client.key, which were created previously, in the configuration file directory.
# Run the '''OpenVPN GUI''' from the desktop icon or start menu. A new icon will appear in the lower right corner (two computers with red screens + a globe on the side).
# Right-click the OpenVPN toolbar icon and select '''Connect'''.

If you chose to encrypt your private key with a password (or passphrase) when initially applying for a LoTW certificate and generating the Certificate Request, OpenVPN will ask you for that password when connecting.

To rephrase: When OpenVPN says "Enter Password", the password being asked is the one you picked when you first applied for a LoTW certificate. It's not something the VPN operator knows (or should know). It's not the one you got on a postcard. Only you have ever been aware of that password (hopefully).

== Linux: OpenVPN ==

=== Ubuntu 15.10 ===

Here is steps to install AMPRNet VPN to Ubuntu 15.10 destop. Install OpenVPN plugin to network manager.
Open terminal and type

sudo apt-get install network-manager-open vpn-gnome

Then add VPN-connection information to NetworkManager

# Click network manager icon on taskbar
# Edit connections
# Add
# OpenVPN
# Create
#* Connection name: AMPRNet
#* Gateway: amprnet-vpn1.aprs.fi
#* Select proper files to User Certificate, CA certificate and Private key
#* Optionally enter private key password if you are set one
# Click Advanced
#* [x] Use custom gateway port: 1773
#* [x] Use LZO data compression
# Click OK
# Click Save
# Click Close

Now you can connect to VPN

# Click network manager icon on taskbar
# VPN connections -> AMPRNet
# Connection should be established

== Linux (Raspberry PI): OpenVPN ==

Log in to Raspberry Pi console. Install openvpn software.

sudo apt-get install openvpn

Create openvpn client configuration file with your favourite editor to /etc/openvpn/client.conf

<pre>
client
dev tun
proto udp
remote amprnet-vpn1.aprs.fi 1773
resolv-retry infinite
persist-key
persist-tun
ca amprnet-vpn-ca.crt
cert client.crt
key client.key
comp-lzo
verb 3
</pre>

Extract your client certificate and key as explained above section Extracting the certificate from LoTW. Copy your certificate files client.crt and client.key to /etc/openvpn/ . You also need amprnet-vpn-ca.crt which can be found inside this archive
http://he.fi/amprnet-vpn/amprnet-vpn-win.zip . Extract it and copy to /etc/openvpn/

Restart openvpn

service openvpn restart

All done.

== Mac OS X: Tunnelblick ==

# [https://tunnelblick.net/ Download Tunnelblick], it's free and open source, and works like a charm. It's based on OpenVPN.
# [http://he.fi/amprnet-vpn/amprnet-vpn-tblk.zip Download the AMPRNet VPN configuration for Tunnelblick], it's a zip file containing a directory with a couple files
# Double-click the downloaded zip file to extract it, you'll get a directory named '''amprnet-vpn.tblk'''
# Move the '''private key''' (in a file which was named '''client.key''' in the previous step) to that directory
# Move the certificates (in a file which was named '''client.crt''' in the previous step) to that directory
# Double-click the '''amprnet-vpn.tblk''' directory - this will launch Tunnelblick and install the VPN configuration

You should now see a "tunnel" icon in the top right corner of the screen. Click it to see a few menu items allowing you to connect and disconnect the VPN.

If you chose to encrypt your private key with a password (or passphrase) when initially applying for a LoTW certificate and generating the Certificate Request, Tunnelblick will ask you for that passphrase when connecting.

To rephrase: When Tunnelblick says "A passphrase is required to connect to amprnet-vpn", the passphrase being asked is the one you picked when you first applied for a LoTW certificate. It's not something the VPN operator knows (or should know). Only you have ever been aware of that passphrase (hopefully).

Quickstart

2023-05-02T14:56:29Z

W9OQI: Added "Click on REGISTER and complete the requested information"

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]].
Click on REGISTER and complete the requested information

# 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]].

Archive/Main Page

2023-03-22T16:10:53Z

W9OQI: Removed extra "." at the end of the top paragraph. JUst wanted to confirm I had edit abilities.

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™ or the 44Net, 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. 44Net is owned and maintained by Amateur Radio Digital Communications ([[ARDC]]).

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet_VPN|Accessing 44Net 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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

Archive/Main Page

2023-03-22T16:09:59Z

W9OQI: added "." to see if I can edit

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™ or the 44Net, 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. 44Net is owned and maintained by Amateur Radio Digital Communications ([[ARDC]])..

__NOTOC__
== Starting points ==
* [[Quickstart]] guide for getting onto the 44Net
* Basic information about 44Net and the [[ampr.org]] domain
* [[Services]] available on 44Net
* If you are looking to get an IP assignment from ARDC please read the [[Portal]] page.
* Frequently Asked Questions (FAQ) [[FAQ]]
* [[Getting started with Linux and packet radio]]
* [[Networks that use 44Net]]

== How to connect to the 44Net ==

* 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 assignment via your Internet Service Provider (ISP)]].
* Instructions for [[AMPRNet_VPN|Accessing 44Net 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 [https://www.ampr.org/terms-of-service/ Terms of Service]

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

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