Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.slackware    |    I think its the one without Selinux crap    |    87,272 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 86,029 of 87,272    |
|    Lew Pitcher to Harold Johanssen    |
|    Re: xhost not working under TigerVNC    |
|    23 Oct 22 14:07:55    |
      From: lew.pitcher@digitalfreehold.ca              On Sat, 22 Oct 2022 15:17:16 +0000, Harold Johanssen wrote:              > On Sat, 22 Oct 2022 14:59:23 -0000 (UTC), Harold Johanssen wrote:       >       >       >> Thanks. I am confused about something here thoug: when I said       >> above that I can vncviewer into A from B, the ports involved in A are (I       >> believe) 5900 and above - in my case, 5901, I think. Are you saying       >> that, besides this, the X server (TigerVNC, in my case) must be       >> listening on port 6000 as well for what I am trying to do to succeed?       >       > Actually, that may well be the problem. In B, which is running Xorg,       > I get the following (among other stuff irrelevant to our purposes):       >       > # ss -nlt       > State Recv-Q Send-Q Local Address:Port Peer Address:Port        Process       > LISTEN 0 32 0.0.0.0:5900 0.0.0.0:*       > LISTEN 0 4096 0.0.0.0:6000 0.0.0.0:*       > LISTEN 0 32 [::]:5900 [::]:*       > LISTEN 0 4096 [::]:6000 [::]:*       >       > whereas in A, which is running TigerVNC, this is what I have:       >       > State Recv-Q Send-Q Local Address:Port Peer Address:Port        Process       > LISTEN 0 5 0.0.0.0:5901 0.0.0.0:*       > LISTEN 0 5 [::]:5901 [::]:*       >       > Nothing seems to be listening on port 6000.              So, we can infer that the vncserver does not use TCP/IP in it's interaction       with X11 clients (as it should use port 6000+ for those). That means that       vncserver must use an X11 "Local" connection to service that part of the       interaction. "Local" connections are often implemented as a Unix-domain       socket (akin to a pipe), and not a network connection.              This means that ssh X11 forwarding (which works by making the remote server       look like it exists on the X11 client system localhost.localnet) won't work       here.                     --       Lew Pitcher       "In Skills, We Trust"              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca