On Tue, Aug 12, 2008 at 10:57 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > > > Rob Lockhart wrote: >> >> In /etc/sysconfig/vncservers I have something like this: >> >> VNCSERVERS="1:myusername" >> VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 -localhost" >> >> (so I can only use localhost, which means I only allow >> connections over ssh or from the local machine). >> >> Yours might be something like this: >> >> VNCSERVERS="1:robert" >> VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 >> InTransports=IPv6,IPv4" >> >> >> Well first my line has [2]. I changed that to [1] and tried all >> sorts of variants to the above, including putting a - infront of >> InTransports (like other options), and replacing the = with a >> space. No listening on IPv6. >> >> I have foudn the RealVNC support mailing list and sent a question >> there, hopefully to get answers. But if anyone has anything to >> suggest here, please do. >> >> I recently reinstalled VNC - actually "TightVNC" as it's better than VNC >> for bandwidth. If you type "Xvnc -h" you'll see all the parameters >> supported. I didn't see any options for IPv6 in my version. But yours >> might indeed have more options. > > Using this method, I don't either, though the help is -help, not -h, but > there is -multicast for IPv6 multicast for XDMCP >> >> I noticed that the default /etc/init.d/vncserver script seemed to be >> ignoring my parameters for VNCSERVERARGS as in the log file, it showed >> listening for all hosts (not just local hosts). This was confirmed by >> connecting directly from another machine to the VNC server port (:1 which is >> port 5901). I had an older version of the vncserver script, and I overwrote >> the one from the repository with that one, and it took my parameters. >> However, the parameters I can confirm are working are: "-nolisten tcp >> -localhost -desktop RobHome -geometry 1280x1024". >> >> First, verify via "Xvnc -h" that the parmeters for IPv6 are supported >> (InTransports). > > BTW, I note in the -help messages that parameters are case insensitive. Or > that is the claim. >> >> Next, could it be possible the ip6tables is blocking you? My network >> doesn't use IPv6 so I don't think I could retrace your steps. > > No. Port 5902 is specifically accepted in both iptables and ip6tables. And > I have tested this using another app that I have bound to that port (but is > not running when I try out vncserver). > > And no answer on the vnc support list.... Going to google, "tightvnc IPv6": http://www.tightvnc.com/related.html which then points (at the bottom): http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html so it looks someone has compiled TightVNC with IPv6 support. Try the new font fix, and see if it works.... -Rob