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

Aperta
  • Qualcosa non va?
#136 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
android, go
Ambito
cli, mobile-dev, networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

@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!

Lingua principale
Go
Stelle
8.8k
Fork
404
Merge medio
3h 48m
PR unite (30g)
1

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di tailscale/tailcat

Tutte le issue di tailscale/tailcat

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.