Quote:
Originally Posted by thebeginning
Correct, @Hubris should also install Tailscale, add their device to their Tailscale account, in their console (or cmd, whatever) do:
Code:
tailscale up --advertise-routes=192.168.1.0/24
where 192.168.1.0/24 is their local subnet (to learn what local subnet is one can do "ipconfig" on Windows or "ip a" on Linux). It's in %path% on Windows usually, but if it's not it's somewhere in Program Files and can be ran from there.
Once done, the subnet will appear in Tailscale web interface under Machines > [device] > three dots on the right > Edit route settings > Approve subnet in there.
Once this is done, they create a sharing link to their device in Machines > Device > Share on the right > Copy share link
This link should be shared privately.
Once you have both your device and theirs, it's just a matter of learning which IP does their Kindle have, enabling Wi-Fi ssh on it with a known key and ssh root@192.168.1.23. While their PC is running with Tailscale on, you'll have access to the Kindle. Once the job is done, they can revoke your access the same way it was granted in the Share menu.
There could be some issue if you have your local network in the same subnet as theirs since the routes will overlap each other, in this case I'd suggest adding not the full /24 subnet but a single device (i.e. 192.168.1.23/32 instead of 192.168.1.0/24 where 192.168.1.23 is Kindle's IP address), it should fix the routing right away. If it still doesn't, on your side do:
Code:
ip route add 192.168.1.23/32 dev a31524pt
and then it should take priority for this individual address and work. This also could be done without redefining the routes, but you get the gist already. |
Sorry guys I just don't have enough time to really perfect this! There seemed to be a few people interested in this on Kindle modding discord that have a lot more experience than me so maybe they will help. Sorry! Thank you so much for everything you've done so far!
