Tailcat ls and adb tunneling on Android (possibly specific to Firestick)

Abierto
  • ¿Algo no está bien?
#136 3 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, go
Área
cli, mobile-dev, networking

Línea de trabajo

Reproduce the reported commands with tailcat on the Firestick: tailcat ls TC_ID, tailcat serve 5555, tailcat forward TC_ID 15555:5555, and adb connect 127.0.0.1:15555. Compare the hanging ls and refused ADB connection with a direct LAN ADB connection. Done means the relevant tunneling behavior is understood and corrected, with both commands responding as expected.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

@bradfitz Thank you for the latest patch you made regarding the Android NS error message and for bumping the go module (I don't really understand what this is but I saw the commit!). I was able to successfully compile and start tailcat on the Firestick via adb shell and it generated a tailcat ID.

I tried a ping using tailcat ping tc_id (where tc_id is the actual id) and pong was displayed (great!!)
I then proceeded to try to ls using the command tailcat ls tc_id but it just hung (waited indefnitely but no response) - this is not a critical need for me but just thought you might have an idea on this.

What I really wanted to try to get going was to be able to serve adb (port 5555) using a forward but I could not get this to work, it just said adb refused to connect when I tried to adb connect 127.0.0.1:15555

The following were my steps, if you have any ideas (I use tailscale at the moment which creates a VPN to be able to access port 5555 but my hope was to use tailcat to avoid the limitations of controlling tailscale from another app).

Commands I have tried:
ON FS: tailcat serve 5555 (I then receive the TC_ID)
ON Windows machine: tailcat forward TC_ID 15555:5555
ON Windows machine: adb connect 127.0.0.1:15555
Response: unable to connect

I can confirm I can make a direct ADB connection to the FS using the internal LAN IP and Port 5555 without the adb popup appearing so I know adb is authorized correctly

Am I perhaps missing something in terms of the possibility of tunneling to get to ADB?

Sorry for the long message and thank you so far for the legendary fixes thus far!

Lenguaje dominante
Go
Estrellas
8.8k
Forks
404
Merge medio
3 h 48 min
PR fusionados (30 d)
1

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de tailscale/tailcat

Todos los issues de tailscale/tailcat

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.