This page is the policy reference index for 44Net participation and operations.
* Ask for clarification in [[Community|Community and mailing lists]] before policy-sensitive actions.
...
1 KB (171 words) - 18:52, 30 April 2026
...ger “current,” because it still helps with context: older designs, earlier policy language, implementation history, and things that shaped what exists today.
: Expected to match today’s policy or implementation. Applies to actively maintained procedures and info.
...
3 KB (474 words) - 18:52, 30 April 2026
...experienced practitioners from the amateur radio, networking, and Internet policy communities.
* Reviewing and recommending policy related to 44Net
...
3 KB (493 words) - 18:52, 30 April 2026
...tional hygiene (IRR/RPKI filtering, route servers, and clear participation policy).
== Policy ==
...
3 KB (352 words) - 18:52, 30 April 2026
* Links to authoritative policy text.
[[Category:Policy]]
...
2 KB (197 words) - 18:52, 30 April 2026
...the 44Net address space and program. The Board establishes organizational policy, approves major initiatives, and ensures that ARDC operates in accordance w
..., and administrative responsibility for 44Net, including approval of major policy directions, program priorities, and organizational strategy.
...
2 KB (270 words) - 18:52, 30 April 2026
=== Use policy-based routing to send only 44Net traffic over the tunnel===
...ault behavior is to modify routing automatically. Disabling this and using policy routing opens up more options for control.
...
4 KB (624 words) - 18:51, 30 April 2026
=== Policy ===
...
4 KB (594 words) - 18:52, 30 April 2026
* Prerequisites such as routing policy and edge design.
...
1 KB (162 words) - 18:52, 30 April 2026
* Decision domains: policy, operations, and documentation.
...
1 KB (151 words) - 18:52, 30 April 2026
...announce their allocated prefixes using BGP and maintain their own routing policy and operational practices. This model is suited to research networks, {{Ter
| Operating routers, BGP edge, and routing policy
...
4 KB (489 words) - 18:52, 30 April 2026
...urce IP address or destination IP address. For example, you could create a policy that sends all traffic through the tunnel, or only traffic destined for 44N
To route traffic from this subnet through the tunnel, create a policy-based route that matches the new subnet as the source and the VPN client as
...
7 KB (1,045 words) - 18:52, 30 April 2026
== Setting up source address routing policy ==
Let's define source address routing policy that will make sure only AMPRNet hosts are routed to the tunnel
...
10 KB (1,498 words) - 18:52, 30 April 2026
* Prerequisites: ASN, policy ownership, and upstream coordination.
...
2 KB (263 words) - 18:52, 30 April 2026
This section should describe activity, not policy.
...
2 KB (291 words) - 18:52, 30 April 2026
...r 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 need
...
19 KB (2,777 words) - 18:52, 30 April 2026
* [[FAQ]] if you want answers to common operational and policy questions
...
3 KB (395 words) - 18:52, 30 April 2026
Usually it holds 2 rules, with a default policy of 'drop':
...RD (or something suggestive) <span style="color: red;">with a default drop policy</span>.
...
9 KB (1,563 words) - 18:52, 30 April 2026
...nterfaces in their own [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] scenario; and places all local AMPRNet allocations in the ma
''AMPRNet Policy Routes''
...
10 KB (1,632 words) - 18:52, 30 April 2026
...nterfaces in their own [https://en.wikipedia.org/wiki/Policy-based_routing policy-based routing] scenario; and places all local AMPRNet allocations in the ma
''AMPRNet Policy Routes''
...
10 KB (1,631 words) - 18:52, 30 April 2026
