NgTech-LTD/gns3-server
2
0
Fork 0
mirror of https://github.com/GNS3/gns3-server.git synced 2026-09-01 23:55:15 +03:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove misleading Controller Hostname Unreachable section

Browse Source 
This section was misleading - the actual root cause is host=0.0.0.0
causing controller to register as 127.0.0.1, not hostname resolution.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
YueGuobin 2026-04-25 15:55:37 +08:00
parent e88b12086a
commit d81a7410e2
No known key found for this signature in database
1 changed files with 0 additions and 19 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
docs/features/compute-controller-setup.md
View File

@ -112,22 +112,3 @@ Cannot get an IP address on same subnet: No common subnet for compute X (control
4. Verify both machines are on the same network and can ping each other
5. Check firewall rules allow TCP/UDP communication on required ports
### Controller Hostname Unreachable
If the controller machine uses a hostname defined in `/etc/hosts` (e.g., `guobin.localhost`), and the compute node reports:
```
Cannot get an IP address on same subnet: No common subnet for compute X (controller) and Y
```
1. **Symptom**: The controller's hostname resolves to an IP that is unreachable from the compute node
2. **Root Cause**: The `/etc/hosts` entry for the controller's hostname points to a stale or unreachable IP address
3. **Solution**:
- Ensure the controller's hostname in `/etc/hosts` resolves to the correct, reachable IP address
- Example (correct):
```
192.168.1.104 guobin.localhost
```
- If the machine's IP is dynamic (DHCP), consider:
- Setting a DHCP static lease on the router for a fixed IP
- Using mDNS (`.local` domain) if supported by the compute node