A workaround for me was to create manually the ssh tunnel from a terminal : assuming tou can issue a simple ssh to your router with
ssh <LoginName>@<PublicNameOfRouter>
the tunnel is started with
ssh -L 9999:<VpnserverAsSeenFromRouter>:5901 <LoginName>@<PublicNameOfRouter>
assuming you've started the vpnserver on screen :1 (for screen :2 use 5902 in place of 5901 and so on)
The tricky thing is then to ask vinagre to connect to localhost:9999 (yes, localhost, not your remote router)... and it works!
NB the ssh tunnel is stopped by disconnecting from the ssh that started it.
A workaround for me was to create manually the ssh tunnel from a terminal : assuming tou can issue a simple ssh to your router with
ssh <LoginName> @<PublicNameOfR outer>
the tunnel is started with
ssh -L 9999:<Vpnserver AsSeenFromRoute r>:5901 <LoginName> @<PublicNameOfR outer>
assuming you've started the vpnserver on screen :1 (for screen :2 use 5902 in place of 5901 and so on)
The tricky thing is then to ask vinagre to connect to localhost:9999 (yes, localhost, not your remote router)... and it works!
NB the ssh tunnel is stopped by disconnecting from the ssh that started it.