starlink: dish route + status card on the Van Router page
The Starlink RTL8153 gets a declarative NM profile in 50-van-wan.yaml (replaces the auto 'Wired connection 1') with a 192.168.100.1/32 link route, so the dish's management address stays reachable from the router and — via the existing !br0 masquerade — from the van LAN, regardless of which WAN holds the default route. New Cockpit "Starlink" card queries the dish's gRPC API (:9200, get_status via grpcurl — not packaged in apt, deploy.sh warns when missing) inside the existing single batched spawn: online/obstructed/outage pill, alerts, uptime, sw version, PoP latency, down/up throughput, obstruction %. Sentinels distinguish adapter-absent / no-grpcurl / dish-unreachable. Gotcha captured while cutting over: a WAN profile without ipv4.route-metric makes NM re-assert its DHCP default (metric ~101) against van-failover's enforce_route pruning every cycle; the profile metric must match (failover's set_profile_metric does this on health transitions). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
2da97d26f4
commit
751facd511
@@ -35,6 +35,11 @@
|
||||
<div id="failover"></div>
|
||||
</div>
|
||||
|
||||
<div class="card">
|
||||
<h3>Starlink</h3>
|
||||
<div id="starlink"></div>
|
||||
</div>
|
||||
|
||||
<div class="card">
|
||||
<h3>WAN / Uplinks</h3>
|
||||
<table>
|
||||
|
||||
Reference in New Issue
Block a user