Comments on: Vino – testando a conectividade

By: Giorgio

Giorgio — Mon, 19 Jan 2009 01:26:50 +0000

Hi, any plans to allow the vino/vinagre to set up specific options for individual connections like color depth, compression level, refresh rate? I often have to use vnc on low bandwidth settings, but vino/vinagre do not allow me to do that Thanks!

By: jam

jam — Wed, 05 Nov 2008 14:58:06 +0000

it would be nice if vino had the option to open a secure tunel to a machine with a listening vnc client.

By: Rafael Proença

Rafael Proença — Mon, 03 Nov 2008 00:16:16 +0000

Brilliant! You have been doing a wonderful job Jonh, keep up the great work!

Regards.

By: Junix

Junix — Thu, 30 Oct 2008 17:19:38 +0000

Good work!!!

I think that is a great idea, very usefull.
You are a smart guy.

Best regards,

Junix

By: Bob Wallum

Bob Wallum — Wed, 29 Oct 2008 16:54:27 +0000

I think the route is in place isn’t it? Open a ssh channel then vnc through it. Vinagre/Vino is the vnc bit. What I would like is some clear syntax to make it work.

At the target end a NAT server is the norm I suggest and the target user machine must have a port forwarded from the NAT router. A window to allow the target to make their router forward a port 590x would be great. ‘sudo route’ tells them the router (default gateway). Can the port forward be automated? Is nmap any good here?

Then for the Remote Desktop Viewer end its down to syntax to string it all together. Mail headers give the route through the internet so sending an email is a very good idea (could RDV parse the header and pluck out the route? Equally could the body of the email be parsed to pick out the machine name/ip address and forwarded port?)

By: Sami Haahtinen

Sami Haahtinen — Sat, 25 Oct 2008 17:01:56 +0000

Thinking outside the box, how about adding support for other transports than plain TCP. Eric already mentioned empathy, which supports XMPP and has libjingle support.

How about using XMPP as the transport to negotiate the connection for the two parties. libjingle is capable of doing the negotiation and is rather good at it, it’s even capable of doing NAT piercing. The downside for this would be that we need a separate client that supports VNC with XMPP negotiation. But in the end, if two parties are able to talk to each other, why not take advantage of that and allow programs to sort out the kinks.

By: Hugo

Hugo — Sat, 25 Oct 2008 14:16:11 +0000

The changes you proposed for Vino’s user interface helps a lot, considering the additional comments about colors, icons and preferences for simplicity, as suggested above by some people.

I also would like to see an easy, opensource based and non-invasive solution for connecting two linux systems behind NAT, similar to crossloop (www.crossloop.com, which is free but proprietary).

By: gean gustavo

gean gustavo — Sat, 25 Oct 2008 13:54:42 +0000

como eu faço pra conectar ao meu servidor VNC que roda em um ubuntu 8.04 usando o Browser na porta 5800 como usava no realVNC? Obrigado.

By: Michael Monreal

Michael Monreal — Sat, 25 Oct 2008 10:58:09 +0000

IPv6? Ha! Well, it will replace v4 at some point in time rather sooner than later I suppose but it won’t change the usage of NAT in most places.

By: Misc

Misc — Sat, 25 Oct 2008 09:01:51 +0000

I think you could also take in account ipv6, since the goal is to have routable ip on every computer. You will likely still have a firewall problem, of course.