public (wzorce/schematy, bez IP/portow/sciezek hostow): observer, capability-model, event-system, standards, agent-operating-procedures, service-model, action-approval-model. private: recon-multiagent, fleet-inventory, fleet-inventory-verify, kb-mail-pillar, kb-documents-pillar, topology, agent-system. deprecated (martwe stuby z 2026-04-15) — visibility private wg rozstrzygniecia 6: access-model, core-stack, legacy-services-list, networking. git mv + frontmatter, tresc nietknieta. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
| okf | type | visibility | status | updated | links | superseded_by |
|---|---|---|---|---|---|---|
| 0.1 | subsystem | private | deprecated | 2026-04-15 | kb/subsystems/fleet-inventory.md + hosts/<node>/capabilities.yaml (stub z 2026-04-15, sprzed floty) |
Networking
Description
This page documents the current known network position and port forwarding for the homelab.
Current configuration
- The homelab is behind NAT.
- Port forwarding is configured as follows:
- External ports
80-81forward to internal ports4480-4481 - External port
443forwards to internal port4443
- External ports
Known facts
- NAT is present between the public internet and the homelab.
- Public HTTP/HTTPS traffic reaches the homelab through forwarded ports.
- External ports
80,81, and443are known to be forwarded. - Internal ports
4480,4481, and4443are known forwarding targets.
Unknown / needs clarification
- Router or firewall model.
- Whether the WAN IP is static, dynamic, or CGNAT.
- Internal IP address of the Raspberry Pi 5.
- Whether the Raspberry Pi 5 uses DHCP or static addressing.
- Exact mapping for external ports
80-81to internal ports4480-4481:- Whether
80maps to4480. - Whether
81maps to4481.
- Whether
- Protocols forwarded for each port: TCP, UDP, or both.
- Whether any other ports are forwarded.
- LAN subnet and gateway.
- DNS provider and DNS records.
- IPv6 availability or absence.
- Firewall rules on the Raspberry Pi 5.