The goal is to open a web browser in my home network from a from a remote location with ssh tunnelling.
SSH tunnel is okay, I just want to somehow run a browser on my RPI3 in my home network.
Is it possible somehow?
I use my pi as a media server, only kodi is running on it, there isn't any GUI operating system on it (raspbian for example).
All kind of solution is interested.
Related
sending linux terminal traffic to chromium browser
As you know there is chromium extension called veepn. it's a tunneling service
this question may be strange, but i hardly looking a way to send linux terminal traffic (for example wget) to chromium browser.
I don't want to use vpn connection on my linux network.
anyway to do that ? thank you guys.
I am running Ubuntu Server 16.04 on the Google Compute Engine and I want to install Unity 7.4 desktop over it and connect to it with Google Remote Desktop.
It is my development machine (headless desktop), not a standalone server which needs to be minimal. As I work on the go, I am used to work remotely in the cloud. There is no problem with hardware as I can increase the RAM, CPU or HDD as needed.
After I install ubuntu-desktop package I am not able to connect SSH port 22 to my compute engine instance anymore and I lost control completely and have to recreate new instance.
There is no headless Google Remote Desktop installer, so basically I have to install temporary VNC to install Chrome, then configure the Chrome RDP headless service to run on system startup, delete the temporary VNC connection and after that I should be able to connect there anytime with my Chrome client on the go.
I have following questions:
Is Unity able to work with VNC? I have found only tutorials for XFCE and similar lightweight desktops.
Is Unity able to work with Google RDP?
What about performance? There is no 3D graphics card in Google Cloud
I have LTE on the go, so network should be no problem.
if impossible to run Unity remotely, which lightweight desktop is closest to it? (I am quite a Mac fan)
I am trying to SSH into my raspberry pi from my windows machine, and the terminal environment WAS working fine, but the GUI is acting really crappy. There is no Xming window that opens up when Xming starts (but it is running according to the task manager). The taskbar in Raspbian doesn't move around (and covers up the windows taskbar), and there is a bunch of little glitches with the desktop. My motors are also being weird: when I turn on my Pi one of them starts moving. The same thing happens when I turn off my Pi (but not the H-Bridge Board). Everything (including the motors) work perfectly fine when I use my Pi with a TV via HDMI. I have the model 2 Raspberry Pi running Raspbian, Windows 10 on my computer, and am using Putty. I'm pretty new to this, so I will appreciate any help.
Do you need the GUI? If not, I would suggest turning off X11 forwarding in putty (Connection - SSH - X11) and just using the console.
Has anyone successfully used XRDP/freeRDP to remote login to a Windows PC from a LINUX Client? I did some research on the matter and I found there may be incompatibility issues. However those posts were quite old.
I would like to use the latest XRDP or freeRDP
The site says the following:
"The goal of this project is to provide a fully functional Linux terminal server, capable of accepting connections from rdesktop, freerdp, and Microsoft's own terminal server / remote desktop clients.
Unlike Windows NT/2000/2003/2008/2012 server, xrdp will not display a Windows desktop but an X window desktop to the user.
So it sounds like I can communicate between a Linux Box and Windows. But it sounds like the Windows PC can only be the client logging into a Linux Server and not vice-versa."
Is this true?
That's not true. You can using a freeRDP client in Linux connecting to a server on Windows. I've just tried the latest freeRDP code in Ubuntu, and I've tested Win7/Win10, both are OK.
Follow the instruction of freeRDP in the following link:
https://github.com/FreeRDP/FreeRDP/wiki/Compilation
and hope you make it.
Ps: There may be some connectivity issues, like firewall or something, just google it.
I would like to setup a small computer (Raspberry Pi) running Arch Linux to accept remote X sessions. Doing this usually means setting up Xorg server and running one of the Display Managers. I have done this before, and I will go this route if I have to. However, since the machine is very underpowered, and it is actually not connected to a physical monitor, I was hoping to setup the X server to accept only remote sessions. This way no memory would be wasted on managing the local graphics card, video memory etc, since they are not being used. Is it possible to setup the X server to accept only remote sessions without going into local graphical mode? And how?
It's possible to set up a *ix to remote display to a system you're sitting in front of, without an X server on the machine running the app.
You need X11 libraries, one or more X11 applications, and you probably want openssh set up for remote X11 forwarding - all on the raspberry pi. You'll also want an X server running on the machine you're sitting in front of.
On the Raspberry Pi, change your sshd_config to include "X11Forwarding yes". After making this change, restart sshd or reboot.
Then apt-get or yum your X11 libraries and app(s).
When you connect to the Raspberry Pi machine, use "ssh -Y" instead of just ssh to pass along xauth data.
Good luck!
Disable automatic start of the login manager and X server, instructions are googlable, say http://www.debianadmin.com/howto-boot-debian-in-text-mode-instead-of-graphical-mode-gui.html. From personal experience running X apps on raspberry remotely is not too good either.