Supported Protocols
The Nekotopia mesh operates on WireGuard, a modern Layer 3 VPN transporting IPv4 and IPv6. For members requiring legacy protocol support, we provide Layer 2 overlay capability via VXLAN encapsulation.
Native Transport (Layer 3)
| Protocol | Status | Notes |
|---|---|---|
| IPv4 | ✅ Native | Full support, default transport |
| IPv6 | ✅ Native | Full support, dual-stack available on request |
Layer 2 Overlay (VXLAN)
By establishing a VXLAN tunnel over the WireGuard mesh, members gain a virtual Ethernet segment spanning all participants. This enables transport of any protocol that runs over Ethernet, including legacy and vintage networking stacks.
| Protocol | Status | Use Case | Notes |
|---|---|---|---|
| IPX/SPX | ✅ Supported | Novell NetWare, DOS/Windows 9x gaming | Frame type 802.2 or Ethernet II. Ideal for classic multiplayer: DOOM, Duke Nukem 3D, Descent, Warcraft II |
| AppleTalk Phase II | ✅ Supported | Classic Macintosh networking | EtherTalk encapsulation. Supports file sharing (AFP), printing (PAP), and zone discovery |
| NetBEUI | ✅ Supported | Windows for Workgroups, LAN Manager | Non-routable, broadcast-based. Works within single VXLAN segment |
| DECnet Phase IV | ✅ Supported | VAX/VMS, PDP-11, Ultrix | Runs natively over Ethernet. Area routing possible within overlay |
| LAT | ✅ Supported | DEC terminal services | Latency-sensitive; performance depends on baseline RTT across mesh |
| NetBIOS over LLC | ✅ Supported | OS/2, early Windows networking | Raw 802.2 LLC frames; distinct from NetBIOS over TCP/IP |
| Banyan VINES | ⚠️ Untested | Banyan network services | Should work over Ethernet encapsulation; no active members to verify |
| XNS | ⚠️ Untested | Xerox Network Systems | Predecessor to IPX; theoretically supported |
Architecture
┌─────────────────────────────────────────────────────────────────┐ │ Member Endpoint │ ├─────────────────────────────────────────────────────────────────┤ │ Vintage Host (IPX/AppleTalk/NetBEUI) │ │ │ │ │ ▼ │ │ ┌─────────────┐ │ │ │ Bridge/TAP │ ← Ethernet frames │ │ └──────┬──────┘ │ │ ▼ │ │ ┌─────────────┐ │ │ │ VXLAN │ ← Encapsulates L2 in UDP │ │ └──────┬──────┘ │ │ ▼ │ │ ┌─────────────┐ │ │ │ WireGuard │ ← Encrypted IP transport │ │ └──────┬──────┘ │ │ ▼ │ │ Internet │ └─────────────────────────────────────────────────────────────────┘
Considerations
MTU
VXLAN adds 50 bytes of overhead. Combined with WireGuard's 60-80 byte overhead, effective payload MTU is approximately 1370 bytes assuming standard 1500-byte internet path. Vintage systems rarely approach this limit, but fragmentation may occur with large NetWare packets.
Broadcast Domains
Legacy protocols are chatty. IPX SAP advertisements, AppleTalk NBP lookups, and NetBEUI name queries all broadcast. Each VXLAN segment forms a single broadcast domain—keep segments small or expect background traffic.
Latency Sensitivity
Some protocols (notably LAT and certain real-time IPX games) assume LAN-grade latency. Performance over a geographically distributed mesh will vary. The network equity tools described elsewhere can normalize latency at the cost of imposing artificial delay on all participants.
Routing
IPX and DECnet support routing across multiple network segments. AppleTalk Phase II supports zone routing. If your deployment requires multi-segment topologies, contact the network team to discuss architecture.
Requesting Access
Layer 2 overlay access is available to members on request. Provide:
- Protocol(s) required
- Intended use case
- Estimated number of hosts
- Whether you require a dedicated segment or will join the shared vintage LAN