This suggests installation using vnc over ipv6 is supported: https://fedoraproject.org/wiki/Anaconda/Features/Ipv6OnlyInstallation
But when I use inst.vnc boot option, I get an text screen that says to connect to an ipv4 address, an ipv6 address isn't listed. When I go to a shell and use 'ip addr' there is a global ipv6 address, but no formatting for tigervnc I've come up with will connect, it won't connect:
vncviewer.desktop[12590]: CConn: unable connect to socket: Invalid argument (22)
If I boot Fedora 23 Server on this same hardware, the 'ip addr' address can be used successfully to ssh into the server, and also point a browser to https://%5Bipv6%5D:9090 to reach the Cockpit interface successfully.
root 1744 0.0 0.9 251060 36468 pts/0 Sl+ 03:29 0:00 Xvnc :1 -depth 16 -br IdleTimeout=0 -auth /dev/null -once DisconnectClients=false desktop=Fedora rawhide installation on host 10.0.0.15 SecurityTypes=None rfbauth=0
I can't tell if -InTransports needs to explicitly specify ipv6 for it to work. But at this point I'm stumped and can't tell if it's user error or a bug. And netstat isn't on non-live media apparently so I don't have access to that while xvnc is running to see if it's listening over something other than just an ipv4 address.
Hi All, I got fed up with vnc failing on Fedora 23 and figured it would be better under fedora 24 KDE, well it wasn't so I decided what the heck, I haven't seen Gnome is a while and it's the default, maybe it will work better.
I followed the destructions at:
https://docs.fedoraproject.org/en-US/Fedora/24/html/System_Administrators_Gu...
Took a few detours and learned a bunch of new stuff. I now have a vncserver@:0.service that starts, and I can even connect to it using vncviewer, but after about 30 - 40 seconds it times out with the message:
systemd[1]: Failed to start Remote desktop service (VNC). systemd[1]: vncserver@:0.service: Unit entered failed state. systemd[1]: vncserver@:0.service: Failed with result 'timeout'.
Any suggestions?
Gary B
On Wed, Jan 27, 2016 at 1:47 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 01/26/2016 08:44 PM, Chris Murphy wrote:
And netstat isn't on non-live media apparently so I don't have access to that while xvnc is running to see if it's listening over something other than just an ipv4 address.
Is "ss"?
No.
On Fri, Jan 29, 2016 at 2:38 PM, Chris Murphy lists@colorremedies.com wrote:
On Wed, Jan 27, 2016 at 1:47 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On 01/26/2016 08:44 PM, Chris Murphy wrote:
And netstat isn't on non-live media apparently so I don't have access to that while xvnc is running to see if it's listening over something other than just an ipv4 address.
Is "ss"?
No.
OK I figured it out and learned two things.
1. TigerVNC wants the IP address in the form [IP]:1
So literally the brackets are included, then the full IP with each colon, then a colon outside the brackets and a 1.
2. nmap -6 -A -T4 IP
Where IP is just the IP with colons, no brackets, was able to find the open 5901 port for vnc. So it was definitely working the whole time, I just had the wrong formatting for IPv6 in TigerVNC.
-
Chris Murphy -
Gary Baribault -
Gordon Messmer