[Bug]: pairing fails after a correct PIN when the inviter connected over IPv6 link-local — the joiner's return POST drops the %zone ([fe80::…]:14321 → no route to host)
Los mantenedores suelen responder en 4 días
Evaluación
Este issue todavía no se ha evaluado.
Descripción
PAIR version
v0.1.1 (13b6811), all 14 services built from source with Go 1.25.5 (darwin/arm64); same behaviour expected from the release binaries (the code path is services/nvpair-cluster-manager/invite.go).
Operating system
macOS 26.5.2 on both nodes (inviter and joiner).
Hardware
Two Apple Mac mini M4 (16 GB) on one Wi-Fi LAN, IPv4 192.168.86.0/24 plus IPv6 link-local on en0.
Inference engine and model
Ollama 0.30.7 on the joiner (llama3.2:1b); not relevant to the bug.
What happened
cluster:invite-node {"address":"karen.local"} from the inviter returned a PIN and state:"pending"; the joiner received cluster:invite-received and answered cluster:respond-to-invite {inviteId, accept:true, pin} with the correct PIN — and the result was state:"failed". The joiner's log shows why: its completion/notify POST to the inviter used the inviter's IPv6 link-local address without the zone:
[nvpair-cluster-manager] INFO invite inv-9f69cc176d6c: completion failed: Post "http://[fe80::c16:bee4:c6a1:3fd]:14321/v1/cluster/pairing": dial tcp [fe80::c16:bee4:c6a1:3fd]:14321: connect: no route to host
[nvpair-cluster-manager] INFO invite inv-9f69cc176d6c: notify inviter fail attempt 1/3: ... (same, ×3)
fe80::/10 addresses are only routable with a scope (%en0); the inviter had reached the joiner over link-local (the hostname resolved to an IPv6 link-local first), the joiner took the remote address of that inbound connection as the inviter's address, and the zone was dropped when it was rendered back into a URL. Both nodes' /v1/cluster/pairing were reachable over IPv4 the whole time.
Expected
Either keep the zone when rendering a link-local address into the return URL ([fe80::…%25en0]), or prefer a global/IPv4 address from the inviter's advertised ips= list for the return path; at minimum surface the dial error in the respond-to-invite result instead of a bare state:"failed" after a correct PIN.
Steps to reproduce
- Two macOS nodes on one LAN with IPv6 link-local enabled (default), PAIR services running on both.
- On node A:
{"jsonrpc":"2.0","id":1,"method":"cluster:invite-node","params":{"address":"<node-B-hostname>.local"}}— where the name resolves to a link-local IPv6 first (askaren.localdid here:fe80::…then192.168.86.17). - On node B: answer
cluster:invite-receivedwithcluster:respond-to-inviteand the PIN shown on A. - Observe
state:"failed"and the log line above on B. - Repeat with
"address":"192.168.86.17"(IPv4 literal):state:"paired",nodes:get-initialshows two members on both sides.
Sanitized logs
Above; nothing else in either log around the failure. Happy to attach the full sanitizer bundle if useful.
Confirmations
- I searched existing issues (#1 mDNS source port, #3 Local Network permission, #44 multicast drops are adjacent; none covers the pairing return URL).
- I agree to follow the Code of Conduct.
- Lenguaje dominante
- Go
- Estrellas
- 1.6k
- Forks
- 266
- Merge medio
- 3 d 18 h
- PR fusionados (30 d)
- 28
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NVIDIA/Personal-AI-Router
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 20/100
NVIDIA/Personal-AI-Router#165 ·
Los mantenedores suelen responder en 4 días
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 46/100
NVIDIA/Personal-AI-Router#164 ·
Los mantenedores suelen responder en 4 días
-
enhancement
Dificultad 4/5 Más de una semana Aptitud para principiantes 12/100
NVIDIA/Personal-AI-Router#162 ·
Los mantenedores suelen responder en 4 días
-
enhancement
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
NVIDIA/Personal-AI-Router#154 · 1 comentario ·
Los mantenedores suelen responder en 4 días
-
[Feature]: [Ollama] Alert the user about model pull failuresPosiblemente ocupada @ckelseynv la tomó hace 5 días. Abiertoenhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 56/100
NVIDIA/Personal-AI-Router#152 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 4 días
Todos los issues de NVIDIA/Personal-AI-Router
Issues similares
-
component/server severity/minor type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
diagnose globalnet reports a failure for every exported headless ServicePosiblemente ocupada @kurtyoon la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
submariner-io/subctl#1948 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
Upgrade to Go 1.27.1Abiertohelp wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
meshery-extensions/meshery-mcp-server#63 · 1 comentario ·
-
Upgrade to Go 1.27.1Abiertohelp wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100