open-webui: reach the LLM via the host LAN IP, not the bridge gateway

The bridge gateway (10.89.3.1) lives in the rootless netns; llama-server
runs in the host netns, so the gateway refuses. 192.168.0.143:52625
reaches it through the rootless NAT (verified from the container).
Same LAN-IP pattern the doc already prescribes for the Dankserver
backend.

dankclaw/open-webui/quadlet/open-webui.container

@@ -6,7 +6,7 @@
 # Chat UI for the LLM fleet. It runs on the CPU image (dankclaw is CPU-only, so
 # the :cuda image would waste a large pull for a GPU it cannot use) and points
 # its OpenAI connection at the live vLLM backend on this host via the bridge
-# gateway (10.89.3.1:52625, model frank-default-large). It publishes 3005
+# gateway (192.168.0.143:52625, model frank-default-large). It publishes 3005
 # (3000 is Gitea's HTTP port). Data persists under
 # /home/dank/Containers/open-webui/data. See docs/Dankclaw/OpenWebUI.md.
 #
@@ -15,8 +15,10 @@
 # interface: a zombie that accepted TCP and reset every request, and chat
 # served empty responses for ~2 days with no error anywhere. It now runs on a
 # pinned bridge network (open-webui.network), which has no per-container
-# helper to die. The healthcheck probes /health (app liveness) and requires a
-# non-loopback interface (network liveness).
+# helper to die. The LLM is reached via the host LAN IP (192.168.0.143):
+# the bridge gateway lives in the rootless netns, not the host netns where
+# llama-server runs. The healthcheck probes /health (app liveness) and
+# requires a non-loopback interface (network liveness).
 
 [Unit]
 Description=open-webui chat UI container
@@ -27,7 +29,7 @@ ContainerName=open-webui
 Network=open-webui.network
 Image=ghcr.io/open-webui/open-webui:main
 PublishPort=3005:8080
-Environment=OPENAI_API_BASE_URL=http://10.89.3.1:52625
+Environment=OPENAI_API_BASE_URL=http://192.168.0.143:52625
 Environment=ANONYMIZED_TELEMETRY=False
 Environment=DO_NOT_TRACK=True
 Volume=/home/dank/Containers/open-webui/data:/app/backend/data