Internet Requirements - Revision history

KI5QKX: mw push

2026-09-30T22:33:04Z

mw push

← Older revision		Revision as of 22:33, 30 September 2026
Line 5:		Line 5:
	== 44Net Connect ==		== 44Net Connect ==

	44Net Connect is the most flexible way to get 44Net onto your device. It works over pretty much any Internet connection that allows outbound UDP traffic, and it can handle changes in your IP address or network seamlessly, which is helpful for devices that roam or change networks.		44Net Connect is the most flexible way to get 44Net onto your device. It works over pretty much any Internet connection that allows outbound UDP traffic, and it can handle changes in your IP address or network seamlessly, which is helpful for devices that roam or change networks.

	It can work over home broadband, cellular, satellite, and public Wi-Fi. It can also work behind NAT and CGNAT, and even on some connections that block VPN traffic.		It can work over home broadband, cellular, satellite, and public Wi-Fi. It can also work behind NAT and CGNAT, and even on some connections that block VPN traffic.
Line 19:		Line 19:
	==== Inbound access ====		==== Inbound access ====

	For IPIP Mesh to work, your Internet connection and all intermediate devices, including ISP-provided equipment, must allow:		For IPIP Mesh to work, your Internet connection and all intermediate devices, including ISP-provided equipment, must allow IP-in-IP traffic (IP protocol 4).
	* IP-in-IP traffic (~~ipencap~~ protocol 4)
	* RIPv2 packets ~~arriving~~ on UDP port 520		If you use RIP route updates, your gateway must accept the RIPv2 packets on UDP port 520 inside the IPIP tunnel. This does not require opening UDP port 520 on your public Internet connection. See [[IPIP Mesh/Firewalls\|Mesh firewall guidance]].

	==== Public IP address ====		==== Public IP address ====
Line 39:		Line 39:
	Announcing via BGP is the most advanced way to get 44Net onto your network.		Announcing via BGP is the most advanced way to get 44Net onto your network.

	For running a router on your premises, you will need a connection to a provider willing to handle your subnet.		For running a router on your premises, you will need a connection to a provider willing to handle your subnet.

	To announce your subnet from a cloud provider, you will need a provider that supports BYOIP (Bring Your Own IP) and accepts 44Net subnets. In particular, the provider must allow you to announce your subnet [[RPKI and ROAs on 44Net\|without RPKI ROAs.]]		To announce your subnet from a cloud provider, you will need a provider that supports BYOIP (Bring Your Own IP) and accepts 44Net subnets. In particular, the provider must allow you to announce your subnet [[RPKI and ROAs on 44Net\|without RPKI ROAs.]]
Line 47:		Line 47:
	== Speed and quality ==		== Speed and quality ==

	The speed and quality of service required depends on the intended use of your connection. The WireGuard protocol used by 44Net Connect is designed to be efficient and resilient, and the link itself usually tolerates variable connection quality. The application running over the link may be ~~more~~ more sensitive, however, including things like streaming, voice, remote desktop, or video.		The speed and quality of service required depends on the intended use of your connection. The WireGuard protocol used by 44Net Connect is designed to be efficient and resilient, and the link itself usually tolerates variable connection quality. The application running over the link may be more sensitive, however, including things like streaming, voice, remote desktop, or video.

	For example, a typical VOIP call generally needs only about 64kbps of bandwidth, so high speeds are not usually necessary for voice applications like IRLP, Allstar, or DMR. LTE or Starlink standby mode may be more than sufficient. Voice applications are sometimes sensitive to packet loss, jitter, and latency, however, so an unstable or marginal connection may work fine or it might not.		For example, a typical VOIP call generally needs only about 64kbps of bandwidth, so high speeds are not usually necessary for voice applications like IRLP, Allstar, or DMR. LTE or Starlink standby mode may be more than sufficient. Voice applications are sometimes sensitive to packet loss, jitter, and latency, however, so an unstable or marginal connection may work fine or it might not.
Line 62:		Line 62:

	=== Am I on CGNAT? ===		=== Am I on CGNAT? ===
	You can check whether you might be behind CGNAT using an online tool like [https://portwarp.com/tools/cgnat-detector PortWarp CGNAT Detector]. If you are behind CGNAT, you will not be able to participate in the IPIP Mesh or announce your own subnet via BGP, so ~~it'll~~ be 44Net Connect or nothing for you.		You can check whether you might be behind CGNAT using an online tool like [https://portwarp.com/tools/cgnat-detector PortWarp CGNAT Detector]. If you are behind CGNAT, you will not be able to participate in the IPIP Mesh or announce your own subnet via BGP, so it’ll be 44Net Connect or nothing for you.

KI5QKX: Organize IPIP Mesh documentation and navigation

2026-09-29T19:09:30Z

Organize IPIP Mesh documentation and navigation

← Older revision		Revision as of 19:09, 29 September 2026
Line 33:		Line 33:
	If your public IP address is not static, you will need a dynamic DNS service to keep your hostname updated. The Portal does not currently provide this.		If your public IP address is not static, you will need a dynamic DNS service to keep your hostname updated. The Portal does not currently provide this.

	See [[DNS\|DNS setup]] and [[~~Gateway~~\|gateway setup guides]].		See [[DNS\|DNS setup]] and [[IPIP Mesh/Gateways\|gateway setup guides]].

	== BGP-announced subnets ==		== BGP-announced subnets ==

KI5QKX: mw push

2026-09-28T23:53:18Z

mw push

← Older revision		Revision as of 23:53, 28 September 2026
Line 1:		Line 1:

	{{DISPLAYTITLE:Internet Requirements}}		{{DISPLAYTITLE:Internet Requirements}}

KI5QKX: mw push

2026-09-28T23:49:49Z

mw push

New page

{{DISPLAYTITLE:Internet Requirements}}

44Net does not provide Internet service, so you will need your own Internet connection. This page describes the requirements for your Internet connection to support 44Net services.

== 44Net Connect ==

44Net Connect is the most flexible way to get 44Net onto your device. It works over pretty much any Internet connection that allows outbound UDP traffic, and it can handle changes in your IP address or network seamlessly, which is helpful for devices that roam or change networks.

It can work over home broadband, cellular, satellite, and public Wi-Fi. It can also work behind NAT and CGNAT, and even on some connections that block VPN traffic.

See [[44Net Connect/Quick Start|Connect Quick Start]].

== IPIP Mesh ==

The IPIP Mesh is a long-running project to interconnect 44Net subnets over the Internet using a mesh of IP-in-IP tunnels. Its design assumes an Internet that is largely open and unrestricted, which is less the case today than it was when the project started. It is still possible to participate in the IPIP Mesh, but you may run into obstacles with some ISPs.

=== Requirements ===

==== Inbound access ====

For IPIP Mesh to work, your Internet connection and all intermediate devices, including ISP-provided equipment, must allow:
* IP-in-IP traffic (ipencap protocol 4)
* RIPv2 packets arriving on UDP port 520

==== Public IP address ====

Your public IP address does not need to be static, but it must be reachable from the Internet. If your ISP uses CGNAT, you almost certainly cannot participate in the IPIP Mesh.

==== DNS A record ====

You must configure a DNS hostname that resolves to your public IP address. This hostname is periodically resolved by the Portal to update the IPIP tunnel endpoints broadcast from the gateway via RIP. You can use your own domain name, a free dynamic DNS service, or a free <callsign>.ampr.org record you set up in the Portal.

If your public IP address is not static, you will need a dynamic DNS service to keep your hostname updated. The Portal does not currently provide this.

See [[DNS|DNS setup]] and [[Gateway|gateway setup guides]].

== BGP-announced subnets ==

Announcing via BGP is the most advanced way to get 44Net onto your network.

For running a router on your premises, you will need a connection to a provider willing to handle your subnet.

To announce your subnet from a cloud provider, you will need a provider that supports BYOIP (Bring Your Own IP) and accepts 44Net subnets. In particular, the provider must allow you to announce your subnet [[RPKI and ROAs on 44Net|without RPKI ROAs.]]

See [[BGP/Quick Start|BGP Quick Start]] and [[Guide for ISPs]].

== Speed and quality ==

The speed and quality of service required depends on the intended use of your connection. The WireGuard protocol used by 44Net Connect is designed to be efficient and resilient, and the link itself usually tolerates variable connection quality. The application running over the link may be more more sensitive, however, including things like streaming, voice, remote desktop, or video.

For example, a typical VOIP call generally needs only about 64kbps of bandwidth, so high speeds are not usually necessary for voice applications like IRLP, Allstar, or DMR. LTE or Starlink standby mode may be more than sufficient. Voice applications are sometimes sensitive to packet loss, jitter, and latency, however, so an unstable or marginal connection may work fine or it might not.

Remote operation via remote desktop or a lightweight web UI might only sip bandwidth as well, even streaming audio. Voice QSOs could be fine as far as bandwidth and latency are concerned, but time-sensitive applications like FT8 might not be viable.

== Things to check before you start ==

=== Speed, latency, jitter, and packet loss ===
Testing these may uncover problems that affect your application. You can check these using a speed test like [https://testmy.net/ TestMy] or [https://www.speedtest.net/ Speedtest]. Check both download and upload speeds.

=== Connection stability ===
Less of an issue on typical Internet connections, but a remote site might be on a less stable connection. Many routers record connection quality, which can be useful for estimating link stability. UniFi, for example, has a chart showing packet loss and latency over time.

=== Am I on CGNAT? ===
You can check whether you might be behind CGNAT using an online tool like [https://portwarp.com/tools/cgnat-detector PortWarp CGNAT Detector]. If you are behind CGNAT, you will not be able to participate in the IPIP Mesh or announce your own subnet via BGP, so it'll be 44Net Connect or nothing for you.

[[Category:Reference]]
[[Category:Getting Started]]