CTRL + A

CTRL + C

remote adres.naszego.routera.pl

dev tun

proto tcp-client

comp-lzo adaptive

keepalive 15 60

ifconfig 10.8.0.2 10.8.0.1

secret 'C:\Program Files\OpenVPN\config\key.txt'

route 192.168.1.0 255.255.255.0

persist-key

persist-tun

nobind

redirect-gateway

dhcp-option DNS 192.168.1.1

uruchom z routerem- [color=red]zaznaczamy[/color]

typ interfejsu: [color=red]TUN[/color]

protokół: [color=red]TCP[/color]

port: [color=red]1194[/color]

firewall: [color=red]automatyczny[/color]

tryb autoryzacji: [color=red]klucz statyczny[/color]

lokalne/zdalne adresy: [color=red]10.8.0.1[/color]   oraz   [color=red]10.8.0.2[/color]

Expanding the scope of the VPN to include additional machines on either the client or server subnet.

Including multiple machines on the server side when using a routed VPN (dev tun)



Once the VPN is operational in a point-to-point capacity between client and server, it may be desirable to expand the scope of the VPN so that clients can reach multiple machines on the server network, rather than only the server machine itself.



For the purpose of this example, we will assume that the server-side LAN uses a subnet of 10.66.0.0/24 and the VPN IP address pool uses 10.8.0.0/24 as cited in the server directive in the OpenVPN server configuration file.



First, you must advertise the 10.66.0.0/24 subnet to VPN clients as being accessible through the VPN. This can easily be done with the following server-side config file directive:

push "route 10.66.0.0 255.255.255.0"



Next, you must set up a route on the server-side LAN gateway to route the VPN client subnet (10.8.0.0/24) to the OpenVPN server (this is only necessary if the OpenVPN server and the LAN gateway are different machines).



Make sure that you've enabled IP and TUN/TAP forwarding on the OpenVPN server machine