AXIP / 44Net Links

Updated July 15, 2026

At a glance

node.w5aww.ampr.org:10093/UDP

Numeric form:

44.27.29.34:10093/UDP

Prefer the hostname so peers survive future address renumbering.

Why AXIP here?

The home internet path is Starlink (CGNAT). A routed 44net address via WireGuard lets other AMPRNet nodes reach LinBPQ for AXIP without depending on ordinary inbound port-forward from the consumer WAN. Design notes (redacted): Network design (44net).

LinBPQ MAP entry

Add to the CONFIG section of your BPQAXIP port:

MAP W5AWW-7 node.w5aww.ampr.org UDP 10093 B

Alternate:

MAP W5AWW-7 44.27.29.34 UDP 10093 B

Your firewall must allow outbound UDP to that endpoint.

Requesting a reciprocal link

Email [email protected] (W5AWW) with:

Node callsign
AXIP hostname or 44net address
UDP port
Whether your endpoint accepts inbound UDP
Whether the link is for testing or long-term use

Example reciprocal MAP (on W5AWW-7):

MAP YOURCALL-7 yournode.example.ampr.org UDP 10093 B

Operators behind CGNAT

CGNAT alone does not block AXIP if both ends have working routed 44net (or another agreed path). Options include:

• 44net WireGuard (or similar AMPRNet VPN)
• LinBPQ TCP Master/Slave
• An intermediate AXIP relay
• A private VPN between stations

If you cannot accept inbound UDP, say so when you write.

Testing interests

• Basic AXIP connectivity
• NET/ROM links and route quality
• BBS forwarding
• CONVerse / chat
• Long-term stability (including Starlink + WireGuard behavior)
• Future AREDN / bridging experiments

Public checks

dig +short node.w5aww.ampr.org

Expected:

44.27.29.34

Contact

I welcome AXIP test links, BBS forwarding discussions, and longer-term packet connections. Use the email above for link requests and coordination.

73 de W5AWW