On 9/7/2022 4:41 AM, piorunz wrote: > On 07/09/2022 05:58, notoneofmyseeds wrote: > > On 07.09.22 06:19, Alexander V. Makartsev wrote: > > > >>> > >> I've switched to NoMachine [1] a long time ago. > >> It has all features I need, which are multi-platform and cross-OS > >> support, public key authentication, reliable file transfer between > >> hosts, and completely free no strings attached license for personal use. > > > > and the there's anydesk, with conditions just as nomachine. > > > > anydesk.com > > > >> > >> > >> [1] https://www.nomachine.com/ > > Thanks for your replies guys. These solutions are overkill to my needs, > I just need reliable LAN access from one machine to another, as for WAN > access I already have ssh tunnel which tunnels all traffic I want if > need be. So, I don't think I need external, commercial, not open source > solution for my simple remote access. I'd rather fix VNC server I have > right now, or switch to different VNC server. Anyone has experience with > VNC, or similar LAN protocols, which work? Thanks in advance. > > -- > With kindest regards, Piotr. > > ⢀⣴⠾⠻⢶⣦⠀ > ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system > ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ > ⠈⠳⣄⠀⠀⠀⠀ >
I use the tigervnc-standalone-server which is in the Debian packages archives. I use it only on a trusted LAN network so I don't need an encrypted vnc connection either, and I can access it remotely from the Internet by connecting to the LAN using a VPN (I use strongswan/IKEv2 for the VPN server). The main configuration files are at ~/.vnc, and there are tools to configure it such as vncpasswd. The most important configuration file is ~/.vnc/xstartup, where you launch your DE or window manager of your choice. You can launch the server from a terminal logged in as an ordinary user and the server runs as an ordinary user in the background so after you start the server in a terminal you can exit that terminal session. With the vnc port (usually 5901) open in the firewall, you can connect to the server and start your apps, and once you have apps running, it will keep them running in the session until you kill the server. I use it with gnome-session with Xorg (I tried wayland session a while back and Xorg seemed more stable), and it works adequately for my needs on stable, testing, and sid. It works with both VNC viewers I have tried: RealVNC on Windows, and tigervnc-viewer on Debian. There is one slight annoyance that I live with: With the gnome-session desktop, there are some apps and settings that will require me to enter my password when I first use that setting or app, such as setting up a color profile, using the keyring, and starting the Brave browser. This could probably be fixed with appropriate commands in the ~/.vnc/xstartup file, but I have not tried debugging it and I just enter the password when asked by the gnome desktop and after the first time for each app or setting it won't ask again until I kill the server and restart it. Best regards, Chuck
