Web Fetch Fake-IP Workaround

Legacy workaround for web_fetch fake-ip failures on older npm-global OpenClaw installs. Use when web_fetch is blocked under Clash, Mihomo, or Surge fake-ip mode and the OpenClaw version does not yet support the openclaw.json ssrfPolicy fix. For OpenClaw v2026.4.10 and later, prefer configuration instead of patching.

xingxing@xing-xing-coder

Install

openclaw skills install @xing-xing-coder/web-fetch-fakeip

web_fetch Fake-IP Workaround

Apply a small, reversible patch so web_fetch works under TUN + fake-ip environments that resolve through 198.18.0.0/15.

Best fit

Use this skill when:

OpenClaw was installed with npm install -g openclaw
You use Clash, Mihomo, or Surge with fake-ip enabled
web_fetch fails with private/internal/special-use IP blocking
Your OpenClaw version is older than v2026.4.10
You need a legacy workaround because the config-based fix is unavailable

Not for

OpenClaw v2026.4.10 or later, use openclaw.json instead
Source-built OpenClaw
Certificate problems
Proxy rule or port mistakes
Missing proxy environment variables

What changes

The script finds the bundled web_fetch call to fetchWithWebToolsNetworkGuard({...}) and inserts:

policy: { allowRfc2544BenchmarkRange: true }, // openclaw-fakeip-patch

This only opens the RFC2544 benchmark range used by common fake-ip setups.

Workflow

bash

bash patch-openclaw-global-fakeip.sh status
bash patch-openclaw-global-fakeip.sh inspect
bash patch-openclaw-global-fakeip.sh apply
openclaw gateway restart

Then retry the failing web_fetch request.

Revert