Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- # unless Windows clients v2.0.9 and lower have to
- # be supported (then net30, i.e. a /30 per client)
- # Defaults to net30 (not recommended)
- ;topology subnet
- # Configure server mode and supply a VPN subnet
- # for OpenVPN to draw client addresses from.
- # The server will take 10.8.0.1 for itself,
- # the rest will be made available to clients.
- # Each client will be able to reach the server
- # on 10.8.0.1. Comment this line out if you are
- # ethernet bridging. See the man page for more info.
- server 194.163.135.241 255.255.255.0
- # Maintain a record of client <-> virtual IP address
- # associations in this file. If OpenVPN goes down or
- # is restarted, reconnecting clients can be assigned
- # the same virtual IP address from the pool that was
- # previously assigned.
- ifconfig-pool-persist ipp.txt
- # Configure server mode for ethernet bridging.
- # You must first use your OS's bridging capability
- # to bridge the TAP interface with the ethernet
- # NIC interface. Then you must manually set the
- # IP/netmask on the bridge interface, here we
- # assume 10.8.0.4/255.255.255.0. Finally we
- # must set aside an IP range in this subnet
- # (start=10.8.0.50 end=10.8.0.100) to allocate
- # to connecting clients. Leave this line commented
- # out unless you are ethernet bridging.
- ;server-bridge 10.8.0.4 255.255.255.0 10.8.0.50 10.8.0.100
- # Configure server mode for ethernet bridging
- # using a DHCP-proxy, where clients talk
- # to the OpenVPN server-side DHCP server
- # to receive their IP address allocation
- # and DNS server addresses. You must first use
- # your OS's bridging capability to bridge the TAP
- # interface with the ethernet NIC interface.
- # Note: this mode only works on clients (such as
- # Windows), where the client-side TAP adapter is
- # bound to a DHCP client.
- ;server-bridge
- # Push routes to the client to allow it
- # to reach other private subnets behind
- # the server. Remember that these
- # private subnets will also need
- # to know to route the OpenVPN client
- # address pool (10.8.0.0/255.255.255.0)
- # back to the OpenVPN server.
- ;push "route 192.168.10.0 255.255.255.0"
- ;push "route 192.168.20.0 255.255.255.0"
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement