Welcome to BroadbanterBanter. |
You are currently viewing as a guest which gives you limited access to view most discussions and other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today.
|uk.comp.home-networking (UK home networking) (uk.comp.home-networking) Discussion of all aspects of computer networking in the home, regardless of the platforms, software, topologies and protocols used. Examples of topics include recommendations for hardware or suppliers (e.g. NICs and cabling), protocols, servers, and specific network software. Advertising is not allowed.|
| ||Thread Tools||Display Modes|
Boredom relief: Guacamole
No, I haven't gone for the fridge and tripped out on cheese ...
I heavily use remote desktop for access to a lot of things, bringing
screens (and sometimes individual applications) from multiple PC's
across to one machine for comfortable working without mucking about with
KVM switches. And following a desire to centralise some of the remote
desktop client configurations, hit upon the idea of creating a secured
remote desktop gateway server accessible throughout me network.
Completely client-less using HTML5!
I'm still rubbing my knee when I fell off my chair!
It runs on Linux, I've got it in a few docker containers. Possibly fine
on a raspberry pi, though haven't tried.
Thinking a good use case for this, is accessing your home desktop from
somewhere else where they have locked down your ability to locally run
teamviewer, logmein etc. Obviously you'll have to sort out the security,
routing etc and it's a teensy bit laggy, but, er, wow ....
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)|