Remote work solution - Printable Version
+- nixers (
+-- Forum: Operating Systems (
+--- Forum: Servers Administration, Networking, & Virtualization (
+--- Thread: Remote work solution (/showthread.php?tid=2272)
Pages: 1 2

Remote work solution - venam - 24-04-2019

Hello nixers,
What's your remote work solution.

What do you use to connect to a machine far away, do your deeds, get things done.
Be it a homemade VPN solution, simply SSH with a terminal multiplexer, or mosh, maybe you have a jump host. Do you use VNC, or X11 forwarding, or thin clients, etc..

Also in which cases do you use those, day job scenario, or home scenario. Does the distance and the connection to the server change your remote workflow.

As for me, I normally use SSH with X11 forwarding for specific applications that are graphical, all within tmux to not accidentally close the terminal. I'm slowly starting to get on the mosh train too.
At work I'm not in the operation team, I'm a developer, and so I only barely use SSH to test things on a test-environment server.
However, I can say that the op team uses a jump-node/firewall where every member has a specific account with ACL to specific credentials that will let them SSH into other remote machines. There are many situations where the connection is extremely slow because of multiple VPN consecutive jump points. And sometimes they are forced to use a graphical environment.

So as far as I'm concerned I'm not very knowledgeable about the topic, I've got a simple solution. I'm really interested in knowing about more complex scenarios.

So what about you nixers, how do you work remotely?

RE: Remote work solution - evbo - 24-04-2019

At home, anything important or useful is either in a git repo or rsync'd to my backup/storage VPS so that my laptop can pull whatever I need on the go.

Work is a big govt enterprise, so all I can say is we have a ridiculously over-engineered VPN solution from Microsoft that, like most MS products, is great when it works but when it breaks the entire world crumbles.

RE: Remote work solution - xero - 24-04-2019

i vpn into private networks then usually mosh or ssh onto the systems i need to access. i use remote desktop super infrequently. i only use tmux locally, but it makes managing multiple sessions both local and remote very seamless.

RE: Remote work solution - jkl - 24-04-2019

I might add 9webdraw to my workflow this year. Currently, SSH is fine.

RE: Remote work solution - josuah - 24-04-2019

Having the remote content available works fine. Things like sshfs have the advantage of letting you using your local tool and be only slow on network in case you open/close the files. All the time you edit the file, things are as fluid as in the local filesystem.

Although, for compiling for instance, it can get really slow.

So something to fight against network latency (it's really what it is about for my slow copper / 3g links) is to have a local editor with sshfs / 9p, and an ssh window to start heavyweight operations or shelling things around.

That's 1 window with the text editor (with each remote 9p/sshfs-mounted on /mnt/$remote), and 1 window per remote.

Things get really rather comfortable this way. I guess it is why FTP is integrated on web devs IDEs...

RE: Remote work solution - z3bra - 25-04-2019

Multiple use cases, multiple solutions!
I use dvtm all the time with abduco, so I can easily detach a local session and reattach it remotely later.

To connect remotely, I use ssh +dvtm all the time. I have no use for any graphical application, as I only administer my remote servers with no X installed.

For work, we also have an OpenVPN tunnel that must be up before you can ssh. For some teams I also set up a machine to proxy their connection from the VPN to the production (this adds the AAA bit to their production access), which does HTTP / FTP and SOCKS proxying, so they can use their local web browser / mysql / jconsole / whatever and still have access to the production as if they were sitting behind their desk. As they have laptops, RDP to a local machine isn't an option.

RE: Remote work solution - mrtn - 25-04-2019

i work remote most of the time - the tools i usually use are ssh, a vpn and git. that's basically it. More important than the part where you connect to a machine is (at least for me) the question of "how do you connect to the fellow humans" who are working with you. For that, i resort mostly to text messaging (be it slack, matrix, mattermost or something like that) and a good screensharing/video conferencing tool (slack/zoom) to be able to work together, brainstorm and see each others faces once in a while.

RE: Remote work solution - pyratebeard - 25-04-2019

For work I work remote quite a bit. Any dev work is done in git. We have a VPN for access to the company network.

For any op work I ssh through one (or more!) jump servers. On our main jumpserver I run multiple tmux sessions to our client sites so I can easily switch between environments.

My own servers/devices use either ssh or mosh and tmux or dtach.

RE: Remote work solution - acg - 25-04-2019

Most of the time I have an open local tmux and open ssh connections to servers as needed. Whether I use a VPN or not, depends on the server I want to connect to.

When I'm remote or after office-hours I use the work vpn and connect to servers from there as I'd do from the office. I don't have any need for remote desktop.

My struggle is when trying to sync files between work computer and personal machine since i don't want to sync every file but i do work or several projects when it comes to development not having sync'ed up dev databases makes working remotely on those projects more complicated.

RE: Remote work solution - hubcaps - 28-04-2019

Depends on the situation for sure.

Professional work VPN into remote infra and use ssh from our jump host from there + tmux.

Homelab stuff I just ssh + port forwarding for my various needs.