The situation is as follows. On Monday, I need to showcase a program that needs the set-up development environment and hardware on my home system, at the university. The ISP are misbehaving and won't turn on the static IP service which is required to use SSH (no workarounds possible, checked with the tech support, SSH is going to work only via the static IP service) until we pay a visit to the office and sort some legal stuff out (read, give them a kick..). Obviously, that's past Monday.What I have at my disposal:the home machine, an Intel desktop PC running Fedora 23 with the required development environment and libraries, as well as the hardware the program needs to run ona laptop that I also own, a Lenovo L440, that has Windows 7 64 bit installed, and a free VMware Player with a Fedora 23 installed in it (vanilla, none of the environment I need is present there or can be set up in a sane amount of time, and of course the machine doesn't have the required hardware)a 100 MBit cable connection provided by the ISP behind a linksys router that I can log in to and change the necessary settings; alos, the ISP allows me to turn NAT on or off in the account settings on their website when necessaryWhat I need:To come to the university, connect the laptop to the Net (will be done either over the University wi-fi or, which is more probable, via a 4G USB modem with a speed of 64Kb/s, though in the case that a higher speed is required, I can pay a certain amount and have unlimited speed and bandwidth unlocked instantly)Then log into my home machineBe able to show the Fedora desktop (X.org, not just a getty login) and send mouse and keyboard input to it; well, just work on it remotely, you seeSSH or anything the depends on a static IP isn't possible. What are my other options if any?
How to show and operate a remote Linux desktop when SSH or any other remote service is unavailable?
linux;ssh;windows;remote desktop;lte
Over simple SSH, you will not see Fedora desktop.If you want to operate on desktop, probably only reasonable solution is VNC.Not having static IP is not a disaster. You might use reverse port forwarding, if you have shell access to some other server with static IP (for example university).There is also tool called autossh which monitors this connection and restarts it, if it fails for some reason (restart of remote machine) to increase reliability.In the bullet-points:On your desktop, set up password-less connection to the server and start ssh:ssh -NTf -R 22:localhost:22022 public-ipWhen you are at university, you can ssh to the same public-ip and then:ssh -p 22022 localhostwill take you to your desktop.You can forward the VNC ports similar way.Few notes:Make sure your connection from desktop does not dieautossh to restore failed connectionsServerAliveInterval, ServerAliveCountMax options to send KeepAlive messagesmake sure you desktop does not go to sleepTry things before presentation :) You should be able to verify functionality from home