fix: connectivity panel rearrangement. LXD VM for repeatable tests.

This commit is contained in:
slawek committed 2026-11-22 15:59:40 +01:00
1 parent 85a1ffa21f
commit da889b4865
15 files changed
+363 -47

No files matched your search

+5 -3
View File
@@ -1159,7 +1159,7 @@ lme /etc/linux-manager/linux-manager.json ~/notes.txt
| Key | Content |
| --- | --- |
| `configuration` | `linux-manager.json` with the defaults applied, without its secret options at any level (`psk`, `database`, and any option named like a secret, password, token or key) |
| `network` | The external and internal interface, their addresses, the internal gateway, `local.cidrs`, `site_to_site`: each connection with `name`, `local_identity`, `remote_identity`, `local_cidrs` and `remote_cidrs`, and the IPv4 routes as `ip -j -4 route` prints them |
| `network` | The external and internal interface, their addresses, the internal gateway, `local.cidrs`, `site_to_site`: each connection with `name`, `local_identity`, `remote_identity`, `local_cidrs` and `remote_cidrs`, `interfaces`: each interface but loopback with `name`, `state`, `mac`, `ipv4`, its IPv4 addresses, and `ipv6`, its global IPv6 addresses, as `address/prefix`, `null` when `ip` fails, and the IPv4 routes as `ip -j -4 route` prints them |
| `ipsec` | `connections` and `sas`: one object per connection and per IKE SA, read from `swanctl --list-conns --pretty` and `swanctl --list-sas --pretty`, with the connection's name under `name` and swanctl's keys and string values |
| `wireguard` | The public key and port of `wg0`, and each peer's public key, endpoint, allowed IPs, handshake age and traffic; no private or preshared key |
| `docker` | `docker.exposed_ports` and the rules of the `LINUX-MANAGER-DOCKER` chain |
@@ -2202,8 +2202,10 @@ name, left of Sign out, opens the account page, and the terminal icon left of it
remote identity and the subnets it resolved, and how long the connection has been up, and their
IPsec security associations, child SAs, connections and connection children, from the server's
`/config`. The other IPsec connections, IKEv2 access, are on the IKEv2 tab of Remote Access.
- **Connectivity**, Network tab: the external and the internal interface with their addresses, the
internal gateway and the local CIDRs, and the IPv4 routes, from the server's `/config`; the panels
- **Connectivity**, Network tab: the Interfaces panel lists every interface but loopback by name
with its type, `external` when it holds an IPv4 default route and `internal` otherwise, its
state, IPv4 and IPv6 addresses and MAC address; the Router panel, shown while the router is on,
the internal gateway and the local CIDRs; and the IPv4 routes, from the server's `/config`; the panels
fold, hide, move and change width, and the browser keeps their layout.
- **Remote Access** (`/remote-access-manager`): a tab each for IKEv2,
OpenVPN and WireGuard access, from the server's `/remote-access` and `/status/full`: the