SSH-based Virtual Private Network #2197
-
Hello, in the OpenSSH manual pages, there is the section on the Virtual Private Network. Is it possible to perform this on Windows ? Is there a way to create a tun interface on windows nativly, and to bind it with the ssh connexion ? **``` ssh contains support for Virtual Private Network (VPN) tunnelling using the tun(4) network pseudo-device, allowing two networks to be joined securely. The sshd_config(5) configuration option PermitTunnel controls whether the server supports this, and at what level (layer 2 or 3 traffic). The following example would connect client network 10.0.50.0/24 with remote network 10.0.99.0/24 using a point-to-point connection from 10.1.1.1 to 10.1.1.2, provided that the SSH server running on the gateway to the remote network, at 192.168.1.15, allows it. On the client: ssh -f -w 0:1 192.168.1.15 trueifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252route add 10.0.99.0/24 10.1.1.2On the server: ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252route add 10.0.50.0/24 10.1.1.1Client access may be more finely tuned via the /root/.ssh/authorized_keys file (see below) and the PermitRootLogin server option. The following entry would permit connections on tun(4) device 1 from user ''jane'' and on tun device 2 from user ''john'', if PermitRootLogin is set to ''forced-commands-only'':
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Win32-OpenSSH does not currently support the PermitTunnel property, https://github.com/PowerShell/Win32-OpenSSH/wiki/sshd_config#not-supported Given this property is unsupported, it is unlikely that this scenario will be able to be completed on a Windows machine. |
Beta Was this translation helpful? Give feedback.
Win32-OpenSSH does not currently support the PermitTunnel property, https://github.com/PowerShell/Win32-OpenSSH/wiki/sshd_config#not-supported
Given this property is unsupported, it is unlikely that this scenario will be able to be completed on a Windows machine.