Skip to content

UPSTREAM PR #18054: server: Fix router proxying to child processes when --host is specified#574

Open
loci-dev wants to merge 1 commit intomainfrom
upstream-PR18054-branch_wbtek-fix/router-host-binding
Open

UPSTREAM PR #18054: server: Fix router proxying to child processes when --host is specified#574
loci-dev wants to merge 1 commit intomainfrom
upstream-PR18054-branch_wbtek-fix/router-host-binding

Conversation

@loci-dev
Copy link
Copy Markdown

Mirrored from ggml-org/llama.cpp#18054

llama-server --host now works for:

  • specific external facing addresses both locally and externally (192.168.3.14)
  • localhost (127.0.0.1)
  • all interfaces (0.0.0.0)

It worked with 127.0.0.1 and 0.0.0.0 before, but when a specific external facing address was specified it:

  • served the WebUI correctly on the specified ip address
  • switch to 127.0.0.1 for child when model was loaded

@loci-review
Copy link
Copy Markdown

loci-review bot commented Dec 15, 2025

Explore the complete analysis inside the Version Insights

Based on the analysis results, I can now provide the summary:


Performance Analysis Summary

Condition 1 Applied: No meaningful changes detected

The comparison between version 55c2244c-43d3-4f65-8b57-f5d9ba63cda9 and baseline 24dfe6da-2760-403d-a4ec-e8afe1ec7d4f shows no measurable performance differences. Power consumption across all binaries remains unchanged, with negligible variations under 0.001% in libllama.so, llama-cvector-generator, llama-run, and llama-tts. No function-level performance regressions detected. Inference throughput and tokens per second remain unaffected.

@loci-dev loci-dev force-pushed the main branch 27 times, most recently from 02b3f55 to ba4079a Compare December 17, 2025 21:09
@loci-dev loci-dev force-pushed the main branch 30 times, most recently from 37b9287 to eebd4bb Compare December 23, 2025 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant