qwen-code PR lets Local Control accept VPN and public-range enterprise LAN addresses
pomelo-nwu · ghdev · 2026-10-14
PR #14140 in QwenLM/qwen-code fixes Local Control being completely unusable in some enterprise environments: when a host's only non-loopback IPv4 is outside RFC 1918/3927 (some corporate intranets number LANs from public ranges) or sits on a VPN/tunnel interface (phone and laptop on the same corporate VPN), qwen serve --local-control fails with "No private IPv4 address is available", and --local-control-address couldn't help since it only disambiguated among already-filtered candidates.
The fix: an explicitly passed address is treated as operator intent—Local Control accepts any non-internal, non-loopback IPv4 the host actually has. Automatic advertisement stays RFC 1918/3927-only; out-of-private-space picks log a loud warning. The LAN listener still enforces the pairing token (401 without it).
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23