Debian
ca03e69637
feat: Network/IP-Verwaltung + Mailguard-Design-Übernahme
...
Backend:
* Migration 0009_networks: network_interfaces (ethernet|vlan|bond|
bridge|wireguard, role wan|lan|dmz|mgmt|cluster, parent + vlan_id
für VLANs) + ip_addresses (interface_id FK, address+prefix, is_vip
+ vip_priority für Cluster-Failover-VIPs).
* Repos services/networkifs + services/ipaddresses + Models +
Handler /api/v1/network-interfaces (CRUD + /:id/ip-addresses)
und /api/v1/ip-addresses (CRUD).
* /api/v1/system/interfaces refactored auf Go-natives net.Interfaces()
statt `ip -j addr show` shell-out — die systemd-Sandbox blockt
AF_NETLINK auch für Go's runtime, deswegen edgeguard-api.service
RestrictAddressFamilies um AF_NETLINK ergänzt. Output-Shape
bleibt identisch (ifindex, ifname, flags[], mtu, link_type,
address, addr_info[]) — Frontend muss nicht angepasst werden.
Frontend:
* Networks-Page (/networks): "System-discovered Interfaces"
read-only Tags-Card oben, deklarierte Interfaces unten als
Tabelle mit Modal-CRUD; Type-Switch zeigt parent+vlan_id-Felder
bei type=vlan; Role-Tags farbig (wan blau, lan grün, dmz orange,
mgmt purple, cluster magenta).
* IPAddresses-Page (/ip-addresses): Tabelle pro Interface, VIP-
Toggle blendet vip_priority-Eingabe ein. Goldenes VIP-Tag in der
Liste.
* Sidebar erweitert um Networks + IP-Adressen + section-grouping.
Design 1:1 von mail-gateway/management-ui/ übernommen:
* enterprise.css verbatim (Inter-Font via Google CDN statt local
woff2), Sidebar 240px dunkler Gradient #0B1426→#101D33→#0D1829,
branding-accent #1677ff für Active-State, abgerundete Cards mit
shadow-Token, Header weiß mit subtilem backdrop-filter.
* AntD-Theme-Tokens: colorPrimary #0EA5E9, fontSize 13, fontFamily
'Inter', controlHeight 34, borderRadius 6.
* Layout-Komponenten neu strukturiert: AppLayout/Sidebar/Header
matchen mailguard-Klassen-Naming (.app-layout, .main-content,
.sidebar-section, .sidebar-menu-item.active, .header-left, …).
* Sidebar mit 4 Sektionen (Übersicht / Routing / Netzwerk / System)
+ Logo-Header + Versions-Footer.
Live-deployed auf 89.163.205.6: Networks-Endpoint listet eth0
(89.163.205.6/24, MAC bc:24:11:64:29:e8) + lo, frontend zeigt sie
als System-Tags in der Networks-Page.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com >
2026-05-09 16:08:44 +02:00
Debian
c7e5b28cf7
build: make deb pulls UI build via bun, drop stale angie comment
...
* Makefile: ui target prefers bun (with npm fallback) so make deb
end-to-end reproduces a fresh dist/. deb-amd64/deb-arm64 now
depend on ui, otherwise stale (or missing) management-ui/dist
goes into edgeguard-ui.deb.
* deploy/systemd/edgeguard-api.service: stale "angie" reference
in hardening comment removed.
Verified locally: make deb-amd64 produces three packages —
edgeguard-api_<v>_amd64.deb (6.9 MB), edgeguard-ui_<v>_all.deb
(320 KB), edgeguard_<v>_all.deb (4 KB meta). dpkg-deb -c
confirms layout matches packaging spec (binaries in /usr/bin,
units in /etc/systemd/system, UI under /usr/share/edgeguard/ui).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com >
2026-05-09 12:08:13 +02:00
Felix Netzel
0ceab4c814
chore: initial skeleton
...
- docs/architecture.md: native rewrite plan (5 services + control plane,
Active-Active cluster like nmg, Floating-IP for HTTP ingress)
- cmd/edgeguard-{api,scheduler,ctl}: minimal Gin + CLI stubs
- packaging/debian/edgeguard-{api,ui,meta}: control + maintainer scripts
- deploy/systemd/edgeguard-api.service + edgeguard-scheduler.service
with hardening defaults
- Makefile: build / cross-compile (amd64+arm64) / deb / publish targets
- scripts/install.sh + scripts/apt-repo/build-package.sh stubs
2026-05-08 18:45:41 +02:00
