Good experience with neko remote browser
-
Probably doesn't have it set up with subnet access on to his friends network. Which tbf you wouldn't actually want for this use case.
wrote on last edited by [email protected]Yes - we're "I'll let you use my electricity for your computer thing" friends, not "I'm okay with seeing your printer on my home network" friends.
-
Perhaps there was an easier lighter-weight way of doing this?
Yeah, SSH tunneling. What I would do (and have done in the past) is something like:
ssh -L 8080:192.168.0.1:80 myserverThat will forward port 8080 on your host to port 80 on 192.168.0.1, so you can access your router's web UI with
http://localhost:8080/in your own web browser.You can also setup full tunneling with SSH, but that requires messing around with SOCKS and I usually can't be bothered.
Thanks - this is exactly what I needed.
-
I‘m using an ssh tunnel for that pupose. So if I can ssh into a remote synology, I can also create an ssh tunnel to any of the IPs of the remote network. Then I just open my regular local browser with an address https://localhost/:<local-tunnel-port>
Thanks yes - that's exactly what I needed.
-
No, he had access but clearly the router admin interface wasn't set up to allow remote access. He then needed to access the router from a browser inside the LAN, and he did have the proxmox host configured correctly to access remotely.
Yes, this.
-
Why is the cat showing its arsehole?
Because cat people are weird as fuck.
-
Yes - we're "I'll let you use my electricity for your computer thing" friends, not "I'm okay with seeing your printer on my home network" friends.
Well, that’s what you are doing with ssh tunnels and remote browsers. If you want separation, they can put your computer in their router’s DMZ (demilitarized zone), so it doesn’t have access to their devices. Additionally, If you use the Tailscale IPs (or host names) instead of their local IPs on his network, they won’t ever change.
-
Perhaps there was an easier lighter-weight way of doing this?
sshuttledoes exactly that. It's basically a VPN that uses SSH tunnelling. If you have a host in the same network as the target machine, and you can SSH into it,sshuttlecan route all TCP traffic between you and the target (or a subnet) through the host without having to bind local ports manually.sshuttle -r ssh_server <hosts/subnets...>Oh man this looks so much simpler than having to Google/man page how to ssh tunnel every 8-10 months.
-
Perhaps there was an easier lighter-weight way of doing this?
Yeah, SSH tunneling. What I would do (and have done in the past) is something like:
ssh -L 8080:192.168.0.1:80 myserverThat will forward port 8080 on your host to port 80 on 192.168.0.1, so you can access your router's web UI with
http://localhost:8080/in your own web browser.You can also setup full tunneling with SSH, but that requires messing around with SOCKS and I usually can't be bothered.
I just can't get over the fact that I didn't knew of ssh tunneling till today. P.S I have a 24x7 home server for last 5years
-
Perhaps there was an easier lighter-weight way of doing this?
Yeah, SSH tunneling. What I would do (and have done in the past) is something like:
ssh -L 8080:192.168.0.1:80 myserverThat will forward port 8080 on your host to port 80 on 192.168.0.1, so you can access your router's web UI with
http://localhost:8080/in your own web browser.You can also setup full tunneling with SSH, but that requires messing around with SOCKS and I usually can't be bothered.
wrote on last edited by [email protected]I use this to help my grandma remotely! The two steps needed were to join her into my Tailscale network and set up SSH with key authentication only.
Now I am able to SSH into her computer and enable VNC (remote control) and connect to the VNC-server over an SSH-tunnel like this.
