Artikel ini belum diterjemahkan. Isi berikut berbahasa Inggris. Buka versi asli bahasa Inggris.
This guest-network tutorial is for an administrator with sudo access and working console recovery. It does not grant public IPv4, NAT64, a proxy, or any additional network entitlement. Provider endpoints change. Test the actual hostname instead of relying on a historical IPv6 compatibility table.
Check the failure boundary
Run these commands inside your guest, not on the provider host:
# Use the actual endpoint that failed.
getent ahosts github.com
curl -6 --connect-timeout 10 --max-time 20 --head https://github.com
curl -6 --connect-timeout 10 --max-time 20 --head https://registry-1.docker.io/v2/A DNS failure, missing IPv6 route, timeout, TLS error, and HTTP authentication error require different remedies.
An HTTP 401 from a registry can show that its HTTPS endpoint answered. It does not indicate a successful image pull.
Check image layers, registry authentication, redirects, and package-download hosts separately.
Keep TLS verification enabled. Do not use curl -k, disable Git certificate checks, or publish verbose output containing credentials.
Solution 1: GitHub via IPv6 proxy
Prefer native connectivity or an operator-approved route. A third-party proxy introduces another operator and availability boundary.
Do not copy historical hard-coded addresses into /etc/hosts. They can become stale and override healthy public DNS.
If an approved proxy is required:
- Obtain its current configuration and privacy policy from its operator.
- Record and back up any existing guest proxy or hosts-file settings.
- Configure only the required destination according to that operator’s instructions.
- Test HTTPS with certificate verification enabled before sending credentials.
- Test
git ls-remote https://github.com/NousResearch/hermes-agent.gitwithout a private token. - Restore the previous settings if the test fails or the proxy is no longer required.
HTTPS reachability does not establish SSH transport support. Use the repository’s authorized HTTPS remote when appropriate. Never send a personal access token to an untrusted substitute hostname or bypass a certificate error. Ask your network administrator about a trusted proxy rather than cycling through unknown public relays.
Solution 2: Docker Hub via IPv6 endpoint
Use the standard Docker Hub image names first:
sudo docker pull hello-world
sudo docker run --rm hello-worldThe historical registry.ipv6.docker.com beta endpoint is not a required current setup step.
Do not configure an old registry mirror merely because an earlier tutorial recommended it.
A successful pull checks registry access and image retrieval, not outbound IPv6 from a container.
Follow Docker IPv6 networking to test the container network separately.
Solution 3: NAT64 + DNS64
DNS64 alone does not provide IPv4 connectivity. Your network needs a reachable NAT64 gateway using the matching synthesis prefix.
Google Public DNS64 requires a gateway using 64:ff9b::/96, as its prerequisites explain.
Do not assume 8Labs supplies that route for your service.
- Ask support whether your assigned network offers NAT64 and which DNS64 resolver matches it.
- Record the existing resolver configuration and open a recovery console.
- Configure only the approved resolver through your operating system’s persistent network manager.
- Do not overwrite a generated
/etc/resolv.confas a permanent solution. - Check name resolution for the failed IPv4-only endpoint.
- Test an HTTPS connection to that endpoint with a timeout and normal certificate verification.
- Restore the previous resolver configuration if resolution or connectivity regresses.
A synthesized AAAA answer proves DNS synthesis, not a working translator. NAT64 is an outbound mechanism here. It does not create an inbound IPv4 mapping for your website, SSH, or RDP. See assigned addresses and NAT for inbound service endpoints.
Solution 4: LLM APIs — direct access or an approved gateway
Check the exact API endpoint used by your client. API domains, model catalogs, and transport support can change independently. Use your provider’s current API reference and a model available to your account. An HTTP authentication, quota, or model error is not necessarily an IPv6 failure.
A third-party API gateway changes the processor receiving prompts, credentials, and responses. Review its data policy, prices, model support, and account requirements before switching. Its key is separate from the original provider’s key. Do not forward the original provider’s secret without explicit support.
For a native IPv4-only endpoint, use an approved dual-stack egress or qualified NAT64 route. Changing a client base URL does not make every original endpoint or feature available through a gateway.
Verification and recovery
Check these outcomes independently:
- DNS returns an address usable through your assigned network.
- HTTPS completes with a valid certificate for the intended hostname.
- Git lists the expected public repository references.
- Docker retrieves and runs the intended image.
- An authenticated API call uses the intended account and supported model.
If a change fails, restore your recorded proxy, hosts-file, or resolver settings before making another unrelated change. For missing provider routes, send support the hostname, UTC time, failure type, and redacted diagnostic. Never include API keys, registry credentials, Git tokens, or complete environment files.