relaying/ RPC
This commit is contained in:
@@ -120,6 +120,10 @@ $env:HF_HOME = "D:\DEV\models"
|
||||
--port 8005
|
||||
```
|
||||
|
||||
The example above starts the Windows node as the second half of a split Qwen
|
||||
model. To run the full model on Windows instead, omit `--shard-start` and
|
||||
`--shard-end`.
|
||||
|
||||
`--host 0.0.0.0` binds the node to all Windows interfaces. `--advertise-host`
|
||||
is what the tracker gives to other nodes, so it must be the Windows LAN IP that
|
||||
the tracker and peer nodes can actually reach.
|
||||
@@ -139,10 +143,10 @@ lines like:
|
||||
curl http://192.168.0.42:8005/v1/health
|
||||
```
|
||||
|
||||
If that endpoint returns 404, that is okay: it still proves the TCP connection
|
||||
reached the node process. If it times out or connection-refuses, check the
|
||||
Windows Firewall rule, `--host 0.0.0.0`, the selected LAN IP, and that the node is
|
||||
still running.
|
||||
If that endpoint returns 404 or 501, that is okay: it still proves the TCP
|
||||
connection reached the node process. If it times out or connection-refuses, check
|
||||
the Windows Firewall rule, `--host 0.0.0.0`, the selected LAN IP, and that the
|
||||
node is still running.
|
||||
|
||||
### Public tracker + WSS relay
|
||||
|
||||
|
||||
Reference in New Issue
Block a user