Lines Matching full:gateway
356 SSH access to a gateway machine), then you need to change the above
358 sitting-here> ssh -t -L 5900:OtherHost:5900 gateway.east
360 Where gateway.east is the internet hostname (or IP) of the gateway
367 it isn't already running.) (The "-connect gateway:59xx" option may be
369 an automatic way to use a gateway and have all the network traffic
372 These gateway access modes also can be done automatically for you via
373 the "Proxy/Gateway" setting in SSVNC (including the Chaining SSH's
417 Again, this SSH gateway access can be done automatically for you via
418 the "Proxy/Gateway" setting in SSVNC. And under the "Remote SSH
541 the TightVNC "vncviewer -via gateway host:port" in its default mode to
1859 Q-56: Can Apache web server act as a gateway for users to connect via
3989 access to a gateway machine), then you need to change the above Putty
4681 Q-56: Can Apache web server act as a gateway for users to connect via
4687 the gateway to create the encrypted port redirection to x11vnc running
8618 proxy/gateway tools. Also, a perl repeater implemention is here:
9192 Note that one can also make a home-brew SOCKS5 ipv4-to-ipv6 gateway
9229 Chaining ssh's: Note that for use of a ssh gateway and -L redirection
9237 gateway="example.com" # or "user@example.com"
9249 exec /usr/bin/ssh -t -L 5900:localhost:5900 $gateway \
9260 If the gateway machine's sshd is configured with GatewayPorts=no (the
10439 Using Apache as an SSL Gateway to multiple x11vnc servers inside a
10446 user somewhere out on the Internet logs in to the SSH gateway machine
10448 user@gateway) to set up the encrypted channel that VNC is then
10468 Apache webserver as a gateway. The idea is that the company or home
10470 SSL or non-SSL) and we add to it the ability to act as a gateway for
10533 The scheme described here sets up apache on the firewall/gateway as a
10542 In this example suppose the gateway machine running apache is named
10543 "www.gateway.east" (e.g. it may also provide normal web service). We
10575 on www.gateway.east:
10684 http://www.gateway.east:563/vnc/host2
10698 http://www.gateway.east:563/vnc/proxy/host2
10703 sometimes with the Proxy case if you see 'Bad Gateway' error you will
10709 http://www.gateway.east:563/vnc/trust/host2
10710 http://www.gateway.east:563/vnc/trust/proxy/host2
10727 http://www.gateway.east/vnc/host2
10728 http://www.gateway.east/vnc/trust/host2
10766 http://www.gateway.east:563/vnc/host2/index.vnc?CONNECT=host2+5915&PORT=563,
10857 ss_vncviewer -proxy www.gateway.east:563 host1:15
10861 ss_vncviewer -proxy proxy1.foobar.com:8080,www.gateway.east:563 host1:15
10865 possible Proxy/Gateway entries
10866 Proxy/Gateway: www.gateway.east:563
10867 Proxy/Gateway: proxy1.foobar.com:8080,www.gateway.east:563
10975 https://www.gateway.east/vnc/host2
10978 https://www.gateway.east/vnc/proxy/host2
10989 https://www.gateway.east/vnc/host2
10990 https://www.gateway.east/vnc/proxy/host2
10993 https://www.gateway.east/vncs/host2
11002 https://www.gateway.east/vncs/trust/mach2
11122 Where 24.35.46.57 is the internet IP address of the gateway. In this
11231 https://gateway/vncs/machinename Similarly for non-https:
11232 http://gateway:563/vnc/machinename
11343 * Support for SSH Gateway connections and non-standard SSH ports.
11689 the otherwise unreachable VNC Server. SSH gateway machines can be used
11769 -via <GATEWAY>
13047 that acts as a proxy/gateway. Modes like these require
15013 redirection is performed by a router/gateway/firewall
